Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

A printout of Section 2 of the Continentalclusters ASCII configuration file follows.
###############################################################
#### #### Section 2. Recovery Groups #### ####
#### #### This section defines recovery groups--sets #### ####
#### #### of ServiceGuard packages that are ready to #### ####
#### #### recover applications in case of cluster #### ####
#### #### failure. Recovery groups allow one cluster #### ####
#### #### in the Continentalclusters configuration to #### ####
#### #### back up another member cluster's packages. #### ####
#### #### You create a separate recovery group for #### ####
#### #### each ServiceGuard package that will be #### ####
#### #### started on the recovery cluster when the #### ####
#### #### cmrecovercl(1m) command is issued. #### ####
#### #### #### ####
#### #### A recovery group consists of a primary #### ####
#### #### package running on one cluster, a recovery #### ####
#### #### package that is ready to run on a different #### ####
#### #### cluster. In some cases, a data receiver #### ####
#### #### package runs on the same cluster as the #### ####
#### #### recovery package, and in some cases, a data #### ####
#### #### sender package runs on the same cluster #### ####
#### #### as the primary package.For rehearsal #### ####
#### #### operations a rehearsal package forms a part #### ####
#### #### of the recovery group. The rehearsal package #### ####
#### #### is configured always in the recovery cluster.#### ####
#### #### During normal operation, the primary package #### ####
#### #### is running an application program on the #### ####
#### #### primary cluster, and the recovery package, #### ####
#### #### which is configured to run the same #### ####
#### #### application, is idle on the recovery cluster.#### ####
#### #### If the primary package performs disk I/O, #### ####
#### #### the data that is written to disk is #### ####
#### #### replicated and made available for possible #### ####
#### #### use on the recovery cluster. #### ####
#### #### For some data replication techniques, this #### ####
#### #### involves the use of a data receiver package #### ####
#### #### running on the recovery cluster. #### ####
#### #### In the event of a major failure on the #### ####
#### #### primary cluster, the user issues the #### ####
#### #### cmrecovercl(1m) command to halt any data #### ####
#### #### receiver packages and start up all the #### ####
#### #### recovery packages that exist on the #### ####
#### #### recovery cluster. #### ####
#### #### During rehearsal operation, before starting #### ####
#### #### the rehearsal packages,care should be taken #### ####
#### #### that the replication between the primary and #### ####
#### #### the recovery sites is suspended. For some #### ####
#### #### data replication techniques which involve #### ####
#### #### the use of a data receiver package, #### ####
#### #### rehearsal operations must be commenced only #### ####
#### #### after shutting down the data receiver #### ####
#### #### package at the recovery cluster. Rehearsal #### ####
#### #### packages are started using the #### ####
#### #### cmrecovercl -r command. #### ####
#### #### Enter the name of each package recovery #### ####
#### #### group together with the fully qualified #### ####
#### #### names of the primary and recovery packages. #### ####
#### #### If appropriate, enter the fully qualified #### ####
#### #### name of a data receiver package. Note that #### ####
#### #### the data receiver package must be on the #### ####
#### #### same cluster as the recovery package. #### ####
#### #### The primary package name includes the #### ####
#### #### primary cluster name followed by a slash #### ####
#### #### ("/") followed by the package name on the #### ####
Building the Continentalclusters Configuration 81