NCP-MCI-6.10 · Question #106
A Disaster Recovery administrator has setup a Protection Policy for 50 workloads - all configured in a similar fashion in terms of OS, storage, network, and performance. The RPO is 60 minutes with a…
The correct answer is D. The storage container name of the protected VMs is not the same as the DR cluster storage. In Nutanix Protection Policies, the storage container name on the remote DR cluster must match the container name on the source cluster for replication to succeed. A mismatch causes recovery points to fail to appear on the DR side even though they exist locally.
Question
A Disaster Recovery administrator has setup a Protection Policy for 50 workloads - all configured in a similar fashion in terms of OS, storage, network, and performance. The RPO is 60 minutes with a specified retention of 10 copies local, 5 copies remote, and crash consistency. After configuring the Protection Policy and activating it, the administrator has noticed that recovery points are not showing up in DR. Yet, everything within the Protection Policy looks correct and recovery points are showing up on production side. What is the most likely issue?
Options
- ANutanix NGT is not installed on the source VMs.
- BThe storage container RF factor of the protected VMs is not the same as the RF factor in the DR
- CWindows updates need to be run on all the affected VMs.
- DThe storage container name of the protected VMs is not the same as the DR cluster storage
How the community answered
(40 responses)- A10% (4)
- B8% (3)
- C3% (1)
- D80% (32)
Why each option
In Nutanix Protection Policies, the storage container name on the remote DR cluster must match the container name on the source cluster for replication to succeed. A mismatch causes recovery points to fail to appear on the DR side even though they exist locally.
NGT is required for application-consistent snapshots, but crash-consistent recovery points - as configured here - do not require NGT and would still replicate without it.
RF factor differences between source and destination containers do not prevent replication; they are independent storage settings per cluster.
Windows updates have no bearing on Protection Policy replication or the appearance of recovery points in DR.
Nutanix Leap Protection Policies map source storage containers to destination containers by name by default. If the container name on the DR cluster differs from the source cluster, replication cannot place the recovery points correctly, so they appear on production but not on the DR site. Verifying and aligning the storage container names on both clusters resolves this replication gap.
Concept tested: Nutanix Leap Protection Policy storage container name mapping
Source: https://portal.nutanix.com/page/documents/details?targetId=Leap-Admin-Guide:leap-protection-policies-c.html
Topics
Community Discussion
No community discussion yet for this question.