System information

n
Apply Inventory Mappings to All Members of a Protection Group on page 35
If the status of a protection group is Not Configured, you can configure protection for all of the
unconfigured virtual machines by using existing site-wide inventory mappings, in one step.
n
Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group on page 36
You can configure the mappings for the virtual machines in a protection group individually. This
ability allows you to use different resources on the recovery site for different virtual machines.
n
Modifying the Settings of a Protected Virtual Machine on page 37
You can edit the settings of a virtual machine in a protection group. Editing the settings of a virtual
machine to add or change storage devices, such as hard disks or DVD drives, can affect the protection
of that virtual machine.
n
Remove Protection from a Virtual Machine on page 38
You can temporarily remove protection from a replicated virtual machine without removing it from its
protection group.
n
Protection Group Status Reference on page 38
You can monitor the status of a protection group and determine the operation that is allowed in each
state.
n
Virtual Machine Protection Status Reference on page 39
You can monitor the status of a virtual machine in a protection group and determine the operation
that is allowed in each state.
About Array-Based Protection Groups and Datastore Groups
When you create a protection group for array-based replication, you specify array information and
Site Recovery Manager computes the set of virtual machines to a datastore group. Datastore groups contain
all the files of the protected virtual machines.
You add virtual machines to an array-based protection group by placing them in a datastore that belongs to
a datastore group that Site Recovery Manager associates with a protection group. Site Recovery Manager
recomputes the datastore groups when it detects a change in a protected virtual machine. For example, if
you add a hard disk that is on another LUN to a protected virtual machine, Site Recovery Manager adds the
LUN to the datastore group of that protection group. You must reconfigure the protection to protect the new
LUN. Site Recovery Manager computes consistency groups when you configure an array pair or when you
refresh the list of devices.
You can also add virtual machines to the protection group by using Storage vMotion to move their files to
one of the datastores in the datastore group. You can remove a virtual machine from an array-based
protection group by moving the virtual machine's files to another datastore.
If your storage array supports consistency groups, Site Recovery Manager is compatible with vSphere
Storage DRS and vSphere Storage vMotion. You can use Storage DRS and Storage vMotion to move virtual
machine files within a consistency group that Site Recovery Manager protects. If your storage array does not
support consistency groups, you cannot use Storage DRS and Storage vMotion in combination with
Site Recovery Manager.
How Site Recovery Manager Computes Datastore Groups
Site Recovery Manager determines the composition of a datastore group by the set of virtual machines that
have files on the datastores in the group, and by the devices on which those datastores are stored.
When you use array-based replication, each storage array supports a set of replicated datastores. On storage
area network (SAN) arrays that use connection protocols such as Fibre Channel and iSCSI, these datastores
are called logical storage units (LUN) and are composed of one or more physical datastores. On network file
system (NFS) arrays, the replicated datastores are typically referred to as volumes. In every pair of
Site Recovery Manager Administration
30 VMware, Inc.