Designing a Continental Cluster
Understanding Continental Cluster Concepts
Chapter 242
Figure 2-2 Sample Mutual Recovery Configuration
In the above figure, the salespkg is running on the New York cluster
and can be recovered by the Los Angeles cluster. Similarly, the custpkg
running on the Los Angeles cluster can be recovered by the New York
cluster. As stated previously, physical data replication is carried out
using ESCON (Enterprise Storage Connect) links between the disk
array hardware in New York and Los Angeles via an ESCON/WAN
converter at each end. Each cluster is running a monitor that checks the
status of the alternate cluster.
As depicted in the above example, each cluster runs just like any
Serviceguard cluster, with applications configured in packages that may
fail from node to node as necessary. Each cluster is configured with a
recovery version of the packages that are running on the alternate
cluster. These packages do not run under normal circumstances, but are
set to start up when they are needed. In addition, either cluster may run
other packages that are not involved in Continentalclusters operation.
NYnode1 NYnode2
LAnode1 LAnode2
monitor
custpkg
Cluster
Los Angeles
New York
WAN
Highly Available
Network
Data Replication Links
Disk
Disk
Array
Array
monitor
ESCON/WAN converter
salespkg
Cluster