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

Table 3 Supported System and Data Center Combinations
Serviceguard VersionData Center CData Center BData Center A
A.11.16 or later1 Arbitrator Node11
A.11.16 or laterQuorum Server System11
A.11.16 or later2 Arbitrator Nodes12
A.11.16 or later2 Arbitrator Nodes21
A.11.16 or later1 Arbitrator Node22
A. 11.16 or later2* Arbitrator Nodes22
A. 11.16 or laterQuorum Server System22
A. 11.16 or later1 Arbitrator Node33
A. 11.16 or later2* Arbitrator Nodes33
A.11.16 or laterQuorum Server System33
A.11.16 or later1 Arbitrator Node44
A.11.16 or later2* Arbitrator Nodes44
A.11.16 or laterQuorum Server System44
A.11.16 or later1 Arbitrator Node55
A.11.16 or later2* Arbitrator Nodes55
A.11.16 or laterQuorum Server System55
A.11.16 or later1 Arbitrator Node66
A.11.16 or later2* Arbitrator Nodes66
A.11.16 or laterQuorum Server System66
A.11.16 or later1 Arbitrator Node77
A.11.16 or later2* Arbitrator Nodes77
A.11.16 or laterQuorum Server System77
A.11.16 or laterQuorum Server System88
* Configurations with two arbitrators are preferred because they provide a greater degree of
availability, especially in cases when a node is down due to a failure or planned maintenance. It
is highly recommended that two arbitrators be configured in Data Center C to allow for planned
downtime in Data Centers A and B.
The following is a list of recommended arbitration methods for Metrocluster solutions in order of
preference:
• 2 arbitrator nodes, where supported
• 1 arbitrator node, where supported
• Quorum Server with APA
• Quorum Server
For more information on Quorum Server, refer to the Serviceguard Quorum Server Release Notes
for HP-UX.
Site Aware Failover Configuration
While configuring a Serviceguard package, the node names are ordered by preference to run the
package. The first node in the list is the primary node for running the package and the subsequent
26 Designing a Metrocluster