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

Physical Data Replication for ContinentalClusters Using Continuous Access XP
Setting up a Primary Package on the Primary Cluster
Chapter 6306
# 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:
pkgname.cntl MetroCluster/CA package control script
pkgname_xpca.env MetroCluster/CA environment file
pkgname.ascii ServiceGuard package ASCII configuration file
pkgname.sh Package monitor shell script, if applicable
other files Any other scripts you use to manage
MC/ServiceGuard packages.
The MC/ServiceGuard cluster is ready to automatically switch
packages to nodes in remote data centers using MetroCluster/CA.
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.
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.
12. Using standard MC/ServiceGuard commands (cmruncl, cmhaltcl,
cmrunpkg, cmhaltpkg), test the primary cluster for cluster and
package startup and package failover.
13. Any running package on the primary cluster that will have a
counterpart on the recovery cluster must be halted at this time.