Once a successful recovery has occurred (and the state is confirmed) it is important to run the SRM reprotect operation as soon as possible. The FlashArray recovery process for vVols will put the recovered volumes in a protection group, but replication is not enabled on them until reprotect.
Furthermore, Site Recovery Manager does re-apply the a storage policy upon recovery to the recovered virtual machines. This is achieved by looking at the storage policy mappings within SRM:
What these mappings are missing though is a replication group mapping, as what replication group to put the VM storage in may or may not be known prior to recovery. Therefore immediately after recovery the recovered VMs will be out of compliance:
The policy is assigned but the replication group is not:
To resolve this, click on Reprotect in SRM:
The VASA provider will enable the replication (and snap policy if previously configured) schedule. From
to:
The reprotect operation will add the correct replication group into the policy assignment for the recovered virtual machines:
Accordingly, the virtual machines will now be marked as compliant:
Lastly, the reprotect will issue a synchronization of the protection group in step 5: