Nutanix manages data recovery operations differently depending on whether a virtual machine is in an asynchronous or synchronous replication state. For a standard Asynchronous VM like " REPORTING-DEV, " the local cluster takes periodic snapshots. If data corruption occurs, the administrator can perform an " In-place Restore " or " Revert " using a local recovery point. This is a standard procedure where the current vDisks are overwritten by the point-in-time data from the snapshot.

However, " ERP-PROD " is part of a Synchronous replication policy (0 RPO). This means the storage container it resides on is effectively " stretched " and locked in an active-active relationship with a remote cluster. Every write must be identical at both sites. If an administrator attempts to " Revert " a synchronous VM to a local snapshot, it would cause an immediate data mismatch between the primary and recovery sites, breaking the zero-RPO guarantee and potentially causing cluster-wide consistency issues. To protect data integrity, Prism Central typically grays out or blocks the " Revert " option for VMs currently in an active synchronous " Sync " state. To recover such a VM, an administrator would generally need to either " Clone " the snapshot to a new VM or temporarily move the VM into an asynchronous state by modifying the policy, thereby unlocking the ability to revert the data disks locally before re-enabling synchronization.