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

“CurrentContinentalclustersConfigFileName” if -F is not specified. If you want
to edit the new configuration file, do not use the -a option. If the option -a is specified, the
new configuration is applied automatically.
3. If option -a is specified with cmswitchconcl in step 2, skip this step. Otherwise manually
apply the new Continentalclusters configuration.
If the -F option is specified in step 2:
# cmapplyconcl -v -c newContinentalclustersConfigFileName
If the -F option is not specified in step 2:
# cmapplyconcl -v -c CurrentContinentalcusterConfigFileName
4. Restart the monitor packages on every cluster.
# cmmodpkg -e ccmonpkg
5. View the status of the Continentalclusters.
# cmviewconcl
The cmswitchconcl command is also used to switch the package role of a recovery group. If
only a subset of the primary packages will remain running on the surviving (recovery) cluster, a
new option -g is provided with the cmswitchconclcommand. This option reconfigures the roles
of the packages of a recovery group and helps retain recovery protection after a failover.
Usage of the option -g (recovery group based role switch reconfiguration) is the same as the one
for -c(cluster based role switch reconfiguration). The options -c and -g of the cmswitchconcl
command are mutually exclusive.
# cmswitchconcl \
-C currentContinentalclustersConfigFileName \
-g RecoverGroupName \
[-a] [-F NewContinentalclustersConfigFileName]
Creating a new primary cluster
After creating a new cluster, restore the critical applications to the new cluster and restore the
original recovery cluster to act as the recovery cluster for the newly created primary cluster. To do
this:
1. Configure the new cluster as a Serviceguard cluster. Use the cmviewcl command on the
surviving cluster and compare the results to the new cluster configuration. Correct any
inconsistencies on the new cluster.
2. Halt the monitor package on the original recovery cluster.
# cmhaltpkg ccmonpkg
3. Edit the Continentalclusters configuration file to replace the data from the old failed cluster
with data from the new cluster. Verify and apply the Continentalclusters configuration.
# cmcheckconcl -v -C cmconcl.config
# cmapplyconcl -v -C cmconcl.config
4. Do the following for every recovery group where the new cluster will run the primary package.
a. Synchronize the data from the disks on the surviving recovery cluster to the disks on the
new cluster.
b. To minimize application down time, start the primary package on the newly created
cluster before resynchronizing the data of the next recovery group.
5. If the new cluster acts as a recovery cluster for any recovery group, create a monitor package
for the new cluster.
Apply the configuration of the new monitor package.
Creating a new primary cluster 29