HP P6000 Continuous Access Implementation Guide (T3680-96431, August 2012)

10. Dual-controller arrays4. Management server
11. Cluster site5. Hosts
6. Host I/O and replication fabric—blue
HP Metrocluster Continuous Access
HP P6000 Continuous Access supports a ServiceGuard cluster running on HP-UX 11i v1 or HP-UX
11i v2 Update 2. Also known as HP-UX Metrocluster Continuous Access, this configuration has
half the cluster in each of two data centers and uses HP P6000 Continuous Access to replicate
data between the data centers. In the event of a fault, failure, or disaster, HP-UX Metrocluster
Continuous Access automatically reconfigures the destination DR group. This allows automatic
failover of ServiceGuard application packages between local and remote data centers. For more
information about HP-UX Metrocluster Continuous Access EVA, see the HP website:
http://h71028.www7.hp.com/enterprise/cache/4171-0-0-0-121.html
HP Continentalcluster
HP P6000 Continuous Access supports HP Continentalcluster on HP-UX 11i v1 and HP-UX 11i v2
Update 2 that is spread across separate data centers at unlimited distances.
In this configuration, HP P6000 Continuous Access is used to replicate data from one site (where
the primary cluster resides) to the other site (where the recovery cluster resides). Upon primary
cluster failure, HP Continentalcluster fails over the ServiceGuard application packages from the
primary cluster to the recovery cluster.
Reduced-availability configurations
IMPORTANT: The following reduced-availability configurations are not recommended for
production environments.
The following configurations are supported primarily to reduce the cost of test and development
configurations. They are not recommended for production environments. Because they have one
or more SPOFs, they do not offer the same level of disaster tolerance and/or high availability as
described in “Basic dual-fabric configuration” (page 23).
Single-fabric configuration
The single-fabric HP P6000 Continuous Access solution is designed for small, entry-level tests or
proof-of-concept demonstrations where some distance is needed between each of the two switches
in the solution. This solution can also be used for producing copies of data needed for data
migration or data mining, but is not recommended for ongoing production due to multiple SPOFs.
Fabric zoning is required to isolate hosts, as documented in the HP SAN Design Reference Guide.
The two switches share one intersite link, leaving the remaining ports for hosts, array controllers,
and a management server. For example, if a 16-port switch is being used, the remaining 15 ports
support up to:
• Four hosts, one array, and one management server
• Two hosts, two arrays, and one management server
Figure 7 (page 28) shows a single-fabric configuration. Any supported fabric topology described
in the HP SAN Design Reference Guide can be used. All intersite links supported in the basic
remote replication configuration are also supported in the single-fabric configuration. This means
that the intersite link can be direct fiber, a single WDM wavelength, or a single FCIP link.
Reduced-availability configurations 27