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

As the processing of each recovery group occurs (the message about the data receiver package
appears only using logical data replication with data sender and receiver packages):Processing
the recovery group nfsgroup on recovery cluster eastcoast.Disabling
switching for data receiver package nfsreceiverpkg on recovery cluster
eastcost.Halting data receiver package nfsreceiverpkg on recovery cluster
east coast.Starting recovery package nfsbackuppkg on recovery cluster
eastcoast.Enabling package nfsbackuppkg in cluster
eastcoast.----------------exit status = 0----------------
The command cmrecovercl starts up all the recovery packages that are configured in the recovery
groups. The cmrecovercl -c command skips recovery for recovery groups in maintenance
mode.
In addition to starting the recovery packages all at once, another option is to recover an individual
recovery group by using the following command:
# cmrecovercl -g Recovery_Group_Name
Running the cmrecovercl command with option -g starts up only the recovery package configured
in the specified recovery group. The cmrecovercl -g command fails to recover if the specified
recovery group is in maintenance mode.
NOTE: After the cmrecovercl command is run, there is a delay of at least 90 seconds per
recovery group as the command makes sure that the package is not active on another cluster.
Use the cmviewcl command on the local cluster to confirm that the recovery packages are running
correctly.
Starting a recovery package forcefully
You can use the cmforceconcl command to force a Continentalclusters package to start even
if the status of a remote package in the recovery group is unknown. This command is used as a
prefix with the cmrunpkg and cmmodpkg command.
Under normal circumstances, Continentalclusters does not allow a package to start in the recovery
cluster unless it can determine that the package is not running in the primary cluster. In some cases,
communication between the two clusters might be lost, and it might be necessary to start the
package on the recovery cluster anyway. To do this, use the cmforeconcl command, which is
used along with a cmrunkpg or cmmodpkg command, as in the following example:
# cmforceconcl cmrunpkg -n node3 Pkg1
CAUTION: When using the cmforceconcl command, ensure that the other cluster is not running
the package. Failure to do this might result in the package running in both clusters, which causes
data corruption.
Adding or Removing a Node from a Cluster
To add a node or to remove a node from Continentalclusters, use the following procedure:
1. Halt any monitor packages that are running.
# cmhaltpkg ccmonpkg
2. Add or remove the node in a cluster by editing the Serviceguard cluster configuration file and
applying the configuration.
# cmapplyconf -C cluster.config
3. Edit the Continentalclusters configuration ASCII file to add or remove the node in the cluster.
42 Administering Continentalclusters