Designing a Continental Cluster
Switching to the Recovery Packages in Case of Disaster
Chapter 2 107
This should only be used after positive confirmation from the remote site.
In a multiple recovery pair configuration where more than one primary
cluster is sharing the same recovery cluster, running cmrecovercl
without any option will attempt to recover packages for all of the
recovery groups of the configured primary clusters. Recovery can also be
done in this multiple recovery pair case on a per cluster basis by using
option -c.
# cmrecovercl -c <PrimaryClusterName>
If the monitored cluster comes back up following an alert or alarm, but it
is certain that the primary packages cannot start (say, because of
damage to the disks on the primary site), then use a special procedure to
initiate recovery:
1. Use the cmhaltcl command to halt the primary cluster.
2. Wait for the monitor to send an alert.
3. Use cmrecovercl -f to perform recovery.
After the cmrecovercl command is issued, Continentalclusters displays
a warning message, such as the following and prompts for a verification
that recovery should proceed (the names “LAcluster” and “NYcluster” are
examples):
WARNING: This command will take over for the primary cluster
“LAcluster”
by starting the recovery package on the recovery cluster
“NYcluster”.
You must follow your site disaster recovery procedure
to ensure that the primary packages on “LAcluster” are not
running
and that recovery on “NYcluster” is necessary. Continuing
with this command while the applications are running on the
primary cluster may result in data corruption.
Are you sure that the primary packages are not running and will
not come back, and are you certain that you want to start the
recovery packages? [Y/N]
Reply “Y” to proceed only if you are certain that recovery should take
place. After replying “Y”, a group of messages will appear as shown
below.