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

Building a Continental Cluster
Understanding Continental Cluster Concepts
Chapter 5182
Application Recovery in a Continental Cluster
If a given cluster of a continental cluster should become unavailable,
ContinentalClusters allows an administrator to issue a single command
(cmrecovercl, described later) to transfer mission critical applications
from the that cluster to another cluster, making sure that the packages
do not run on both clusters at the same time. Transfer is not automatic,
although it is automated through a recovery command, which a root user
must issue. The result after issuing the recovery command is shown in
Figure 5-3.
Figure 5-3 Continental Cluster After Recovery
The movement of an application from one cluster to another cluster does
not replace local failover activity; packages are normally configured to
fail over from node to node as they would on any high availability cluster.
Cluster recovery—failover of packages to a different cluster—occurs
only after the following:
• ContinentalClusters detects the problem.
• ContinentalClusters sends you a notification of the problem.
NYnode1 NYnode2
salespkg
custpkg_bak
LAnode1 LAnode2
Cluster
Los Angeles
Cluster
New York
WAN
Highly Available
Network
Data Replication Links
Disk
Disk
Array
Array