Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

NOTE: If you are not using a package name as a filename for the package control script,
you must follow the convention of the environment file name. This is the combination of the
file name of the package control script without the file extension, an underscore and type of
the data replication technology (caeva) used. The extension of the file must be env. The
following examples demonstrate how you must select the environment file name.
For Example:
If the file name of the control script is pkg.cntl, the environment file name would be
pkg_caeva.env.
If the file name of the control script is control_script.sh, the environment file name would
be control_script_caeva.env.
7. Edit the environment file pkgname_caeva.env as follows:
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 is
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
quotation marks 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 HP
P6000/EVA storage system which resides in Data Center 1. This WWN can be found
on the front panel of the P6000/EVA controller, or from HP P6000 Command View 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 HP
P6000/EVA storage system which resides in Data Center 2. This WWN is available on
the front panel of the P6000/EVA controller, or on the HP P6000 Command View 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. Customize the control script file and create the environment file, and then 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, HP recommends to correct the syntax errors.
Configuring legacy Metrocluster package 93