Configuring HP Serviceguard Toolkit for Oracle Data Guard

9
In Figure 3, Metrocluster is configured with two data centers: one as the primary site and the other as
the recovery site. The Data Guard primary database instance is configured in Data Center 1 such 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 will be brought up on any one node in
Data Center 1 while other nodes in the data center will serve as backup nodes for that instance.
Array-based replication technology enables the data written to the storage array in Data Center 1
to be replicated to the storage array located in Data Center 2. It is not necessary to configure
the standby database in Data Center 2 because the data replication is taken care of by the
Metrocluster solution.
The standby database instance is configured at a third location (say site 3), which is not configured
within the Metrocluster environment. The third location is a separate Serviceguard cluster with two
nodes and a shared disk. The standby database instance will be brought up on any one node in the
third location, and the database and the archived logs will be located on the shared disk. If high
availability is not desired for the standby database then the third location need not be configured in a
Serviceguard cluster. In such a situation, there will be only one server at the third location and the
standby database instance has to be brought up manually.
In case of a disaster, if Data Center 1 is down, then the primary database instance will be failed over
to Data Center 2 and will continue to function as a primary database. Since Metrocluster has
achieved data replication from Data Center 1 to Data Center 2, there will not be any problems when
starting the primary database at Data Center 2 using the replicated data from the shared disk. Once
the primary database instance comes up at Data Center 2, it will continue to send the archived logs to
the standby database located at the third location.
Data Guard in EDC environment
Figure 4: ODG in EDC environment in which both the primary and the standby are single-instance databases
EDC
Node
1
Node
2
Node
3
Node
4
Package for
primary DB
Package for
standby DB
Standby
DB
Primary
DB
Site A
Site B