Table 27 Additional Validation of Site Controller Packages (continued)

Check the managed and critical

cmapplyconf

Checks if the managed or critical

package types

cmcheckconf [-P/-p]

package type is either multi node or

 

failover.

 

 

 

 

 

Check if the Site values are valid

cmapplyconf

Checks if the site values in this package

 

cmcheckconf [-P/-p]

are the sites that are configured in the

 

cluster configuration.

 

 

 

 

 

Verify if the Site Safety Latch

cmapplyconf

Checks if the Site Controller EMS

dependencies are configured properly

cmcheckconf [-P/-p]

resource dependency is configured on

for a complex workload

 

all the packages that are the foremost

predecessors in the dependency order among the packages that are configured to be managed by the Site Controller Package on both sites.

NOTE: It is recommended that you add the location of the package environment file available in the Site Controller package directory to the list of files in /etc/cmcluster/cmfiles2check.

Configuring Metrocluster for RAC

The Oracle RAC database can be deployed in a Metrocluster environment for disaster tolerance using SADTA. This configuration is referred to as Metrocluster for RAC. In this architecture, a disaster tolerant RAC database can be configured as two RAC databases that are replicas of each other; one at each site of the Metrocluster. At any given time in a Metrocluster, the RAC database at only one site is up and actively services clients while the other RAC database, which is a replica on the remote site, remains passive. The active RAC database data I/O is continuously replicated (synchronously or asynchronously) to the remote site using physical data replication technologies, such as Continuous Access with EVA, or Continuous Access P9000 or XP, or EMC SRDF.

When the active RAC database fails, or when the site hosting the active RAC database is lost in a disaster, Metrocluster automatically initiates a site failover for the RAC database. A Metrocluster site failover activates the passive database configuration at the remote site by starting it using the replicated data in that site. After a successful site failover, the redundant RAC passive database becomes the new active RAC database.

While configuring replicas of the RAC databases within a Metrocluster, it is important that the two sites in the Serviceguard cluster are configured by grouping cluster nodes based on the sites they are located in. If you have CVM or CFS configured in your environment, an SGeRAC-enabled Oracle Clusterware sub-cluster and a Serviceguard Storage Management Suite CFS sub-cluster must be created at each site. Only nodes from the site on which the sub-clusters are created can be members of these clusters.

For every site aware disaster tolerant RAC database, a RAC database must be configured at each site using the Oracle Clusterware sub-cluster of the site. The database at each site uses the CFS sub-cluster file systems created over the local disk of a replicated disk pair.

The RAC database processes, the disk groups, and file systems at each site are configured in a stack of inter-dependent MNP packages. The RAC database processes are packaged using the SGeRAC Toolkit (delivered as part of the SGeRAC product). The CVM DG MNP and CFS MP MNP packages are created using SG SMS commands for the disk groups and cluster file systems that are used to store the database.

For more information on using SG SMS commands to create disk groups and cluster file systems, see the VERITAS Storage Foundation Cluster File System HP Serviceguard Storage Management Suite Extracts document available at http://www.hp.com/go/hpux-serviceguard-docs. Also, see the Serviceguard, SGeRAC, and SMS Compatibility and Feature Matrix and the latest release notes for your version of Serviceguard for up-to-date information about support for CVM and CFS, available at: http://www.hp.com/go/hpux-serviceguard-docs.

360 Designing a Disaster Recovery Solution Using Site Aware Disaster Tolerant Architecture