Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy

d. Specify the DNS resolvable name or IP address of the HP 3PAR storage system that resides
in DC1.
dts/3parrc/DC1_STORAGE_SYSTEM_NAME "3PAR001"
e. Specify the DNS resolvable name or IP address of the HP 3PAR storage system that resides
in DC2.
dts/3parrc/DC2_STORAGE_SYSTEM_NAME “3PAR002”
f. Specify the Remote Copy volume group name configured on the HP 3PAR storage system
that resides in DC1, containing the disks used by the application.
dts/3parrc/DC1_RC_VOLUME_GROUP “mcrcgroup”
g. Specify the Remote Copy volume group name configured on the HP 3PAR storage system
that resides in DC2, containing the disks used by the application.
dts/3parrc/DC2_RC_VOLUME_GROUP “mcrcgroup.r2835”
h. Specify the user on the HP 3PAR storage system that resides in DC1.
dts/3parrc/DC1_STORAGE_SYSTEM_USER “mc3parusr”
Metrocluster executes the Remote Copy commands on DC1 storage system through ssh
using this user. This user must have access to perform the Remote Copy operations on
the DC1_RC_VOLUME_GROUP.
i. Specify the user on the HP 3PAR storage system that resides in DC2.
dts/3parrc/DC2_STORAGE_SYSTEM_USER “mc3parusr”
Metrocluster executes the Remote Copy commands on DC2 storage system through ssh
using this user. This user must have access to perform the Remote Copy operations on
the DC2_RC_VOLUME_GROUP.
NOTE: The name of the storage system user can be same or different on DC1 and DC2
arrays.
j. Specify the target name associated with the Remote Copy volume group on DC1 for the
HP 3PAR storage system in DC2.
dts/3parrc/DC1_RC_TARGET_FOR_DC2 “3PAR002”
k. Specify the target name associated with the Remote Copy volume group on DC2 for the
HP 3PAR storage system in DC1.
dts/3parrc/DC2_RC_TARGET_FOR_DC2 “3PAR001”
NOTE: For steps f through k, use HP 3PAR Management Console/HP 3PAR CLI to
identify the values for configuring Metrocluster with 3PAR Remote Copy attributes.
l. Specify the timeout, in minutes, to wait for completion of the Remote Copy volume group
resynchronization from source to destination volume before starting up the package on
the destination.
dts/3parrc/RESYNC_WAIT_TIMEOUT 5
The legal values for this parameter are “0” (default value) or “no_timeout” or value greater
than “0”.
If RESYNC_WAIT_TIMEOUT is 0 (default value), and if the state of Remote Copy volume
group is in “syncing” state, Metrocluster software will not wait and will return an error.
The package will fail to start with an error and will not start on any node in the cluster.
If RESYNC_WAIT_TIMEOUT is greater than zero, and if the state of a volume in Remote
Copy volume group is in “syncing” state, Metrocluster software waits till
RESYNC_WAIT_TIMEOUT value for the completion of the synchronization. If
Configuring Modular Packages 23