3PAR Replication Adapter 4.x for VMware vCenter Site Recovery Manager Implementation Guide

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. This feature is always enabled.
• 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.
NOTE: ESX 3.5 is only supported on HP 3PAR OS 2.3.1 and not supported on HP 3PAR
OS 3.1.1.
• 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.
• If a failover operation is unsuccessful, make sure to clean up the local disaster state cache.
Otherwise, the subsequent SRM operations will fail.
On both the protected and recovery sites where HP 3PAR SRA is installed, issue the following
command:
◦ tpdsrm viewstate
◦ tpdsrm cleanstate -sysid <StorageSystemID> -rcgroup <RCGroupName>
• If HP 3PAR SRA fails the QuerySyncStatus call due to the GetTaskStatus call returning the error,
Malformed InServ Data List: xxx, perform the following steps to work around this
problem:
1. Get the task ID from the Malformed InServ Data List: {0 {<TaskID>} xxx}
error.
2. Log into the HP 3PAR Storage system at the protected site and issue the showtask –d
<TaskID> command. Ensure that the task ID is valid.
3. Issue the removetask –d <TaskID> command to remove the task detail.
4. Rerun the SRM operation again.
If you have multiple failed virtual volumes in the group, you may need to repeat steps 1
through 4 for all volumes.
28 Special Notes