Overview of Solution for Metrocluster with 3PAR Remote Copy
Figure 53 depicts applications deployed in a Metrocluster with 3PAR Remote Copy environment. A Metrocluster is configured with the nodes at Site1 and Site2. When Site1 and Site2 form a Metrocluster, a third location is required where Quorum Server or arbitrator nodes must be configured. There is a 3PAR storage system at each site and they are connected to each other through Remote Copy links.
Figure 53 Sample Configuration of Metrocluster with 3PAR Remote Copy
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. Under normal circumstances 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
For each application, synchronous replication is configured to replicate data between the two sites using Remote Copy volume 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 1 as its DC1 while some other applications can have Site 2 as its DC1. Figure 53 depicts an example of two applications distributed in a Metrocluster with 3PAR Remote Copy environment balancing the server and replication load. In this example, Site1 is the primary site or DC1 for application A, and recovery site or DC2 for application B. Site2 is the primary site or DC1 for application B, and recovery site or DC2 for application A.
Overview of HP 3PAR Remote Copy Concepts
The 3PAR storage systems are configured for use in data replication from one 3PAR storage system unit to another. This type of physical data replication is a part of the Metrocluster with 3PAR Remote
Overview of Solution for Metrocluster with 3PAR Remote Copy 311