The primary goal of configuring NDB high availability is ensuring the availability and uptime of the NDB service.

NDB patches both the Grid home and the Oracle home. The Grid home contains the Grid Infrastructure, while the Oracle home contains the Oracle database software. When patching a RAC environment, both homes are typically patched.

The Windows Domain profile includes information related to the SQL service startup account and the NDB worker service account. The NDB worker service account is used to communicate with the database server VM and SQL Server. This user has admin rights on the newly provisioned database server VM and SQL Server. The SQL service startup account is a domain account used to run the SQL Server database service.

Ports 3205 and 3260 are crucial for iSCSI connections, which NDB uses to interact with storage resources. Specifically, these ports must be open on the Nutanix cluster‘s Data Services IP. This allows the NDB server, agent, and database agent to communicate effectively with the storage presented by the Nutanix cluster when disks are part of a volume group attached via iSCSI

Having all the databases in the same Availability Group and registering databases in NDB ensures synchronization. Using SQL Server Always-On Availability Groups (AG). AGs synchronize a set of databases and allow for automatic failover. This requires the Enterprise Edition of SQL Server and a Full Recovery Model for the databases. It‘s important to note that AGs only synchronize the databases within the group, not server-level objects like logins or Agent Jobs.

When provisioning a new database, the two available target options are: Provision database to an existing registered [database server/cluster]: As part of the database provisioning process in NDB, you can select a database server that you have already registered or provisioned. Provision database to a new database server/cluster: The “Create Database Server“ option can be used if you don‘t have an existing database server to clone the database into. NDB will create a new database server based on the source database server hosting the source database.

When registering a new Nutanix Cluster with NDB (Nutanix Database Service), the component installed on the target cluster is the NDB Agent VM. This lightweight agent facilitates communication between the cluster and the NDB server.

The administrator should perform a Log Catch-up using source database Time Machine, then refresh the clone database.

The size of a database time machine is defined by the size of all snapshots and/or transaction logs maintained by NDB.

If there are no authorized servers available during the SQL database clone process, the database administrator should authorize one or more database server VMs. They can do this by clicking the plus icon within the NDB interface.

NoSQL databases are known for their ability to handle large-scale data with high availability and fault tolerance.

High availability in a database system can be achieved through various methods, including: Redundancy: Implementing redundant hardware components like multiple servers, storage devices, and network connections ensures the system can tolerate failures without service interruption. For example, setting up a standby server that can take over if the primary server fails.

Generally, procedural programming is commonly used for database restoration scripts due to the sequential nature of the restore process.

In database management, patching refers to the process of applying updates to database software to fix bugs, improve performance, and address security vulnerabilities. It involves installing code changes or replacing entire files to bring the database software to a newer, more stable, and secure version. This can include updates to the database management system (DBMS) itself, as well as related components like drivers or extensions.

Nutanix Database Service (NDB) leverages the Nutanix Cloud Platform‘s distributed architecture and built-in data protection mechanisms to offer high availability and fault tolerance. Features such as replication factor (RF) and synchronous replication ensure data availability even in the event of hardware failures.

The administrator should create a clone from a July 31st snapshot in Time Machine is correct. NDB Time Machine allows point-in-time recovery by restoring the database to a specific timestamp or snapshot. This approach avoids directly modifying the production database.

Data Consistency, developer community, Network latency and bandwidth are typically primary considerations when selecting a database engine for provisioning.

After testing database patches, create a new software profile version in Nutanix NDB. Apply the patches to a non-production or gold image database server. Add this patched server to NDB as the new software profile version. Finally, publish the new version. Any database server provisioned with this profile will then show an available update.

Assigning a static IP address to an NDB (Nutanix Database) instance primarily helps with: Improving security: By associating the NDB instance with a specific IP address, you can configure firewalls and access control lists to restrict access to only authorized systems or networks. This reduces the risk of unauthorized access to the NDB instance and the sensitive data it manages. Simplifying network configuration: Using a static IP address makes it easier to locate and connect to the NDB instance, especially when configuring other services or applications that interact with it. It also helps to prevent IP conflicts within the network and ensures that the NDB instance‘s address remains consistent over time, even if the server is rebooted. This simplifies ongoing management and troubleshooting.

When provisioning databases using procedural concepts, the imperative programming paradigm is frequently employed. NDButilize scripts, REST APIs, and standardized profiles, all of which align with the imperative paradigm‘s focus on explicit instructions and sequential execution. For example, the “Database Provision Workflow“ document outlines a series of steps for provisioning, restoring, and benchmarking databases, indicating a procedural approach.

When creating a Windows Domain profile in NDB, the optional fields that can be skipped and provided during the provisioning process are the custom Organizational Unit (OU) paths for server clusters and database server VMs. While these OU paths are part of the Windows Domain profile, they are not mandatory for profile creation.

Out-of-Place Upgrade is the Correct Choice, because upgrade oracle with NDB flow the following work flow ( 1- A new VM is provisioned with the latest Oracle version. 2- The existing data disks (containing the database files) are attached to the new VM. 3- Ensures a clean installation of Oracle while preserving the database. 4- Minimizes risk by allowing rollback to the previous environment if needed.

On the NDB Dashboard, the Database Summary table displays the total space used by all NDB clones for a specific database.

No, the database instance must be NDB managed to be upgraded using an NDB workflow. NDB (Nutanix Database Service) manages databases running on Nutanix AOS. If your source database is on a non-Nutanix platform, you would first need to migrate it to a Nutanix cluster and register it with NDB. Then, you can use the NDB workflows for upgrades, patching, cloning, etc. More

The developer should navigate to Databases > Clones, select the appropriate clone from the table, click Refresh, select the desired Point In Time or Snapshot and click Refresh to perform the refresh.

The best way to refresh a database every day at 9:30 PM with data from as close to the refresh time as possible is – Schedule an SLA policy to perform snapshot every day at 9:30 PM. An SLA policy scheduled for 9:30 PM will capture the latest data up to that point, fulfilling the requirement. Options a and b involve taking the snapshot at 9 PM, resulting in older data being used for the refresh. Option c, while scheduled at the correct time, performs only a log catchup and does not address the need for a full database refresh.

The two statements that best describe the features and functionality of NDB Oracle patching are: NDB patching can be automated using REST API/CLI for scheduled patching many Oracle servers in a fleet patching scenario. NDB patching for Oracle databases has automatic rollback if any of the steps in the patching workflow fails. While NDB Oracle patching offers rollback capabilities, it‘s important to note that the rollback is automatic only if a step within the patching workflow fails. The results don‘t confirm whether fleet patching can be rolled back after successful completion. Additionally, the information available doesn‘t explicitly state whether NDB requires or doesn‘t require the native Oracle Utility OpatchAuto.

The two correct processes for creating a software profile version for a newly-released Oracle International Support Center (ISC) patch are: Download the required patch from My Oracle Support. Applying the patch using OPatchAuto on a cloned virtual machine (VM) of the gold image is also correct. Ensuring the success of patch application is important. Create a new software profile version from the original software profile. Use the cloned VM where OPatchAuto was successfully run, and create the software profile version using the Nutanix Database Service (NDB) graphical user interface (GUI).

The two actions required to clone a source production database to an existing development server are: The development server must be registered by NDB: NDB (Nutanix Database Service) needs to be aware of the development server‘s existence to clone the database to it. The development server must be authorized for the database Time Machine: The Time Machine is an NDB construct associated with each registered source database and is the basis for Copy Data Management (CDM) functionality.

Create the Software Profile in NDB: After registering the VM, navigate to the NDB GUI. Select Profiles > Software, then choose the database engine, then select the registered VM. This creates the software profile, which can then be used to provision new database instances with the same configurations.

A protection Service Level Agreement (SLA) with the Continuous Log Retention option must be selected for the Log Catchup operation in Time Machine. For example, the BRONZE SLA supports continuous log retention.

A Nutanix NDB administrator can leverage Maintenance Windows to automate OS and database patching. This feature allows for scheduling these tasks during designated times, minimizing disruption to production workloads. The administrator can define specific actions within the maintenance window, such as applying OS patches or upgrading the database software.

In the Windows Administrator Name field

Incorrect, this field is not used for SQL Server User.

Correct answer

In the Login field after selecting SQL Server User

Correct, Change the connect to SQL Server login to SQL Server User, then the user can be specified in the Login field after selecting SQL Server User.

Only via the command line registration option

Incorrect, this is not the only method.

By modifying the code in the API Equivalent section

Incorrect, modifying the code is not required.

Details:

The SQL Server User can be specified in the Username field after selecting SQL Server User, the enter the password.

The maximum number of days allowed for alert retention is configurable, but defaults to 180 days. This can be adjusted in the Alert Retention settings within the user interface. Once the retention period is reached, resolved alerts are automatically purged.

The time machine heal snapshot is a database snapshot that NDB dispatches to remove gaps in the time machine’s capability. There are two ways to heal a broken time machine recovery window: Manual Heal. Manually monitor time machine capability for gaps and request for time machine heal snapshot using the below CLI: era > time_machine heal id=|name= Automatic Heal. By default, the time machine auto-heal feature is enabled. Time Machine auto-heal is an engine that runs on the NDB server every 5 minutes and checks for different cases that require a heal. If needed, the NDB server triggers heal snapshots.

Oracle and PostgreSQL are the two database engines supported with NDB for provisioning an HA instance.

Scaling the database extends the storage size proportionally across the attached virtual disks or volume groups. NDB supports scaling for both single and AG databases.

The file type that must be downloaded from the Nutanix Portal for NDB deployment is QCOW2 in case deploy on AHV, and OVA in case deploy on ESXI.

Based on the provided documentation, to create Microsoft SQL Server software profiles on three separate Nutanix clusters, the primary requirement is that each cluster must host a VM with the DB engine. This is essential as the software profile is built from a registered database server virtual machine (VM) in NDB

If the NDB server storage container and the storage container used by NDB for provisioning are different on the NDB server cluster, you must configure mapping between the remote storage container and the storage container of the NDB server.

The command era server set ip=ip_address gateway=gateway_address netmask=ip_netmask nameserver=ns1 ntp_server=ntp1 is used to assign a static IP address to the Nutanix Database (NDB) VM. The nameserver and ntp_server parameters are optional. The other parameters (ip, gateway, and netmask) are required.

Creating a new Database Parameters profile is the recommended approach for managing PostgreSQL settings related to concurrent connections. Many enterprise customers use custom profiles in NDB to tune and configure their PostgreSQL databases according to their business needs. This allows for flexibility when provisioning. While using post-create commands or editing API-equivalent shell scripts could achieve similar results, creating a Database Parameters profile offers a more manageable and standardized solution within the NDB tool.

Refresh the cloned MongoDB instance: Ensure the cloned MongoDB instance used as source data for the script contains the updated data requested by the Development team.

Based on the information available, the administrator likely encountered a missing software profile. To provision an Oracle single instance database in NDB, a software profile is required. This profile contains the necessary software and configurations for the database instance. If it is missing, the provisioning wizard will not be able to proceed with the first step.

An administrator would want to publish a software profile update so that all NDB users can use the updated profile to patch the database software on their VMs.

The NDB administrator should create a clone database from a snapshot to provide the correct database to the QA team.

The Update button is not present because the software profile is not published.

Data Usage widget represents the storage space saved by using NDB‘s cloning method compared to traditional cloning methods. NDB‘s zero-byte cloning feature only consumes storage for the delta changes between the source and clone databases, resulting in significant storage savings.

To prevent database VMs from clustering on a single host after a failure, the administrator should use VM-VM anti-affinity rules. While VM-host affinity rules can specify where a VM can run, they don‘t prevent multiple VMs from running on the same host. Anti-affinity rules, configured via aCLI, ensure that specified VMs cannot run on the same host.

While restoring a PostgreSQL HA instance, if the restore of standby nodes fails, NDB leaves the database in a PARTIAL_READY state. The primary node will be operational and ready to serve application traffic. You can rebuild the standby node using the ndb cluster rebuild command.

Nutanix Guest Tools (NGT) is required for cross-hypervisor compatibility with NDB HA enabled across multiple Nutanix clusters where some are using ESXi and others are using AHV.

A deprecated software profile version can no longer be used for provisioning. Additionally, a message will be displayed on the homepages of database server VMs and server clusters using the deprecated software profile version, indicating that they must update to a newer version.

To reset the NDB GUI password via an SSH session, the administrator should:

Enter the era-server CLI — this is the management interface for Nutanix Database Service (NDB).

Execute the command: security password reset — this securely resets the GUI password for NDB.

Other options like using sudo passwd or entering the era CLI are not applicable for resetting the NDB GUI password.

Windows Remote Management (WinRM) must be enabled on the database server. This can be accomplished by running winrm quickconfig. The command winrm get winrm/config should then return the configuration settings.

The “Update Available“ message for the Software Profile Version in NDB (Nutanix Database Service) indicates a newer version of the software profile, including operating system (OS) patches, database patches, or both, is available for the Oracle Database VM

The administrator must publish the new SQL Server software profile version to make it available to all users. This is typically done through the NDB interface. Look for an option to “Publish“ or similar wording within the software profile management section. Once published, the updated profile version will be selectable when provisioning new database VMs or patching existing ones.

To create a database clone using the NDB GUI the administrator should : Select Time Machines from the main menu dropdown. Select the time machine associated with the database you wish to clone. Click Actions and select Create a Clone.

To minimize storage usage for a test database, selecting the built-in NONE SLA is the correct approach. This policy is configured for no snapshot or log backup.

The most efficient way to exclude kernel patches for the Linux OS on a Nutanix cluster would be to exclude the appropriate repositories on the virtual machine (VM) before patching. A pre-script to disable the repositories could also achieve this.

Nutanix Database Service (NDB) offers space-efficient clones using its Copy Data Management (CDM) feature. NDB leverages Nutanix snapshots to create zero-byte database clones. This means a clone initially consumes almost no space. Storage space is used only as changes are written to the clone. This dramatically reduces the storage footprint compared to full clones.