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

Physical Data Replication for ContinentalClusters Using Continuous Access XP
Setting up a Recovery Package on the Recovery Cluster
Chapter 6310
less than the RUN_SCRIPT_TIMEOUT set in the package
configuration file. The default setting is the side file timeout
value + 60 seconds.
i. Uncomment the CLUSTER_TYPE variable and set it to
CONTINENTAL.
8. Distribute ContinentalCluster/CA 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.
9. Apply the MC/ServiceGuard configuration using the cmapplyconf
command or SAM.
10. Verify that each node in the MC/ServiceGuard cluster has the
following files in the directory /etc/cmcluster/pkgname:
bkpbkgname.cntl MetroCluster/CA package control script
bkpkgname_xpca.env MetroCluster/CA environment file
bkpkgname.ascii ServiceGuard package ASCII configuration file
bkpkgname.sh Package monitor shell script, if applicable
other files Any other scripts you use to manage
MC/ServiceGuard packages
11. Edit the file /etc/rc.config.d/raidmgr, specifying the Raid Manager
instance to be used for ContinentalClusters, and specify that the
instance be started at boot time.
NOTE The appropriate Raid Manager instance used by
ContinentalClusters must be running before the package is started.
This normally means that the Raid Manager instance must be
started before MC/ServiceGuard is started.