Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access XP
Completing and Running a Continental Cluster Solution with Continuous Access XP
Chapter 3 217
other files Any other scripts you use to manage
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 Serviceguard
is started.
12. Make sure the packages on the primary cluster are not running.
Using standard Serviceguard commands (cmruncl, cmhaltcl,
cmrunpkg, cmhaltpkg) test the recovery cluster for cluster and
package startup and package failover.
13. Any running package on the recovery cluster that has a counterpart
on the primary cluster should be halted at this time.
Setting up the Continental Cluster Configuration
The steps below are the basic procedure for setting up the
Continentalclusters configuration file and the monitoring packages on
the two clusters. For complete details on creating and editing the
configuration file, refer to Chapter 2, “Designing a Continental Cluster.”
1. Generate the Continentalclusters configuration.
# cmqueryconcl -C cmconcl.config
2. Edit the configuration file cmconcl.config with the names of the
two clusters, the nodes in each cluster, the recovery groups and the
monitoring definitions. The recovery groups define the primary and
recovery packages. When data replication is done using Continuous
Access XP, there are no data sender and receiver packages.
Define the monitoring parameters, the notification mechanism (ITO,
email, console, SNMP, syslog or tcp) and notification type (alert or
alarm) based on the cluster status (unknown, down, up or error).
Descriptions for these can be found in the configuration file
generated in the previous step.