Building Disaster Recovery Serviceguard Solutions Using Continentalclusters for Linux B.01.00.00

#### 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 primary cluster. The recovery package name includes ####
#### the recovery cluster name, followed by a slash ("/") ####
#### followed by the package name on the recovery cluster. ####
#### The data receiver package name includes the recovery cluster ####
#### name, followed by a slash ("/") followed by the name of ####
#### the data receiver package on the recovery cluster.The ####
#### rehearsal package name includes the recovery cluster name, ####
#### followed by a slash ("/"). ####
#### ####
#### Up to 74 recovery groups can be entered. ####
#### ####
#### Example: ####
#### ####
#### RECOVERY_GROUP_NAME nfsgroup ####
#### PRIMARY_PACKAGE westcoast/nfspkg ####
#### DATA_SENDER_PACKAGE westcoast/nfssenderpkg ####
#### RECOVERY_PACKAGE eastcoast/nfsbackuppkg ####
#### DATA_RECEIVER_PACKAGE eastcoast/nfsreplicapkg ####
#### REHEARSAL_PACKAGE eastcoast/nfsrehearsalpkg ####
#### ####
#### RECOVERY_GROUP_NAME hpgroup ####
#### PRIMARY_PACKAGE westcoast/hppkg ####
#### DATA_SENDER_PACKAGE westcoast/hpsenderpkg ####
#### RECOVERY_PACKAGE eastcoast/hpbackuppkg ####
#### DATA_RECEIVER_PACKAGE eastcoast/nfsreplicapkg ####
#### REHEARSAL_PACKAGE eastcoast/hprehearsalpkg ####
#### ####
RECOVERY_GROUP_NAME
PRIMARY_PACKAGE
# DATA_SENDER_PACKAGE
RECOVERY_PACKAGE
# DATA_RECEIVER_PACKAGE
# REHEARSAL_PACKAGE
Section 3 of the Continentalclusters ASCII configuration file
#### This section of the file contains monitoring definitions. ####
#### Well planned monitoring definitions will help in making the ####
#### decision whether or not to issue the cmrecovercl(1m) command. ####
#### Each monitoring definition specifies a cluster event along with ####
#### the messages that should be sent to system administrators ####
#### or other IT staff. ####
#### ####
#### A cluster event takes place when a monitor that is located on ####
#### one cluster detects a significant change in the condition ####
#### of another cluster. The monitored cluster conditions are: ####
#### ####
#### UNREACHABLE - the cluster is unreachable. This will ####
#### occur when the communication link to the ####
#### cluster has gone down, as in a WAN failure, ####
#### or when the all nodes in the cluster have ####
#### failed. ####
#### ####
#### DOWN - the cluster is down but nodes are responding. ####
#### This will occur when the cluster is halted, ####
#### but some or all of the member nodes are booted ####
#### and communicating with the monitoring cluster. ####
#### ####
#### UP - the cluster is up. ####
#### ####
Section 3 of the Continentalclusters ASCII configuration file 75