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

a. Set the CLUSTER_TYPE variable to metro if this a Metrocluster.
b. Set the PKGDIR variable to the full path name of the directory where the control script
has been placed. This directory, which is used for status data files, must be unique for
each package. For example, set PKGDIR to/etc/cmcluster/<package_name>,
removing any quotes around the file names. The operator may create the FORCEFLAG
file in this directory. See Appendix B for an explanation of these variables.
c. Set the DT_APPLICATION_STARTUP_POLICY variable to one of two policies:
Availability_Preferred, or Data_Currency_Preferred.
d. Set the WAIT_TIME variable to the timeout, in minutes, to wait for completion of the data
merge from source to destination volume before starting up the package on the destination
volume. If the wait time expires and merging is still in progress, the package will fail to
start with an error that prevents restarting on any node in the cluster.
e. Set the DR_GROUP_NAME variable to the name of DR Group used by this package. This
DR Group name is defined when the DR Group is created.
f. Set the DC1_STORAGE_WORLD_WIDE_NAME variable to the world wide name of the
EVA storage system which resides in Data Center 1. This WWN can be found on the
front panel of the EVA controller, or from command view EVA UI.
g. Set the DC1_SMIS_LIST variable to the list of Management Servers which resides in Data
Center 1. Multiple names are defined using a comma as a separator between the names.
If a connection to the first management server fails, attempts are made to connect to the
subsequent management servers in the order that they are specified.
h. Set the DC1_HOST_LIST variable to the list of clustered nodes which resides in Data
Center 1. Multiple names are defined using a comma as a separator between the names.
i. Set the DC2_STORAGE_WORLD_WIDE_NAME variable to the world wide name of the
EVA storage system which resides in Data Center 2. This WWN can be found on the
front panel of the EVA controller, or from command view EVA UI.
j. Set the DC2_SMIS_LIST variable to the list of Management Server, which resides in Data
Center 2. Multiple names are defined using a comma as a separator between the names.
If a connection to the first management server fails, attempts are made to connect to the
subsequent management servers in the order that they are specified.
k. Set the DC2_HOST_LIST variable to the list of clustered nodes which resides in Data
Center 2. Multiple names are defined using a comma as a separator between the names.
l. Set the QUERY_TIME_OUT variable to the number of seconds to wait for a response from
the SMI-S CIMOM in Management Server. The default timeout is 300 seconds. The
recommended minimum value is 20 seconds.
8. After customizing the control script file and creating the environment file, and before starting
up the package, do a syntax check on the control script using the following command (be
sure to include the -n option to perform syntax checking only):
# sh -n <pkgname.cntl>
If any messages are returned, it is recommended to correct the syntax errors.
9. Distribute Metrocluster Continuous Access EVA configuration, environment and control script
files to other nodes in the cluster by using ftp, rcp or scp:
# rcp -p /etc/cmcluster/<package_name>/*
other_node:/etc/cmcluster/<package_name>
See the example script Samples/ftpit to see how to semi-automate the copy using ftp.
This script assumes the package directories already exist on all nodes.
Using ftp may be preferable at your organization, since it does not require the use of
a.rhosts file for root. Root access via .rhosts may create a security issue.
Building a Metrocluster Solution with Continuous Access EVA 233