Configuring HP Serviceguard Toolkit for Oracle Data Guard

Figure 4 shows a Data Guard setup in an EDC environment. Both the primary and standby databases

are configured as single instance Serviceguard failover packages inside the EDC. All the four nodes

are present inside the same Serviceguard cluster. Failover from Site A to Site B and vice versa is

not allowed.

When Site A goes down, the role of Standby on Site B has to be manually changed to primary, since

the role transitions will not be supported in the first release.

Metrocluster in Continentalclusters environment

Figure 5: Single-instance Data Guard setup in a Continentalclusters environment where the Primary Cluster is configured as a

Metroclusters

Figure 5 describes a Continentalclusters setup with two clusters spread over a total of three different

sites. The Primary Cluster is configured as a Metrocluster spread over two different sites that are

geographically dispersed within the confines of a metropolitan area. The Recovery Cluster is

configured on the third site as a Serviceguard cluster.

The primary database of Data Guard setup is configured as a Primary package in the Primary Cluster

(Metrocluster instance). The Primary Cluster has two data centers (sites), each of which have storage

array for storing the data. Metrocluster enables data written to the primary site to be replicated to the

recovery site and hence the primary database instance can failover to any node within the Primary

Cluster.

Continentalcluster

Primary Cluster

( Metrocluster )

Node

Data Center 1

(

Primary site

)

Data Center 2

(

Recovery site

)

Primary

package

Primary

Data replication in Metrocluster

Recovery Cluster

(

Third site

)

Data Receiver

package

Standby

Primary DB

Standby

Recovery

package

Node