3PAR Storage Replication Adapter for VMware vCenter Site Recovery Manager 5.0 Implementation Guide

device read-only to meet SRM's specification before failover is to remove VLUN exposure so
that no one has access to it. HP 3PAR SRA will not be able to make the device read-writable.
Remote Copy will internally manage the snapshot taking in case something goes wrong during
the failover process. In addition, HP 3PAR SRA will also take a snapshot of the devices on the
protected site of the SRM (Remote Copy role Primary or Primary-Rev) for restore purposes
since the user might activate the Remote Copy sync after failback (setrcopygroup restore)
which would destroy the data content. The snapshot name will have the following prefix:
SRM_RECOVER_RO_<VVID>.
• Devices on the protected storage system should be read-only after failover. This is the same
with prepareFailover. The only difference is if the failover is part of the failback workflow,
the protected storage system will become secondary after failback using the setrcopygroup
restore command. Devices under the secondary Remote Copy group will automatically
have read-only access.
• Devices on the recovery storage system should be read-writable after failover. The way to
make the recovery storage system devices read-writable is to make the Remote Copy role on
the recovery storage system to Primary or Primary-Rev with the setrcopygroup
failover/restore or setrcopygroup reverse command.
• Additional protection to the data on the recovery Storage System. HP 3PAR SRA will take a
snapshot of the devices on the recovery storage system of the SRM before failover for optional
restore purpose. The snapshot name will have the following prefix:
SRM_TARGETBK_RO_<VVID>.
• Support of Dynamic Access Group. The concept of Dynamic Access Group support is to expose
LUNs only to the specified HBA initiators. Any exposure of the participating LUNs made to
other initiators not on the requested list will be removed.
• The same LUN ID should be used for every host in the same Access group. According to
VMware’s ESX configuration guide, LUNs must be presented to each HBA of each host with
the same LUN ID. This is to support the ESX 3.5 configuration.
• Multiple Remote Copy groups in one protected group is not recommended. HP 3PAR SRA will
log a warning to user if multiple instances of such configurations are detected during the Test
or Recovery operation since this might be an indication that VMs are using virtual volumes
from different Remote Copy groups.
• The re-protect operation requires at least one Remote Copy link to be running for the intended
storage pair to be up. If a recovery operation is performed as part of the failback process
when all Remote Copy links are down, additional manual steps are required on the storage
system before the user can re-protect the data.
1. On the original protected storage system, issue the following command: showrcopy
groups <RC group name>
If the group role is not Primary-Rev, continue with SRM Reprotect ; otherwise, go to
step 2.
2. Issue the following command to change Remote Copy role: setrcopygroup reverse
–local –current <RC group name>
3. Continue with the SRM re-protect operation
27