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

Building a Continental Cluster
Restoring Disaster Tolerance
Chapter 5 263
CLUSTER_ALERT 0 MINUTES
NOTIFICATION SYSLOG
“CC alert: UP”
Newly Created Cluster Will Run Primary Packages
After you create a new cluster to replace the damaged cluster, you may
choose to restore the critical applications to the new cluster and restore
the other cluster to its role as a backup for the recovered packages.
1. Configure the new cluster as an MC/ServiceGuard cluster. Use the
cmviewcl command on the surviving cluster and compare the results
to the new cluster configuration. Correct any inconsistencies on the
new cluster.
2. Halt the monitor package on the surviving cluster:
# cmhaltpkg ccmonpkg
3. Edit the continental cluster configuration file to replace the data
from the old failed cluster with data from the new cluster. Check and
apply the ContinentalClusters configuration:
# cmcheckconcl -v -C cmconcl.config
# cmapplyconcl -v -C cmconcl.config
4. For each recovery group where the new cluster will run the primary
package:
a. Synchronize the data from the disks on the surviving cluster to
the disks on the new cluster. This may be time-consuming.
b. Halt the application on the surviving cluster if necessary, and
start it on the new cluster.
c. To keep application down time to a minimum, start the primary
package on the cluster before resynchronizing the data of the
next recovery group.
5. If the new cluster acts as recovery cluster for any recovery group,
create a monitor package for the new cluster.
Use the following command to apply the configuration of the new
monitor pakcage:
# cmapplyconf -p ccmonpkg.config