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

is used and some node has configuration files for
Continentalclusters with a different name, you are
prompted to indicate whether to proceed with deleting
the configuration on that node.
cmforceconcl
ServiceguardPackageEnableCommand
The command is used to force a Continentalclusters package
to start. It allows a package to run even if the status of a
remote package in the recovery group is unknown, which
indicates that the software will not determine the status of
the remote package.
ServiceguardPackageEnableCommand is either a
cmrunpkg or cmmodpkg command.
cmqueryconcl filename The command cmqueryconcl creates a template ASCII
Continentalclusters configuration file. The ASCII file must be
customized for a specific Continentalclusters environment.
After customization, this file must be verified using the
cmcheckconcl command and distributed by using the
cmapplyconcl command. If an ASCII file is not provided,
output is directed to the stdout. This command must be
run as the first step in preparing for Continentalclusters
configuration.
Options are:
-C filename Declares an alternate location for the
configuration file.
cmrecovercl [-f] This command performs the recovery actions necessary to
start the recovery groups on the current cluster. Care must
be taken before running this command. It is important to
contact the primary cluster site to determine whether recovery
is necessary, before running this command.
This command performs recovery actions only for recovery
groups that are out of the maintenance mode (that is,
enabled). If the specified recovery group for -g option is in
maintenance mode, the command exits without recovering
it. When the -c option is used; the command skips
recovering recovery groups that are in the maintenance
mode.
This command can be run from any node on the recovery
cluster. This command first connects to the Continentalclusters
monitoring package running on the recovery cluster. This
node might be a different cluster than where the
cmrecovercl command is being run. The cmrecovercl
command connects to the monitoring package to verify that
the primary cluster is in an Unreachable or Down state. If
the primary cluster is reachable and the cluster is Up, this
command fails. Next, the data receiver packages on the
recovery cluster (if any) are halted sequentially. Finally, the
recovery packages are started on the recovery cluster. The
recovery packages are started by enabling package
switching globally (cmmodpkg -e) for every package. This
causes the package to be started on the first available node
within the recovery cluster. You can run the cmrecovercl
command on a recovery cluster. The cmrecovercl
command fails if there has not been sufficient time since the
primary cluster became unreachable. This command is only
enabled after the time as configured via CLUSTER_ALARM
parameters is reached. After a cluster alarm is triggered,
60 Continentalclusters Command and Daemon Reference