NDB allows creating and refreshing clones to a point in time using two primary methods:
B. Snapshots: NDB uses storage snapshots (e.g., via Nutanix Volumes or AHV) to capture the database state at a specific point. These snapshots can be used to create or refresh clones, providing a consistent recovery point.
D. Transaction logs: Transaction logs (e.g., PostgreSQL WAL, SQL Server logs) enable point-in-time recovery (PITR) by applying logs to a snapshot, allowing clones to be refreshed to a precise moment.
Other options are not supported for this purpose:
A. Full backups: Full backups are used for complete restores but are not optimized for frequent clone refreshes.
C. VM snapshots: VM-level snapshots (e.g., AHV snapshots) are not managed by NDB for database cloning, as they lack database consistency.
Thus, the verified answers are B and D, reflecting NDB’s clone refresh capabilities.
Official Nutanix Database Automation References
Nutanix Database Management & Automation (NDMA) course, Module 5: Data Protection and Recovery, Lesson 5.2: Managing Time Machines and Clones.
Nutanix Certified Professional - Database Automation (NCP-DB) v7.5Knowledge Objectives, Section 5: Protect Databases Using NDB, Objective 5.2: Manage Clones (applicable to v7.5).
Nutanix NDB Administration Guide: "Clone Creation and Refresh" section.
