Because clusters may be separated over wide geographical distances, and because they have independent function, the operation of clusters in a Continentalclusters configuration is somewhat different from that of typical Serviceguard clusters. A typical Continentalclusters recovery pair environment with versions prior than Continentalclusters A.08.00 is shown in Figure 9. A sample Continentalclusters configuration with Continentalclusters version A.08.00 is shown in Figure 10 (page 37).

Figure 9 Sample Continentalclusters Configuration

Figure 10 Sample Continentalclusters Configuration with version A.08.00

Two packages are running on the cluster in Los Angeles, and their data is replicated to the cluster in New York. 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. The New York cluster is running a monitor that checks the status of the Los Angeles cluster. In this example, the Los Angeles cluster runs just like any Serviceguard cluster, with applications configured in packages that may fail from node to node as necessary. The New

Understanding Continentalclusters Concepts

37