Understanding and Designing Serviceguard Disaster Recovery Architectures

Figure 13 N-1 configuration
Highly
Available
Network
Site B Cluster (Primary)
Site A Cluster (Recovery)
Site C Cluster (Primary)
Data replication link
between Site A and C
Node 1 Node 2
Disk
Array
Disk
Array
Disk
Array
Node 1 Node 2
Node 1
Node 2
salespkg
customerpkg
ccmonpkg
WAN
sales_bak
cust_bak
N-1 Bidirectional configuration
N-1 bidirectional Continentalclusters configuration can have a maximum of four clusters running
production application where three production clusters are recovered in the fourth cluster. The
fourth cluster itself is recovered in one of the three other production clusters.
Continentalclusters With Cascading Failover
Continentalclusters with cascading failover uses three main data centers distributed between a
Metrocluster, which serves as a primary cluster, and a standard cluster. The standard cluster serves
as a recovery cluster.
Cascading failover means that applications are configured to fail over from one data center to
another in the primary cluster and then to a third (recovery) cluster if the entire primary cluster fails.
Data replication also follows the cascading model. Data is replicated from the primary disk array
to the secondary disk array in the Metrocluster, and then replicated to the third disk array in the
Serviceguard recovery cluster.
For more information on Cascading Failover configuration, maintenance, and recovery procedures,
see “Cascading Failover in a Continentalclusters” white paper on the high availability documentation
website at http://www.hp.com/go/hpux-serviceguard-docs -> HP Continentalclusters.
Understanding Continentalclusters 31