Components of SADTA

This section describes the components of SADTA. Following are the components of this feature:

•“Site” (page 338)

•“Oracle Clusterware Sub-cluster” (page 339)

•“Cluster File System and Cluster Volume Manager Sub-clusters” (page 339)

•“Complex Workload Redundant Configuration” (page 340)

•“Site Controller Package” (page 341)

•“Site Safety Latch” (page 344)

Site

Site, in SADTA, is a collection of Metrocluster nodes in the same location that are connected to the same disk array. The site information is configured in the cluster configuration file. Sub-clusters, such as Oracle Clusterware or SG SMS Cluster File System, are formed using this site information.

The Serviceguard cluster configuration file includes the following new attributes to define sites:

•SITE_NAME

To define a unique name for a site in the cluster.

•SITE

To associate a node to a site.

Specify a site using this attribute for the node.

Following is a sample of the site definition in a Serviceguard cluster configuration file:

SITE_NAME san_francisco SITE_NAME san_jose NODE_NAME SFO_1

SITE san_francisco

...

NODE_NAME SFO_2 SITE san_francisco

...

NODE_NAME SJC_1 SITE san_jose

...

NODE_NAME SJC_2 SITE san_jose

When sites are configured in a cluster, the cmviewcl command lists the cluster nodes information according to each site, starting with the site name. You can also use the cmviewcl -Scommand to view information that is specific to a site.

For example:

# cmviewcl -S san_francisco

NODE

STATUS

STATE

SFO_1

up

running

SFO_2

up

running

MULTI_NODE_PACKAGES

 

 

 

PACKAGE

STATUS

STATE

AUTO_RUN

SYSTEM

SG-CFS-pkg

up

running

enabled

yes

sfo_crs_dg

up

running

enabled

no

sfo_crs_mp

up

running

enabled

no

sfo_hrdbflash_dg up

running

enabled

no

sfo_hrdbflash_mp up

running

enabled

no

sfo_crs

up

running

enabled

no

sfo_hrdb_dg

up

running

enabled

no

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