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

Migrating to Continentalclusters A.08.00
Continentalclusters version A.08.00 includes enhanced features and capabilities, such as support
for modular packages, IPv6 support, and a secure communication protocol for inter-cluster
operations. HP recommends that you migrate Continentalclusters to the latest version to obtain the
benefits of these features. Upgrading to Continentalclusters A.08.00 requires re-applying the
Continentalclusters configuration.
IMPORTANT: Only configurations using Continentalclusters software version A.06.00 or higher
can be upgraded to Continentalclusters software version A.08.00. For configurations using versions
earlier than A.06.00 must necessarily upgrade to version A.08.00 before migrating to
Continentalclusters version A.08.00.
Complete the following steps to migrate to Continentalclusters A.08.00:
1. Set up the secure communication environment.
For more information on setting up the SSH environment for Continentalclusters, see “Setting
up Security with Continentalclusters Version A.08.00” (page 60).
2. Halt the monitor package.
# cmhaltpkg ccmonpkg
3. Install Continentalclusters A.08.00 using the swinstall command on all nodes of the cluster.
4. Verify the Continentalclusters configuration (text file) file that was used to create this
Continentalclusters configuration.
# cmcheckconcl -v -C cmconcl.config
5. Apply the same Continentalclusters configuration file used in the previous step.
# cmapplyconcl -v -C cmconcl.config
6. Start the monitor package.
# cmrunpkg ccmonpkg
7. Verify the configuration and the status of the cluster.
# cmviewconcl
Testing the Continentalclusters
This section presents some test procedures and scenarios. Some scenarios presume certain
configurations that may not apply to all environments. Additionally, these tests do not eliminate
the need to perform standard Serviceguard testing for each cluster individually.
CAUTION: Data and system corruption can occur as a result of testing. System and data backups
should always be done prior to testing.
Testing Individual Packages
Use procedures like the following to test individual packages:
1. Use the cmhaltpkg command to shut down 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 using a mechanism that tests network connectivity.
5. Perform read-only actions to verify that the application is running appropriately.
6. Shut down the application on the recovery cluster using the cmhaltpkg command.
92 Designing Continentalclusters