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

CFS file system at the host for database storage management. As the underlying Serviceguard
cluster is configured with the site, there are two CFS sub-clusters; one at the San Francisco site with
membership from SFO_1 and SFO_2 nodes and the other at the San Jose site with membership
from SJC_1 and SJC_2 nodes.
Figure 23 Sample configuration
Site safety
latch
SiteA_hrdb_dg
Site A
Node 1
Disk Array
Node 2
Router Router
Node 3 Node 4
Site B
Disk Array
hrdb_dg
hrdb_dg
SiteA_hrb
SiteA_hrdb_mp
hrdb SC
CFS Subcluster
SiteB_hrb
SiteB_hrdb_mp
SiteB_hrdb_dgSiteA_hrdb_dg
CFS Subcluster
Active Inactive
To configure SADTA, two CRS sub-clusters; one at the Site A and the other at the Site B:
1. Install the Oracle Clusterware software at each site in the Metrocluster.
2. Configure the CRS daemons as a Service guard package using SGeRAC toolkit.
3. Install CRS HOme on a file system that is local to a site.
NOTE: The CRS voting and OCR disks must not be configured for replication.
Table 17 lists the CRS packages and other resources that form the CRS sub-cluster at each site.
Table 17 CRS sub-clusters configuration in the Metrocluster
Site BSite ASite
sjc_crssfo_crsCRS Cluster Name
SJC_1 and SJC_2SFO_1 and SFO_2Members
sjc_crssfo_crsCRS MNP
sjc_crs_icsfo_crs_icCRS Interconnect MNP
/opt/crs/oracle/product/10.2.0/crs/opt/crs/oracle/product/10.2.0/crsCRS HOME
102 Configuring Oracle RAC in SADTA