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

Set the AUTO_RUN flag to NO. This is to ensure the package will not start when the cluster
starts.
Only after the primary packages start, use cmmodpkg to enable package switching on all
primary packages. By enabling package switching in the package configuration, it will
automatically start the primary package when the cluster starts. However, had there been a
source disk site disaster, resulting in the recovery package starting and running on the target
disk site, the primary package should not be started until after first stopping the recovery
package.
3. Create a package control script.
# cmmakepkg -s pkgname.cntl
Customize the control script as appropriate to your application using the guidelines in
Managing Serviceguard. Standard Serviceguard package customizations include modifying
the VG, LV, FS, IP, SUBNET, SERVICE_NAME, SERVICE_CMD and
SERVICE_RESTARTparameters. Be sure to set LV_UMOUNT_COUNT to 1 or greater
4. Add customer-defined run and halt commands in the appropriate places according to the
needs of the application. See the Managing Serviceguard user’s guide for more information
on these functions.
5. Copy the environment file template:
/opt/cmcluster/toolkit/SGCA/caeva.env to the package directory, naming it
pkgname_caeva.env:
# cp /opt/cmcluster/toolkit/SGCA/caeva.env
\/etc/cmcluster/pkgname/pkgname_caeva.env
NOTE: If a package name is not used as a filename for the package control script, it is
required to 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 the environment file name should be chosen.
Example 1: If the file name of the control script is pkg.cntl, the environment file name would
be pkg_caeva.env.
Example 2: If the file name of the control script is control_script.sh, the environment
file name would be control_script_caeva.env.
6. Edit the environment file <pkgname>_caeva.env as follows:
a. Set the CLUSTER_TYPE variable to continental
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 a description 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.
Completing and Running Continentalclusters Solution with Continuous Access EVA 247