Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

7. Change each cluster’s state to test that the monitor running on the monitoring cluster will detect
the change in status and send notification.
8. View the status of the Continentalclusters primary and recovery clusters, including configured
event data.
# cmviewconcl -v
CAUTION: Never issue the cmrunpkg command for a recovery package when Continentalclusters
is enabled, because there is no guaranteed way of preventing a package that is running on one
cluster from running on the other cluster if the package is started using this command. The potential
for data corruption is great.
Chapters 3, 4 and 5 contain additional suggestions on testing the data replication and package
configuration.
Documenting the Recovery Procedure
Once everything is configured and the Continentalclusters monitor is running, it is necessary to
define your recovery procedure and train the administrators and operators at both sites. The
checklist in Figure 20 is an example of to document the recovery procedure.
Figure 20 Recovery Checklist
Reviewing the Recovery Procedure
Using the checklist described in the previous section, step through the recovery procedure to make
sure that all necessary steps are included. If possible, create simulated failures to test the alert and
alarm scenarios coded in the Continentalclusters configuration file.
Building the Continentalclusters Configuration 91