Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

extension for RAC (SGeRAC) toolkit at each site. The CRS Home must be installed on a file system
that is local to a site. The CRS voting and OCR disks must not be configured for replication.
The RAC database software must be installed at each site in the Metrocluster. Create ASM disk
groups at the nodes in the source site of replication and configure an identical ASM disk groups
on the nodes in the other site. The ASM disk group (ASM DG) must be configured as a Serviceguard
package using the SGeRAC toolkit at each site. The ASM DG package must have dependency on
the CRS package on the site.
Two replicas of the RAC database must be configured; one at source site of the replication and
the other at the destination site of the replication. The database must be created at the nodes in
source site of the replication and database data must be replicated to the nodes in the other site
using HP P6000/EVA Continuous Access replication. An identical RAC database configuration
must be created at the nodes in other site,The RAC database (RAC DB) must be configured using
the SGeRAC toolkit at each site. The RAC DB package must have dependency on the CRS package
and ASM DG packages on the site.
This section describes the procedures that must be followed to configure SADTA with Oracle RAC
database with ASM. To explain these procedures, consider that the Oracle RAC home directory
is /opt/app/oracle/product/11.1.0/db_1/dbs and the database name is hrdb.
To configure SADTA with Oracle RAC database with ASM:
1. Set up replication.
2. Configure Metrocluster with sites.
3. Install and configure Oracle Clusterware.
4. Install Oracle Real Application Clusters (RAC) software.
5. Create the RAC database with ASM:
a. Configure ASM disk group.
b. Configure SGeRAC Toolkit Packages for the ASM disk group.
c. Create the RAC database using the Oracle Database Configuration Assistant.
d. Configure and test the RAC MNP stack at the source disk site.
e. Halt the RAC database at the source disk site.
6. Configure the identical ASM disk group at the remote site.
This step is required only for Oracle 11g R1.
7. Setup the identical RAC database at the remote site.
8. Configure the Site Controller Package.
9. Configure the Site Safety Latch dependencies.
10. Start the Disaster Tolerant RAC Database in the Metrocluster.
Setting up replication
The procedure for setting up replication is identical to the procedure for setting up replication to
configure Oracle RAC with SADTA. For more information on setting up replication in SADTA for
configuring Oracle RAC database with ASM, see “Setting up replication” (page 104).
Configuring Metrocluster with sites
The procedure for configuring Metrocluster with sites for Oracle RAC database with ASM is identical
to the procedure for configuring Oracle RAC with SADTA. For more information on configuring
Metrocluster with sites for SADTA, see “Configuring Metrocluster with sites” (page 104).
Installing and configuring Oracle clusterware
After setting up replication in your environment and configuring Metrocluster, you must install
Oracle Clusterware. Use the Oracle Universal Installer to install and configure the Oracle
Clusterware. SADTA requires two Oracle Clusterware sub-clusters, one at each site, therefore you
must install and configure Oracle Clusterware twice in the Serviceguard cluster. When you install
Oracle Clusterware at a site, the sub-cluster installation is confined to a site and the Clusterware
storage is not replicated. As a result, Oracle Clusterware must be installed on a local file system
120 Configuring Oracle RAC in SADTA