Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/SRDF

Configuring MC/ServiceGuard Packages for Automatic Disaster Recovery

Chapter 4170

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. (The

value CONTINENTAL is only for use with the ContinentalClusters

product, described in Chapter 5.)

g. If you are using an M by N configuration, be sure that the

variable CONSISTENCYGROUPS is set to 1 in the control script:

CONSISTENCYGROUPS=1

9. Distribute MetroCluster/SRDF configuration, environment and

control script files to other nodes in the cluster by using ftp or rcp:

# rcp -p /etc/cmcluster/pkgname/* \

other_node:/etc/cmcluster/pkgname

See the example script Samples/ftpit to see how to semi-automate

the copy using ftp. This script assumes the package directories

already exist on all nodes.

Using ftp may be preferable at your organization, since it does not

require the use of a.rhosts file for root. Root access via .rhosts may

create a security issue.

10. Verify that each node in the MC/ServiceGuard cluster has the

following files in the directory /etc/cmcluster/pkgname:

pkgname.cntl ServiceGuard package control script

pkgname_srdf.env MetroCluster/SRDF environment file

pkgname.ascii ServiceGuard package ASCII configuration file

pkgname.sh Package monitor shell script, if applicable

RETRYTIM

RETRY

pkgA 60 seconds 5 attempts

pkgB 43 seconds 7 attempts

pkgC 33 seconds 9 attempts