Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Configure RAID Manager in the primary and recovery cluster
For 3DC operations, a package requires three different device groups. For Tri-Link configuration,
a package requires three different device groups: Continuous Access Synchronous or
Continuous Access journal device group between DC1 and DC2, Continuous Access
journal device group between DC1 or DC2 and DC3, and a Delta Resync device group from
either DC1 or DC2 to DC3 depending on where Continuous Access journal pair to DC3 is
configured.
For Multi-Target Bi-Link configuration, a package requires three different device groups:
Continuous Access Synchronous or Continuous Access journal device group
between DC1 and DC2, Continuous Access journal device group between DC1 and DC3,
and a "phantom" device group between DC2 to DC3.
For Multi-Hop Bi-Link configuration, a package requires three different device groups: Continuous
Access Synchronous or Continuous Access journal device group between DC1 and
DC2, Continuous Access journal device group between DC2 and DC3, and a "phantom"
device group between DC1 to DC3.
For information on configuring the RAID Manager configuration files in the primary and recovery
cluster, see “Creating Device Group Pairs” (page 452).
Creating Device Group Pairs
After configuring the Raid Manager configuration files on all nodes in the primary and recovery
cluster, you must create Continuous Access device group pairs. An application configured for an
3DC solution may contain either three or two device group pairs based on Tri-Link or Bi-Link
configuration respectively. An application configured for a 3DC solution with Tri-Link configuration
contains three device group pairs; One Continuous Access Sync or Journal device group pair
between DC1 and DC2, Continuous Access-Journal device group pair, and a Delta Resync device
group pair. An application configured for an Three Data Center solution with Bi-Link configuration
contains two device group pairs; Continuous Access Sync or Journal device group pair between
DC1 and DC2, and Continuous Access-Journal device group pair to DC3. All the device group
pair relations must be established prior to the rest of the configurations and normal package
operations.
For more information on creating device group pairs, see “Creating Device Group Pairs ” (page 437).
Configuring Oracle RAC and the Site Controller Package in the primary cluster
This section describes the following procedures:
1. Setting up Oracle RAC redundantly in the primary cluster
2. Configuring the Site Controller Package in the primary cluster
3. Configuring Site Safety Latch Dependencies in the primary cluster
Setting up Oracle RAC redundantly in the primary cluster
The procedure to create RAC database in Metrocluster is identical to the procedure for creating a
RAC database using SADTA. Complete the procedure described in the section “Configuring Oracle
RAC Database in a Site Aware Disaster Tolerant Architecture” to setup the RAC database in both
sites in the primary cluster. The procedure to configure the Site Controller Package in 3DC solution
is different from that of Metrocluster for RAC. Configure the Site Controller Package in the primary
cluster using the procedure mentioned in the section “Configuring Site Controller Package in the
primary cluster”.
Configuring the Site Controller Package in the primary cluster
A Site Controller Package in the primary cluster must be created using the Metrocluster 3DC primary
module dts/primary_xpca3dc along with the Site Controller module dts/sc.
452 Designing a Three Data Center Disaster Recovery Solution