While Metrocluster provides storage-based data replication across metropolitan distances, organizations often like to build in additional data replicas, either locally or at other data centers. When you perform both storage and ODG replication, it helps to safeguard customer data. ODG protects against logical errors, while storage replication replicates any errors to the other replica. For example, a dropped table.

The integration of ODG with Metrocluster or EDC gives organizations the choice to use storage replication for Oracle and for all other application data.

The primary database can be configured inside a Metrocluster or an Extended Distance Cluster. The standby database can be configured outside the Metrocluster/Extended Distance Cluster as a standalone database or as part of a Serviceguard cluster.

For information about setting up Metrocluster, see the document Designing Disaster Recovery HA Clusters Using Metrocluster and Continentalclusters Manual available at http://www.hp.com/go/ hpux-serviceguard-docs.

Figure 8 Single-instance Data Guard configuration in Metrocluster with standby database residing outside Metrocluster

NOTE: This configuration is supported both in single-instance and RAC environments. For better understanding, the packages in the Figure 8 (page 15) are shown for a single-instance database.

In Figure 8 (page 15), Metrocluster is configured with two data centers; Data Center 1 as the primary site, and Data Center 2 as the recovery site. The Data Guard primary database instance is configured in Data Center 1, so that the archived logs and the primary database reside on the disk that is shared locally between the nodes in that data center. The primary database instance is started on any one node in Data Center 1, while other nodes in the data center are the backup nodes for that instance. The data written to the storage array in Data Center 1 can be replicated to the storage array located in Data Center 2 using array-based replication technology. It is not necessary to configure the standby database in Data Center 2 because the data replication is done by the Metrocluster solution.

The standby database instance is configured at a third location (for example site 3), which is not configured within the Metrocluster environment. The third location is a separate Serviceguard

Supported configuration

15

Page 15
Image 15
HP Serviceguard Toolkits for Database Replication Solutions manual Supported configuration