Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

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
RESYNC_WAIT_TIMEOUT expires and synchronization is still in progress, the package
fails to start with an error and will not start on any node in the cluster.
If the parameter RESYNC_WAIT_TIMEOUT is set to "no_timeout", then the package startup
waits for the resync until it either completes or fails.
NOTE: The RESYNC_WAIT_TIMEOUT value must not be greater than the value of
run_script_timeout parameter specified in the package configuration. Adjust the
run_script_timeout value as necessary to consider the RESYNC_WAIT_TIMEOUT
value in addition to the time taken for the full execution of each function in the package
startup.
m. To allow package to start up with non-current data, set AUTO_NONCURDATA to 1.
dts/3parrc/AUTO_NONCURDATA 1
The legal values for this parameter are “0” (default value) or “1”.
If AUTO_NONCURDATA is set to 1, Metrocluster software will allow the application to start
as long as the data is consistent; even though, it may not be current.
If AUTO_NONCURDATA is set to 0 (default value), Metrocluster software will not allow the
application to start if the data is not current. Require user intervention to bring the data
to current or to force the package to start on a node by creating FORCEFLAG in the
package directory (dts_pkg_dir) .
For the failover_policy parameter, Metrocluster failover packages can be configured
to use any Serviceguard defined failover policies. The site_preferred and site_preferred_manual
failover policies are introduced in Serviceguard specifically for Metrocluster configurations.
The site_preferred value implies that when a Metrocluster package has to fail over, it fails over
to a node within the same site. When there is no other configured node available within the
same site, the package fails over to a node of the remote site.
The site_preferred_manual failover policy provides automatic failover of packages within a
site, and manual failover across sites. To use either of these policies, the underlying cluster
324 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy