Understanding and Designing Serviceguard Disaster Recovery Architectures

Manual Recovery
There are some cases where the cluster health cannot be determined because the monitoring
happens over a network. For example, the cluster status can be reported as unreachable when
either the network service has failed or when the cluster nodes are rebooting. Hence, information
needs to be gathered from an independent source before proceeding with the recovery process.
It is for this reason the recovery in Continentalclusters is manually initiated but automatically
recovered.
After a cluster event of type alarm is triggered, the recovery process can be started using a single
command. The user can choose to recover all the recovery groups or can specify the names of the
recovery groups that need to be recovered.
Types of Configuration
Continentalclusters support the following configurations:
1. Basic configuration
2. Bi-directional/Mutual Recovery configuration
3. N-1 Configuration
4. N-1 Bidirectional configuration
5. Continentalclusters Cascading Failover
Basic configuration
In a basic Continentalclusters configuration, there is one primary cluster and one recovery cluster.
This type of a configuration is ideal when there is only one cluster running production applications
and the other cluster is on a standby mode.The standby cluster can become the production cluster
when there is a disaster.
30 Metrocluster and Continentalclusters