Building Disaster Recovery Serviceguard Solutions Using Continentalclusters for Linux B.01.00.00

1. Halt all the monitor packages if running.
# cmhaltpkg ccmonpkg
2. Verify the Continentalclusters configuration.
# cmcheckconcl -v -C cmconcl.config
This command verifies whether all the parameters are within range, all the fields are filled,
and the entries (such as NODE_NAME) are valid.
3. Distribute the Continentalclusters configuration information to all the nodes in the
Continentalclusters.
# cmapplyconcl -v -C cmconcl.config
After the configuration is applied, a package named ccconfpkg is automatically created.
This package is used to store the Continentalclusters configuration data to all the nodes in the
cluster. This package is internally managed by Continentalclusters.
NOTE: It is not required to run the ccconfpkg package in the primary or recovery cluster
for proper Continentalclusters operation. This special package is displayed with Serviceguard
status commands, such as cmviewcl. Cluster administrators must not attempt to modify,
delete, start, or stop this package using Serviceguard commands. This package is automatically
deleted from all the clusters when the Continentalclusters configuration is deleted using the
cmdeleteconcl command.
Starting the Continentalclusters monitor package
When you start the monitoring package, the recovery clusters are enabled to monitor the primary
clusters. Before doing this, ensure that the configured primary packages are running normally. If
logical data replication is configured, ensure that the data receiver and data sender packages are
running properly.
If physical data replication is being used, ensure that it is operational.
On every monitoring cluster start the monitor package.
# cmmodpkg -e ccmonpkg
After the monitor package is started, a log file /var/adm/cmconcl/logs/cmclsentryd.log
is created on the node where the package is running, to record the Continentalclusters monitoring
activities. HP recommends that this log file be archived or cleaned up periodically.
Testing the Continentalclusters
This section presents some test procedures and scenarios. You can run the testing procedures as
applicable to your environment. In addition, you must perform the standard Serviceguard testing
individually on each cluster.
CAUTION: Testing can result in data corruption. Hence, always backup data before testing.
Testing individual packages
To test individual packages:
1. Use the cmhaltpkg command to shutdown the package on the primary cluster that corresponds
to the package to be tested on the recovery cluster.
2. Do not switch any users to the recovery cluster. The application must be inaccessible to users
during this test.
3. Start up the package to be tested on the recovery cluster using the cmrunpkg command.
4. Access the application manually by using a mechanism that tests network connectivity.
5. Perform read-only actions to verify that the application is running properly.
Starting the Continentalclusters monitor package 21