Understanding and Designing Serviceguard Disaster Recovery Architectures

IMPORTANT: For more information on supported arrays and the features in the various releases
of Metrocluster, see Disaster recovery Clusters Products Compatibility Feature Matrix . This document
can be accessed at: http://www.hp.com/go/hpux-serviceguard-docs and selecting the respective
Metrocluster Product.
Understanding Continentalclusters
Continental Cluster
A continental cluster provides an alternative disaster recovery solution in which distinct clusters
can be separated by large distances, with wide area networking used between them. Continental
cluster architecture is implemented via the HP Continentalclusters product. The design is implemented
with distinct Serviceguard clusters that can be located in different geographic areas with the same
or different subnet configuration. In this architecture, each cluster maintains its own quorum, so an
arbitrator data center is not used for a continental cluster. A continental cluster can use any WAN
connection via a TCP/IP protocol; however, due to data replication needs, high speed connections
such as T1 or T3/E3 leased lines or switched lines may be required. See Figure 11 (page 27).
Figure 11 Sample Continentalclusters Configuration with version A.08.00
Site A
Node 1
Monitor
Package
Site A Disk Array
Site A Cluster (Primary)
Site A
Node 2
Site B
Node 1
Site B
Node 2
Data Replication Links
Recovery
Group
Packages
Recovery
Group Packages
Continentalclusters
Configuration
Package
Monitor
Package
Site B Disk Array
Site B Cluster (Recovery)
FC Switch
FC Switch
WAN
Converters
WAN
Converters
WAN
WAN
PRI_SCM_DB_PKG
cconfpkg
REC_CRM_DB_PKG
ccmonpkg
REC_SCM_DB_PKG
cconfpkg
PRI_CRM_DB_PKG
ccmonpkg
Understanding Continentalclusters 27