Understanding and Designing Serviceguard Disaster Recovery Architectures

Figure 12 Basic configuration
Site A
Node 1
Site A Disk Array
Site A Cluster (Primary)
Site A
Node 2
Site B
Node 1
Site B
Node 2
Data Replication Links
Recovery Package
Primary Package
Recovery Group
Continentalclusters
Configuration
Package
Monitor
Package
Site B Disk Array
Site B Cluster (Recovery)
FC Switch
FC Switch
WAN
Converters
WAN
Converters
WAN
PRI_SCM_DB_PKG
cconfpkg
REC_SCM_DB_PKG
cconfpkg
ccmonpkg
Bi-directional / Mutual Recovery configuration
In a bi-directional Continentalclusters configuration, there are two clusters running production
applications. In case of a disaster affecting one cluster, the production applications from the failed
cluster are recovered on the other cluster. In this case, each cluster is both a primary cluster and
a recovery cluster to the other. Hence, this configuration is also termed as mutual recovery
configuration. See Figure 11 (page 27).
Instead of having a dedicated but idle recovery cluster for each cluster running a production
application, the hardware utilization can be increased by making one production cluster the
recovery cluster for the other and vice-versa.
N-1 configuration
N-1 Continentalclusters configuration can have a maximum of three primary clusters and one
recovery cluster to recover all the three primary clusters.
This configuration is ideal when there are multiple production clusters and the servers for each
cluster are very well utilized in terms of hardware. In this case a single dedicated cluster can
function as the recovery cluster for all the other primary clusters.
30 Metrocluster and Continentalclusters