A VM is protected in an Async Protection Policy and added to a Recovery Plan.

A Planned Failover in Nutanix Disaster Recovery is an orchestrated workflow designed to migrate workloads with zero data loss. However, the behavior of recovery point creation depends on the current state of synchronization and the type of replication policy. For standard Asynchronous (Async) Protection Policies, the system typically relies on the established schedule to maintain recovery point consistency. In many automated workflows, especially during a test or a specific " planned " trigger, the administrator might assume a new snapshot is generated; however, if the system is designed to use the most recent " consistent " state, it may rely on the last successfully replicated recovery point to initiate the restore.

Technically, if a new point were to be created, it would require the VM to be shut down at the source to ensure application consistency—a process that is part of the planned failover sequence. If the policy is configured to use existing data for speed, it bypasses new creation to minimize the maintenance window. This emphasizes the importance of verifying that replication is " In-Sync " or " Healthy " before starting a planned failover. If the last recovery point is several hours old, the " planned " move could result in a significant rollback unless the administrator manually triggers a synchronization task prior to the failover event. Understanding this behavior ensures that BCDR administrators can accurately predict data states following a controlled migration between sites.