NCP-MCI-6.10 · Question #36
A Disaster Recovery administrator has set up a Protection Policy for 50 workloads, all configured similarly. The RPO is 60 minutes with a specified retention of 10 local copies, 5 remote copies, and…
The correct answer is C. The storage container name on the DR cluster does not match the production cluster. In Nutanix replication, when a VM is recovered or replicated to a DR site, the storage container on the DR cluster must have the same name as the source container. Nutanix replication maps containers by name; if the names do not match, the recovery points cannot be written to…
Question
A Disaster Recovery administrator has set up a Protection Policy for 50 workloads, all configured similarly. The RPO is 60 minutes with a specified retention of 10 local copies, 5 remote copies, and crash consistency. After activation, recovery points are not appearing at the DR site, even though they are visible on the production side. What is the most likely issue?
Options
- ANutanix Guest Tools (NGT) is not installed on the source VMs.
- BWindows updates need to be applied to all affected VMs.
- CThe storage container name on the DR cluster does not match the production cluster.
- DThe storage container RF factor does not match in both clusters.
How the community answered
(39 responses)- A8% (3)
- B3% (1)
- C72% (28)
- D18% (7)
Explanation
In Nutanix replication, when a VM is recovered or replicated to a DR site, the storage container on the DR cluster must have the same name as the source container. Nutanix replication maps containers by name; if the names do not match, the recovery points cannot be written to the DR cluster and will not appear there - even though they are visible locally on the production side. NGT (option A) is required only for application-consistent snapshots; since the policy uses crash consistency, NGT absence would not block replication entirely. Windows updates (option B) are unrelated. RF factor mismatches (option D) do not prevent recovery point replication.
Topics
Community Discussion
No community discussion yet for this question.