
An administrator needs to restore a source database from a point in time at 21:50, but the restore option is not available.
What could explain the matter?
Correct Answer: D
The provided exhibit shows the NDB Time Machine restore interface for October 31, 2024, with a Point-in- Time (PIT) restore option selected at 21:50. However, the restore option is unavailable, as indicated by the question. The exhibit includes a warning: "Logs to Backup: The database may contain additional logs. Backup any remaining logs before restore or they will be lost." This suggests that PIT restore requires continuous log retention, and if logs since the last snapshot (at 01:10:00) are not backed up, the restore to 21:50 cannot proceed. Running the "Logs to Backup" operation ensures all transaction logs are captured, enabling PIT restore by allowing NDB to replay logs to the desired point.
* Option A (Point in time must be within the most recent range) is incorrect because the selected 21:
50 is within the log retention period shown (up to the current time), but logs need to be backed up.
* Option B (Selected Restore time is not available) is incorrect because 21:50 is a valid time within the log range, but log backup is the issue.
* Option C (Change to snapshot option) is incorrect because switching to a snapshot limits the restore to the snapshot time (01:10:00), not 21:50.
* Option D (Logs to Backup must be run first) is correct as the warning indicates that backing up remaining logs is necessary for PIT restore.
After running the backup, the administrator can proceed with the PIT restore.
References
* Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Point- in-Time Restore Requirements
* Nutanix Support & Insights, Knowledge Base Article: "Troubleshooting PIT Restore Issues in NDB"
* Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect Databases Using Time Machine