What causes a Time Machine to enter the Frozen state and what are the administrator’s options to complete the request?

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?
A . 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.
B . 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.
C . 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.

D . 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: C

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments