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 2 Building a Campus Cluster Using FibreChannel and MC/ServiceGuard

Guidelines for Disaster Tolerant Architectures with FibreChannel

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

FibreChannel host adapters make it possible to increase the distance between nodes in an MC/ServiceGuard cluster thus making it possible to design a disaster tolerant architecture for campus or metropolitan clusters. The following configurations are supported:

  • Two data centers using FibreChannel hubs. This architecture can be implemented using a variety of disk arrays. Consult the HP 9000 Servers Configuration Guide (available through your HP representative) for a list of supported HA disks.

  • Two data centers using FibreChannel point-to-point and HP SureStore E Disk Array XP Series or EMC Symmetrix disk arrays.

The two-data-center architecture is based on a standard MC/ServiceGuard configuration with half of the nodes in one data center, and the other half in another data center. Nodes can be located in separate data centers in the same building, or even separate buildings within the limits of FibreChannel technology. FibreChannel has a maximum distance of 500 meters (10 kilometers with long-wave hubs). F/W (Fast/Wide) SCSI only allows a maximum length of 25 meters.

Following are the disaster tolerant architecture requirements for campus clusters:

  • Data centers must be self-contained such that the loss of one data center does not cause the entire cluster to fail. All Single Points of Failure (SPOFs) must be eliminated so that surviving systems continue to run if one or more systems fail.

  • The number of nodes in each data center must be equal.

  • Heartbeat networks between the data centers must be redundant and routed along physically different paths so that the loss of any one data center does not cause the network between surviving data centers to fail. All nodes in the cluster must be connected to the redundant heartbeat network links.

    If you are using FibreChannel technology for the network as well, you must use completely different hardware from that used to connect nodes to mass storage devices. This includes cables, repeaters, hubs, and anything else related to the FibreChannel fabric.

  • Data must be mirrored at the remote site using a product such as MirrorDisk/UX. Data connections must be redundant and routed differently, like heartbeat network cables are. It is recommended to route FibreChannel cables and heartbeat network cables in such a way that no two failures can disable all hearbeat networks and both FibreChannel connections.

  • Data components, e.g. FibreChannel hubs, must be redundant and powered using alternative power sources as described in Chapter 1. All failover nodes must be connected to both mirror copies of the data.

  • Dual cluster lock disks are required, one in each data center. All nodes must be connected to both cluster lock disks. Each cluster lock disk must be on a different FibreChannel arbitrated loop.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.