Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Designing Disaster Tolerant High Availability Clusters:

Chapter 5 Building a Continental Cluster

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Table of Contents

Understanding Continental Cluster Concepts
Mutual Recovery Configuration
Application Recovery in a Continental Cluster
Monitoring over a Wide Area Network
Cluster Events
Interpreting the Significance of Cluster Events
How Notifications Work
Alerts
Alarms
Creating Notifications for Failure Events
Creating Notifications for Events that Indicate a Return of Service
Performing Cluster Recovery
Notes on Packages in a Continental Cluster
How MC/ServiceGuard commands work in a ContinentalCluster
Designing a Disaster Tolerant Architecture for use with ContinentalClusters
Mutual Recovery
MC/ServiceGuard Clusters
Data Replication
Highly Available Wide Area Networking
Data Center Processes
ContinentalClusters Worksheets
Preparing the Clusters
Setting up and Testing Data Replication
Configuring a Cluster without Recovery Packages
Configuring a Cluster with Recovery Packages
Building the ContinentalClusters Configuration
Preparing Security Files
Creating the Monitor Package
Editing the ContinentalClusters Configuration File
Checking and Applying the ContinentalClusters Configuration
Starting the ContinentalClusters Monitor Package
Validating the Configuration
Documenting the Recovery Procedure
Reviewing the Recovery Procedure
Testing the Continental Cluster
Testing Individual Packages
Testing ContinentalClusters Operations
Switching to the Recovery Packages in Case of Disaster
Receiving Notification
Verifying that Recovery is Needed
Using the Recovery Command to Switch All Packages
How the cmrecovercl Command Works
Restoring Disaster Tolerance
Restore Clusters to their Original Roles
Primary Packages Remain on the Surviving Cluster
Newly Created Cluster Will Run Primary Packages
Newly Created Cluster Will Function as Recovery Cluster for All Recovery Groups
Maintaining a Continental Cluster
Adding a Node to a Cluster or Removing a Node from a Cluster
Adding a Package to the Continental Cluster
Removing a Package from the Continental Cluster
Changing Monitoring Definitions
Checking the Status of Clusters, Nodes, and Packages
Reviewing Messages and Log Files
Deleting a Continental Cluster Configuration
Renaming a Continental Cluster
Checking Java Versions

Unlike metropolitan and campus clusters, which have a single-cluster architecture, a continental cluster uses multiple MC/ServiceGuard clusters to provide application recovery over wide areas. Using the ContinentalClusters product, two independently functioning clusters are set up in such a way that in the event of a disaster, one cluster can take over the critical operations formerly carried out by the other cluster.

Disaster tolerance is obtained by eliminating the cluster itself as a single point of failure. This chapter describes the configuration and management of a basic continental cluster through the following topics:

For a description of the cascading failover configuration, see Chapter 8. Refer to Appendixes C and D for additional information on the ContinentalClusters command set and on configuration file parameters.

NOTE: This chapter only briefly addresses data replication, highly available WANs, and site security and communication. Chapters 6 and 7 give details on physical data replication using the HP SureStore E Disk Array XP Series with Continuous Access XP and the EMC Symmetrix with the SRDF facility. Information on logical data replication via the Oracle Standby Database is available from your HP representative. Also see the "White Papers" area on web page http://docs.hp.com/hpux/ha.
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.