While adding Time Machine data access to a Nutanix cluster, when is a storage container mapping needed
Time Machine data access is a feature of Nutanix Database Service (NDB) that allows you to access a point-in-time snapshot of a database without restoring it. To use this feature, you need to create a Data Access Management (DAM) policy that defines the access mode, the source database, the destination cluster, and the storage container mapping. The storage container mapping is needed when the source database and the NDB Server containers are different, because NDB needs to know where to store the metadata and the clone of the source database. If the source database and the NDB Server containers are the same, then NDB will use the same container for both the metadata and the clone.Reference:
Database (NCP-DB) Exam Blueprint Guide - Nutanix, Page 9, Objective 5.6
An administrator needs to roll back an Oracle patch on a database server VM using NDB. What is required for this action to be successful?
To roll back an Oracle patch on a database server VM using NDB, the patch must have been applied using NDB in the first place. This is because NDB maintains a patch inventory and history for each database server VM and database that it manages. NDB uses this information to determine which patches can be rolled back and how to revert the changes made by the patch. If the patch was applied outside of NDB, NDB would not have the patch information and would not be able to roll back the patch. Therefore, the patch must have been applied using NDB for the rollback action to be successful. The other options are not required for the rollback action. The database does not need to be shut down or in read-only mode, as NDB can perform the rollback operation online. The patch does not need to be applied on Grid home only, as NDB can roll back patches applied on both Grid home and Database home.Reference:
[Nutanix Database Service (NDB) User Guide], Chapter 7: Patching, Section: Rolling Back a Patch
An administrator would like to use Era for Copy Data Management operations on an Availability Group (AG) database. The AG database is hosted on replicas with different named instances, as shown below:
* SQLAGNI\EMR
* SQLAGN2\EMR
* SQLAGN3\DW
SQLAGN3\DW is running the Analytics service that needs real-time data.
How should the administrator register the database in Era?
What is the purpose of Data Access Management policies in NDB Multi-Cluster?
Data Access Management (DAM) policies are a feature of NDB Multi-Cluster that allows you to control the access and availability of time machine data across different Nutanix clusters. You can use DAM policies to specify which clusters can access the time machine data of a source database, and which clusters can replicate the time machine data for backup or disaster recovery purposes. DAM policies help you to optimize the storage and network resources, as well as ensure the security and compliance of your database workloads. The purpose of DAM policies is not to register multiple Nutanix clusters in NDB, as this is done by using the Add Cluster option in the NDB settings page. The purpose of DAM policies is also not to perform snapshot operations on a single Nutanix cluster, as this is done by using the Time Machine feature in the NDB dashboard. The purpose of DAM policies is also not to remove data accessibility of a time machine across all registered Nutanix clusters in NDB, as this is done by using the Delete option in the Time Machine page.Reference:
Where would an administrator find the total space being used by all Era clones for a specific database?