Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA P6000 for Linux B.12.00.00

For more information on remote data replication concepts and planning a remote replication
solution, see HP P6000 Continuous Access Implementation Guide available at http://www.hp.com/
support/manual—>storage -> Storage Software -> Storage Replication Software -> HP P6000
Continuous Access Software.
Overview of a Metrocluster with HP P6000 Continuous Access configuration
A Metrocluster is configured with the nodes at Site A and Site B. When Site A and Site B form a
Metrocluster, a third location is required where Quorum Server or arbitrator nodes must be
configured. There is a HP P6000/EVA storage at each site and they are connected to each other
through Continuous Access links.
An application is deployed in a Metrocluster by configuring it at both the sites. The sites are referred
either as DC1 or DC2 for an application, based on their role. Typically, the application runs on
DC1 site which is the primary site. If there is a disaster in DC1 site, the application automatically
fails over to the recovery site referred as DC2 site.
NOTE: DC1 and DC2 are application-specific roles of a site.
For each application, either synchronous or enhanced asynchronous mode replication is configured
to replicate data between the two sites using DR group. In a typical configuration, more than one
application is configured to run in a Metrocluster. Depending on the application distribution in a
Metrocluster environment, some applications can have Site A as its DC1 while some other
applications can have Site B as its DC1.
Overview of a Metrocluster with HP P6000 Continuous Access configuration 9