![](/images/backgrounds/286000/hp-serviceguard-metrocluster-users-guide-66984523x1.png)
1 Designing a Metrocluster
This chapter describes the configuration and management of a basic metropolitan cluster through the following topics:
•Designing a Disaster Recovery Architecture for use with Metrocluster Products
•Two Data Centers and Third Location with Arbitrator(s)
•Package Configuration Worksheet
•Cluster Configuration Worksheet
In addition, this chapter outlines the general characteristics of the metropolitan cluster solutions that are provided with use of the following products:
•Metrocluster with Continuous Access for P9000 and XP
•Metrocluster with Continuous Access EVA
•Metrocluster with EMC SRDF
•Metrocluster with 3PAR Remote Copy
A separate chapter details the configuration process for each storage solution. For additional information, refer to the Release Notes for your metropolitan cluster product and the documentation for your storage solution.
Designing a Disaster Recovery Architecture for use with Metrocluster Products
HP Metrocluster is a disaster tolerance solution for HP 9000 and HP Integrity systems running
NOTE: The maximum supported distance between Metrocluster nodes depends on the distance achievable while ensuring the replication technology latency requirements and the Serviceguard network latency requirements.
HP Metrocluster supports the following configurations:
•A single data center without arbitrators (not disaster tolerant.)
•Two data centers and a third location architecture with one or two arbitrator systems or a quorum server system. See Figure 1 (page 25).
Specifically for disaster tolerance, Serviceguard clusters or data centers can also be configured on different subnets. Such configurations provide improved scalability as operators can configure.
Designing a Disaster Recovery Architecture for use with Metrocluster Products | 23 |