After a failover and stabilization of workloads at the recovery AZ, an administrator removes several VMs from the protection policy because they are…

When VMs are removed from a protection policy after failover, their recovery points (snapshots) remain in storage, consuming space unnecessarily. These orphaned recovery points must be manually deleted to reclaim storage. Simply removing VMs from the protection policy doesn't automatically delete their associated recovery points, which continue to consume storage on both local and remote sites until explicitly removed.

A. Recreating the recovery plan doesn't address existing recovery points consuming storage.

B. Reconfiguring replication schedule only affects future replications, not existing recovery points.

D. Disabling Nearsync affects replication frequency but doesn't remove existing recovery points.

1. Nutanix Bible - Data Protection Section: Details recovery point management and storage implications (https://nutanixbible.com)

2. Nutanix AOS 5.20 Administration Guide - Chapter 12: Protection Domains and Disaster Recovery, pp. 234-237

3. Nutanix Best Practices Guide for DR - Section 4.3: Post-Failover Operations and Cleanup Procedures

4. Nutanix University Course Material - NCM Professional Certification: Module 8 - Data Protection and Recovery

5. Nutanix KB-7854: Managing Recovery Points After VM Removal from Protection Policies