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

sfo_hrdb_mp up running enabled no
sfo_hrdb up running enabled no
Oracle Clusterware Sub-cluster
Oracle Clusterware is layered above the Serviceguard cluster membership. In SADTA, the Oracle
Clusterware sub-cluster is formed with membership exclusively from a set of nodes in an underlying
site definition in the Serviceguard cluster.
The Oracle Clusterware sub-clusters are installed and configured separately at each site using the
Oracle Universal Installer. While installing and configuring the Oracle Clusterware sub-cluster,
only nodes that belong to the respective site must be selected. At each sub-cluster, the Oracle
Clusterware daemons are configured as MNP packages using the SGeRAC toolkit.
The Oracle Cluster Registry (OCR) and Voting disk storage for an Oracle Clusterware sub-cluster
must not be replicated between the sites.
In SGeRAC configurations, Oracle Clusterware heartbeat network (CSS heartbeat) can be configured
on a network different from the Serviceguard heartbeat network. In such configurations, a separate
MNP package should be configured to monitor the Oracle Clusterware heartbeat network. Using
the CLUSTER_INTERCONNECT_SUBNET parameter, the Oracle Clusterware MNP must be
configured to be dependent on this package. For more information, see Chapter 2 of the Using
Serviceguard Extension for RAC manual, available at http://www.hp.com/go/
hpux-serviceguard-docs.
When configuring Oracle Clusterware heartbeat networks as said above in Metrocluster for RAC,
SGeRAC sub clusters at each site should have their own MNP package to monitor the Oracle
clusterware heartbeat network in their site. This Oracle Clusterware MNP package at each site
should be configured to depend on the MNP package that is monitoring the Oracle Clusterware
heartbeat network on their site.
An Oracle Clusterware sub-cluster at one site can be started and stopped independently of the
Oracle Clusterware sub-cluster on the other site. The Oracle Clusterware sub-cluster is a common
infrastructure for all Oracle RAC databases configured at the site. Multiple RAC databases local
to a site can be created and registered with the Oracle Clusterware sub-cluster of the site.
NOTE: The Oracle Clusterware sub-cluster functionality is supported only in a Metrocluster
environment that uses SGeRAC and requires the underlying Serviceguard cluster configuration to
have the sites defined appropriately.
Cluster File System and Cluster Volume Manager Sub-clusters
Complex workloads can use Cluster File System (CFS) or Cluster Volume Manager (CVM) for host
storage management. CFS can be configured only using HP Serviceguard Storage Management
Suite (SG SMS). CVM can be configured using either HP SG SMS or VERITAS Cluster Volume
Manager software.
In SADTA, CFS or CVM software can be used to form sub-clusters at each site. The Serviceguard
Storage Management Suite (SG SMS) Cluster File System (CFS) is layered above the Serviceguard
membership. The Cluster File System (CFS) sub-cluster is formed with membership from the cluster
nodes in a site as defined in the underlying cluster.
The CFS sub-cluster at a site manages the disks connected to the nodes in that site. In SADTA, a
CFS sub-cluster is present at each site. The CFS sub-clusters at each site have their own namespaces.
As a result, the same Cluster Volume Manager (CVM) disk group name can be used in both of the
sites in a Metrocluster. While the same CVM disk group and CFS filesystem name can be used in
both subcluster, the diskgroup and mountpoint package names must be unique across both
subcluster.
The CFS sub-cluster daemons are packaged in the regular cluster-wide System Multi-node package
(SMNP): SG-CFS-pkg. The SG-CFS-pkg is a single SMNP package configured across both the site
nodes in a Metrocluster. The SMNP package instances form or join the corresponding site CFS
Overview of Site Aware Disaster Tolerant Architecture 339