6.1

Changing Array States Between Recovery and Reprotect
After running a recovery plan but before running reprotect, if you change the state of an array device, for
example to fix issues with reversal of replication, and you initiate a rescan of the storage devices,
Site Recovery Manager can stop unexpectedly. If this occurs, you must recreate the corresponding
protection groups and recovery plans.
Associating Nonreplicated Datastores with Storage Policies
It is possible to associate a nonreplicated datastore with a storage policy that you include in a storage policy
protection group. However, Site Recovery Manager does not protect the virtual machines that reside on a
nonreplicated datastore, even if that datastore is associated with a storage policy that is included in a
storage policy protection group. Any virtual machines that have files on a nonreplicated datastore appear
with errors in the protection group and are not recovered if you run a recovery plan that includes that
protection group.
Datastores Spanning Multiple Consistency Groups
Do not configure datastores to span multiple consistency groups. Site Recovery Manager cannot protect
such datastores or virtual machines that use multiple consistency groups and operations can fail.
n
The protection group might skip the consistency group if no other datastores backed by the consistency
group are part of the storage policy.
n
The protection group might not report problems related to the datastores.
n
Virtual machines using datastores that span consistency groups are in a nonprotected state even if the
virtual machines use the correct storage policy.
n
The datastores that span multiple consistency groups will appear to be nonreplicated and are not
protected by the storage policy protection group. Those datastores might disappear when
Site Recovery Manager migrates the protection group to the recovery site.
Protecting the Same Consistency Groups in both Array-Based Replication and
Storage Policy Protection Groups
If you tag a replicated datastore and associate it with a storage policy, you can include the storage policy
and its associated consistency groups in a storage policy protection group. It is also possible to include a
datastore group that contains the tagged datastore in an array-based replication protection group.
Consequently, consistency groups can end up being included in both an array-based replication protection
group and in a storage policy protection group.
When a storage policy protection group and an array-based replication protection group both attempt to
protect the same consistency group, the array-based replication protection group takes the ownership of the
consistency group and the virtual machines that it contains. The storage policy protection group marks the
consistency group and virtual machines in an error state. In this situation, you must remove the consistency
group from one of the protection groups.
n
To keep the consistency group in the array-based replication protection group, disassociate the affected
virtual machines from the storage policy. Also disassociate the consistency group from the storage
policy. This removes them from the storage policy protection group.
n
To keep the consistency group in the storage policy protection group, edit the array-based replication
protection group to remove the datastore and virtual machines. This automatically resolves the error in
the storage policy protection group.
Chapter 5 Creating and Managing Protection Groups
VMware, Inc. 51