Implementing disaster recovery for HP Integrity Virtual Machines with Metrocluster and Continentalclusters on HP-UX 11i

33
Appendix II
Sample procedure for distributing a Metrocluster SRDF env file
1. Copy the environment file template /opt/cmcluster/toolkit/SGSRDF/srdf.env to the package
directory /etc/cmcluster/vmmetro. If a legacy style package is created, rename it as the
combination of the package control script file name (without the extension), concatenated with
_srdf.env. For example, if the name of the package control script is vmmetro.cntl, then the
name of this environment file would be
vmmetro_srdf.env. If a modular style Metrocluster
package is created, rename the environment file as
<pkg_name>_srdf.env.
2. Edit the environment file as follows:
a) Uncomment AUTO*environment variables. It is recommended that the default values of these
variables be retained unless there is a specific business requirement to change them.
b) Uncomment the PKGDIR variable and set it to the full path name of the directory where the
control script has been placed. This directory must be unique for each package; it is used for
status data files. For example, set PKGDIR to
/etc/cmcluster/vmmetro.
c) Uncomment the RDF_MODE variable and set it to the RDF mode for RDF pairs in the device
group to be synchronous (
sync) or asynchronous (async). For this example, a synchronous
device group is used. Therefore set
RDF_MODE = sync.
d) Uncomment the DEVICE_GROUP variable and set it to the Symmetrix device group name. If you
are using an M by N configuration, configure the DEVICE_GROUP variable with the name of
the consistency group. In this example, the device group dgVM is used. Therefore set
DEVICE_GROUP = dgVM.
e) Uncomment the RETRY and RETRYTIME variables. These variables are used to decide how often
and how many times to retry the Symmetrix status commands. The defaults should be used for
the first package. For other packages, RETRYTIME should be altered to avoid contention when
more than one package is starting on a node. RETRY * RETRYTIME should be approximately
five minutes to keep package startup time under 5 minutes.
f) Uncomment the CLUSTERTYPE variable and set it to
METRO.
g) If using an M by N configuration, be sure that the variable CONSISTENCYGROUPS is set to
1.
In this example, a regular device group is used. Therefore set
CONSISTENCYGROUPS = 0.
3. Distribute the Metrocluster configuration to all other nodes in the cluster.
Sample procedure for distributing Metrocluster Continuous Access EVA
1. Copy the environment file template /opt/cmcluster/toolkit/SGCAEVA/caeva.env to the
package directory
/etc/cmcluster/vmmetro. If a legacy style package is created, rename it as
the combination of the package control script file name (without the extension and concatenate
with
_caeva.env. For example, if the name of the package control script is vmmetro.cntl, then
the name of this environment file would be
vmmetro caeva.env. If a modular style Metrocluster
package is created, rename the environment file as
<pkg_name>_caeva.env.
2. Edit the environment file as follows:
a) Set the CLUSTER_TYPE variable to
METRO.
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.
c) Set the DT_APPLICATION_STARTUP_POLICY variable to one of two policies:
Availability_Preferred, or Data_Currency_Preferred.