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

Building a Continental Cluster
Restoring Disaster Tolerance
Chapter 5 257
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. Restart the monitor using the following command on each cluster:
# cmrunpkg ccmonpkg
Alternatively, if you have modified the monitoring package
configuration, use the following sequence on each cluster to apply the
new configuration and start the monitor:
# cmapplyconf -P ccmonpkg.config
# cmmodpkg -e ccmonpkg
6. View the status of the ContinentalCluster.
# cmviewconcl
Primary Packages Remain on the Surviving Cluster
Configure the failed cluster as a recovery-only cluster and the surviving
cluster as a primary-only cluster. This minimizes the downtime involved
with moving the applications back to the restored cluster. It also
assumes that the surviving cluster has sufficient resources to handle
running all critical applications indefinitely. Use the following
procedure:
1. Halt the monitor packages. Issue the following command on each
cluster:
# cmhaltpkg ccmonpkg
2. Edit the ContinentalClusters ASCII configuration file. You will need
to change the definitions of monitoring clusters, and switch the
names of primary and recovery packages in the definitions of
recovery groups. You may also need to re-create data sender and
data receiver packages.
3. Check and apply the ContinentalClusters configuration:
# cmcheckconcl -v -C cmconcl.config
# cmapplyconcl -v -C cmconcl.config