User's Guide

Table 13 Status of Continentalclusters Packages After Recovery
Recovery ClusterPrimary Cluster
Required
Monitor
Package
Data Receiver
Package
Recovery
Package
Optional
Monitor
Package
Data Sender
Package
Primary
Package
Data Replication
Method
Halted or
Running
Not usedRunningHalted or
Running
Not usedHaltedPhysical—
Symmetrix
Halted or
Running
Not usedRunningHalted or
Running
Not usedHaltedPhysical— P9000
or XP Series
Halted or
Running
Not usedRunningHalted or
Running
Not usedHaltedPhysical—EVA
Series
Halted or
Running
Not usedRunningHalted or
Running
Not usedHaltedPhysical— 3PAR
Remote Copy
Halted or
Running
HaltedRunningHalted or
Running
Not usedHaltedLogical— Oracle
Standby
Database
How the cmrecovercl Command Works
The cmrecovercl command uses the configuration file to loop through each defined recovery
group of a target remote cluster to be recovered. For each recovery group that is not in the
maintenance mode, the command communicates with the monitor package (ccmonpkg) and verifies
that the remote cluster is unreachable or down, then if there is a data replication package it is
halted, and the recovery package is enabled on the Recovery Cluster. The recovery package can
then start up on the local cluster on the appropriate node, as determined by the FAILOVER_POLICY
configured for the package.
The process continues for the next recovery group, even if there are problems with one recovery
group. The command will skip recovery for any recovery group in maintenance mode. After
processing one recovery group, if the command discovers that the local cluster is back up, the
command exits, since the alarm or alert state no longer exists. This process keeps both the primary
and recovery packages from running on the remote cluster and local cluster at the same time,
which would result in data corruption.
NOTE: If the remote cluster comes back up following a cluster event but the primary packages
cannot run, halt the primary cluster with the cmhaltcl command, then issue cmrecovercl with
the -f option.
Forcing a Package to Start
The cmforceconcl command is used 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
to a cmrunpkg and cmmodpkg command.
Under normal circumstances, Continentalclusters will 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 may be lost, and it may 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 this command, ensure that the other cluster is not running the package.
Failure to do this may result in the package running in both clusters, which will cause data
corruption.
Forcing a Package to Start 97