Setting up the Continentalclusters Configuration

The following steps detail the basic procedure for setting up the Continentalclusters configuration file and the monitoring packages on the two clusters. For details on creating and editing the configuration file, see Chapter 2.

1.A secure communication using SSH must be set up for inter-cluster operations. For more information, see section “Setting up Security with Continentalclusters Version A.08.00” (page 60).

2.Copy the modular package template file /opt/cmconcl/scripts/

ccmonpkg_modular.config to the directory /etc/cmcluster/ccmonpkg on a node in each cluster.

#cp /opt/cmconcl/scripts/ccmonpkg_modular.config /etc/cmcluster/ccmonpkg/ccmonpkg.conf

3.Apply the monitor package in both the clusters.

#cmapplyconf -P /etc/cmcluster/ccmonpkg/ccmonpkg.config

4.Generate the Continentalclusters configuration.

#cmqueryconcl -C cmconcl.config

5.Edit the configuration file cmconcl.config with the names of the two clusters, the nodes in each cluster, the recovery groups and the monitoring definitions. The recovery groups define the primary and recovery packages. When data replication is done using 3PAR Remote Copy, there are no data sender and receiver packages. Define the monitoring parameters, the notification mechanism (OPC, email, console, SNMP, syslog, or tcp) and notification type (alert or alarm) based on the cluster status (unknown, down, up or error). Descriptions for these can be found in the configuration file generated in the previous step.

6.Apply the Continentalclusters configuration file using cmapplyconcl.

#cmapplyconcl -C cmconcl.config

7.Start the monitor package on both clusters.

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 source disk site using cmrunpkg. Test local failover within the source disk site.

10.View the status of the Continentalclusters primary and target disk sites, including configured event data.

#cmviewconcl -v

Switching to the Recovery Cluster in Case of Disaster

It is vital that the administrators verify that recovery is needed after receiving a cluster alert or an alarm. Network failures may produce false alarms. After validating a failure, start the recovery process using the cmrecovercl [-f] command.

328 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy