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

1. If this was not done previously, split the EMC SRDF logical links for the disks associated with
the application package. See the script, Samples/pre.cmquery (edit to the SRDF groups
configured) for an example of how to automate this task. The script must be customized with
the Symmetrix device group names.
2. Create and test a standard Serviceguard cluster using the procedures described in the
Managing Serviceguard user’s guide.
3. Install Continentalclusters on all the cluster nodes in the source disk site (Skip this step if the
software has been pre installed)
NOTE: Serviceguard should already be installed on all the cluster nodes.
Run swinstall(1m)to install Continentalclusters and Metrocluster with EMC SRDF products
from an SD depot.
4. When swinstall(1m) has completed, create a directory as follows for the new package
in the source disk site.
# mkdir /etc/cmcluster/<pkg_name>
5. Copy the environment file template /opt/cmcluster/toolkit/SRDF/srdf.env to the
package directory, naming it pkgname_srdf.env:
# cp /opt/cmcluster/toolkit/SGSRDF/srdf.env \
/etc/cmcluster/pkgname/pkgname_srdf.env
6. Create an Serviceguard Application package configuration file.
# cd /etc/cmcluster/<pkg_name>
# cmmakepkg -p <pkg_name>.conf
Customize it as appropriate to your application. Be sure to include Node names, and the path
name of the control script (/etc/cmcluster/<pkg_name>/<pkg_name>.cntl) for the
RUN_SCRIPT and HALT_SCRIPT parameters.
Also change AUTO_RUN (PKG_SWITCHING_ENABLED in Serviceguard A.11.09) to NO. This
will ensure that the application packages will not start automatically. (the ccmonpkg will be
set to yes) Define the service (as required)
7. Create a package control script.
# cmmakepkg -s pkgname.cntl
Customize the control script as appropriate to your application using the guidelines in the
Managing Serviceguard user’s guide. 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.
8. 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.
9. Edit the environment file <pkg_name>_srdf.env as follows:
a. Add the path where the EMC Solutions Enabler software binaries have been installed to
the PATH environment variable. The default location is /usr/symcli/bin.
b. Uncomment AUTO*environment variables. It is recommended to retain the default values
of these variables unless there is a specific business requirement to change them. See
Appendix B for an explanation of these variables.
c. 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 and
is used for status data files. For example, set PKGDIR to
/etc/cmcluster/<pkg_name>.
300 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF