An NDB administrator would like to configure a database with a Time Machine protection mode that includes the Log Catchup operation. What would be…

To configure a database with a Time Machine protection mode that includes the Log Catchup

operation in NDB, the most essential component is a Service Level Agreement (SLA) that supports

continuous log retention. The Log Catchup operation enables point-in-time recovery (PITR) by

replaying transaction logs from a specified point, ensuring minimal data loss and meeting Recovery

Point Objective (RPO) requirements. This functionality depends on the Time Machine being

configured with an SLA that includes the "Continuous Log Retention" option, which ensures

transaction logs are captured and retained continuously alongside snapshots.

Option A is incorrect because a daily snapshot alone is insufficient without log retention to enable

Log Catchup.

Option B is incorrect because an SLA retention schedule for daily snapshots does not inherently

include continuous log capture, which is required for Log Catchup.

Option C is correct as it specifies the Continuous Log Retention option, the critical feature for

enabling Log Catchup in a Time Machine SLA.

Option D is incorrect because while frequency settings are important, they are secondary to selecting

an SLA with continuous log retention as the foundational requirement.

This configuration ensures robust data protection and recovery capabilities tailored to the database’s

needs.

Reference:

Nutanix Database Service (NDB) User Guide, Chapter 5: Configuring Time Machines, Section: Setting

Up SLAs with Log Catchup

Nutanix Support & Insights, Knowledge Base Article: "Configuring Time Machine with Log Catchup in

NDB"

Nutanix Certified Professional - Database Automation (NCP-DB) v6.5 Blueprint, Section 5: Protect

Databases Using Time Machine