An administrator needs to prepare the steps to recover a cluster using Cluster Protect, where Prism Central is hosted on another cluster. What steps should the administrator take?
A.
Set the Cluster to Failed in the NC2 ConsoleRedeploy Multi Cloud Snapshot TechnologyRedeploy the cluster using the NC2 consoleRecover the User VMs
B.
Redeploy the cluster using the NC2 consoleMark the broken Cluster to be replaced in the NC2 consoleRedeploy Multi Cloud Snapshot TechnologyRecover the User VMs
C.
Redeploy the cluster using the NC2 consoleRedeploy Multi Cloud Snapshot TechnologyMark the broken Cluster to be replaced in the NC2 consoleRecover the User VMs
D.
Set the Cluster to Failed in the NC2 ConsoleRedeploy the cluster using the NC2 consoleRedeploy Multi Cloud Snapshot TechnologyRecover the User VMs
When using the Nutanix Cluster Protect feature to recover a failed NC2 cluster on AWS, and the management Prism Central (PC) instance is hosted on a separate, healthy cluster, a specific orchestration sequence must be followed. The process begins in the NC2 console, where the administrator must manually change the status of the cluster to Failed. This step is critical as it signals the portal to initiate the recovery workflow and release associated cloud resources. Next, the administrator uses the console to redeploy the cluster, which provisions new bare-metal instances and installs the AOS software. Once the infrastructure is ready, Multicloud Snapshot Technology (MST) must be redeployed or re-enabled on the new cluster to re-establish the connection to the Amazon S3 bucket containing the snapshots. Finally, the User VMs (UVMs) are recovered and hydrated from these snapshots. This specific order ensures that the target environment and management links are fully operational before data restoration commences.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit