User's Manual

• 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 provided by SRM. Any exposure of the participating
LUNs made to other initiators not on the requested list will be removed. This feature is always
enabled.
• 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, run the command showrcopy groups <RC
group name>
If the group role is not Primary-Rev, continue with SRM Reprotect; otherwise, go to
step 2.
2. Run the following command to change Remote Copy role:
setrcopygroup reverse –local –current <RC group name>
3. Continue with the SRM reprotect operation.
NOTE: You need not perform these manual steps if the Primary Array is up and if you have
validated the HP 3PAR StoreServ SSL certificate for both the Primary and Secondary HP 3PAR
StoreServ Storage systems on both the primary and recovery sites. For more information on
validating SSL certificates, see “Validating HP 3PAR StoreServ Storage SSL certificates” (page
21).
• 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.
34 Special notes