6.1

If the storage arrays fail to reverse replication for any consistency groups in the protection group, the
recovery plan goes into the Incomplete Reprotect state. In this state, you must resolve the storage issues and
run reprotect again. Rerunning reprotect on a storage policy protection group only affects the direction of
replication of consistency groups for which a previous reprotect operation did not complete successfully.
When the storage arrays have reversed the direction of replication, Site Recovery Manager reestablishes
vSphere entity protection and monitoring. The conditions for reestablishment of vSphere entity protection
and monitoring during reprotect are less strict than the conditions for establishing vSphere entity protection
and monitoring during the creation of a storage policy protection group:
n
Site Recovery Manager checks the storage policies on the new protected site for compliance. If storage
policies on the new protected site are non-compliant, reprotect does not fail but Site Recovery Manager
cannot protect the virtual machines that are associated with that storage policy. For information about
compliance, see “Prerequisites for Storage Policy Protection Groups,” on page 49 and “Limitations of
Storage Policy Protection Groups,” on page 50.
n
Site Recovery Manager restarts vSphere entity monitoring on the new protected site.
n
Site Recovery Manager starts protecting all compliant virtual machines. This might not be the same set
of virtual machines as was recovered when you ran the recovery plan initially because you or another
user might have associated more virtual machines with the storage policy on the new protected site.
Reprotect does not fail if Site Recovery Manager fails to protect a virtual machine on the new protected
site.
n
The storage policy protection group is ready for recovery from the new protected site to the new
recovery site.
Preconditions for Performing Reprotect
You can perform reprotect only if you meet certain preconditions.
You can perform reprotect on recovery plans that contain array-based replication protection groups,
vSphere Replication protection groups, and storage policy protection groups.
Before you can run reprotect, you must satisfy the preconditions.
1 Run a planned migration and make sure that all steps of the recovery plan finish successfully. If errors
occur during the recovery, resolve the problems that caused the errors and rerun the recovery. When
you rerun a recovery, operations that succeeded previously are skipped. For example, successfully
recovered virtual machines are not recovered again and continue running without interruption.
2 The original protected site must be available. The vCenter Server instances, ESXi Servers,
Site Recovery Manager Server instances, and corresponding databases must all be recoverable.
3 If you performed a disaster recovery operation, you must perform a planned migration when both sites
are running again. If errors occur during the attempted planned migration, you must resolve the errors
and rerun the planned migration until it succeeds.
Reprotect is not available under certain circumstances.
n
Recovery plans cannot finish without errors. For reprotect to be available, all steps of the recovery plan
must finish successfully.
n
You cannot restore the original site, for example if a physical catastrophe destroys the original site. To
unpair and recreate the pairing of protected and recovery sites, both sites must be available. If you
cannot restore the original protected site, you must reinstall Site Recovery Manager on the protected
and recovery sites.
Site Recovery Manager Administration
114 VMware, Inc.