An administrator needs to restore a source database from a snapshot. The database shares the source volume with multiple other databases. How does NDB handle this database restore operation?

When restoring a database that resides on a storage volume shared with other databases, NDB cannot simply revert the entire volume from a snapshot, as this would revert all databases on it. Instead, NDB performs a more granular, file-level restore. It temporarily mounts the snapshot, copies only the specific data and log files belonging to the database being restored back to the original source volume, and then brings the database online. This process ensures that other databases on the shared volume are not affected.

B. This is inaccurate. NDB does not replace the source volume with disks; it copies files from the snapshot disks onto the existing source volume.
C. This action would revert all databases on the shared volume to the point in time of the snapshot, causing data loss for the other databases.
D. NDB is precise and only copies the files for the specific database being restored, not all database files from the snapshot.

1. Nutanix Database Service Administration Guide (Version 2.5), Chapter: Restoring a Database, Section: Restoring a Source Database. The documentation describes the restore workflow, which involves attaching snapshot disks and copying the relevant database files for out-of-place restores, which is the method used for shared volumes.

2. Nutanix University, NCP-DB 6.5 Courseware, Module: NDB Operations, Section: Database Restore. The course explains that for shared LUNs, NDB performs a file-level copy from the mounted snapshot to avoid impacting co-located databases.