A request is received to refresh a database clone from a new manual snapshot.
When the administrator attempts to create the new snapshot from the Time Machine, it is in a Frozen state.
What causes a Time Machine to enter the Frozen state and what are the administrator's options to complete the request?
- Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: The Time Machine must be paused, then the database re-registered with a new Time Machine and a new clone created. - Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, create a new Time Machine and create a new clone. - Cause: The Time Machine enters a Frozen state when the database is de-registered without removing the Time Machine.
Resolution: To complete the request the database must be re-registered in NDB, this thaws the Time
Machine and it resumes operation so the clone can be refreshed. - Cause: The Time Machine enters a Frozen state after too many snapshot or log catchup failures.
Resolution: Remediate the snapshot or log catchup failures, this thaws the Time Machine, allowing normal operations to continue and the request can be completed.
Answer(s): C
Explanation:
A Time Machine is a core construct of the copy data management service in NDB that captures and manages the data of a database to deliver a recovery point objective (RPO) SLA. A Time Machine can enter a Frozen state for various reasons, such as database de-registration, snapshot or log catchup failures, or manual intervention.
When a Time Machine is in a Frozen state, it stops taking new snapshots and log backups, and cannot perform any clone, refresh, or restore operations. To resume the normal operation of a Time Machine, it must be thawed by resolving the root cause of the freeze. One of the common causes of a Time Machine freeze is when the database is de-registered from NDB without removing the Time Machine. This can happen when the administrator wants to move the database to a different NDB instance or cluster, or when the database is accidentally de- registered. In this case, the Time Machine becomes orphaned and frozen, and cannot be used for any operations. To complete the request to refresh a database clone from a new manual snapshot, the administrator must first re-register the database in NDB using the same database name and ID as before. This will automatically thaw the Time Machine and resume its operation. The administrator can then create a new manual snapshot from the Time Machine and use it to refresh the database clone. The other options are not correct, as they either require unnecessary steps or do not address the root cause of the freeze.
Reference:
Nutanix Certified Professional - Database Automation (NCP-DB) v6.5, Section 5 - Protect NDB- managed Databases Using Time Machine, Objective 5.1: Create, delete, and modify SLA retention policies
Nutanix Database Management & Automation (NDMA) Course, Module 4: Nutanix Database Service (NDB) Data Protection, Lesson 4.1: Data Protection Overview, Topic: Time Machine Concepts Nutanix Support & Insights, TN-2101: Nutanix Database Service Time Machine Under the Hood, Section: Time Machine States and Transitions
Reveal Solution Next Question