Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access EVA
Completing and Running a Continental Cluster Solution with Continuous Access EVA
Chapter 4 275
switching on a recovery package will be automatically set by the
cmrecovercl command on the recovery cluster when it successfully
starts 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_RESTART parameters. Be
sure to set LV_UMOUNT_COUNT to 1 or greater.
NOTE Some of the control script variables, such as VG and LV, on the
recovery cluster must be the same as on the primary cluster. Some of
the control script variables, such as, FS, SERVICE_NAME,
SERVICE_CMD and SERVICE_RESTART are probably the same as on the
primary cluster. Some of the control script variables, such as IP and
SUBNET, on the recovery cluster are probably different from those on
the primary cluster. Make sure that you review all the variables
accordingly.
4. Add customer-defined run and halt commands in the appropriate
places according to the needs of the application. See Managing
Serviceguard for more information on these functions.
5. Copy the environment file template
/opt/cmcluster/toolkit/SGCA/xpca.env to the package directory,
naming it pkgname_xpca.env:
# cp /opt/cmcluster/toolkit/SGCA/caeva.env \
/etc/cmcluster/pkgname/pkgname_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,