Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Continental Cluster
Testing the Continental Cluster
Chapter 5 245
Testing the Continental Cluster
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 MC/ServiceGuard testing for each cluster individually.
NOTE 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 you want to test 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.
7. If using physical data replication, do not resync from the recovery
cluster to the primary cluster. Instead, manually issue a command
that will overwrite any changes on the recovery disk array that may
inadvertently have been made.
8. Start the package up on the primary cluster and allow the users to
connect to the application.