Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access EVA
Completing and Running a Continental Cluster Solution with Continuous Access EVA
Chapter 4 279
NOTE The monitor package for a cluster checks the status of the other
cluster and issues alerts and alarms, as defined in the
Continentalclusters configuration file, based on the other cluster’s
status.
8. Check /var/adm/syslog/syslog.log for messages. Also check the
ccmonpkg package log file.
9. Start the primary packages on the primary cluster using cmrunpkg.
Test local failover within the primary cluster.
10. View the status of the continental cluster primary and recovery
clusters, including configured event data.
# cmviewconcl -v
The continental cluster is now ready for testing. See “Testing the
Continental Cluster” on page 101.
Switching to the Recovery Cluster in Case of Disaster
It is vital the administrator verify that recovery is needed after receiving
a cluster alert or alarm. Network failures may produce false alarms.
After validating a failure, start the recovery process using the
cmrecovercl [-f] command. Note the following:
• During an alert, the cmrecovercl will not start the recovery packages
unless the -f option is used.
• During an alarm, the cmrecovercl will start the recovery packages
without the -f option.
• When there is neither an alert nor an alarm condition, cmrecovercl
cannot start the recovery packages on the recovery cluster. This
condition applies not only when no alert or alarm was issued, but
also applies to the situation where there was an alert or alarm, but
the primary cluster recovered and its current status is Up.