Configuring global clustering
You can configure global clustering in one of the following ways:
Before you configure global clustering, review the following requirements:
-
Cluster names on the primary and secondary sites must be unique.
-
Node and resource names must be unique within a cluster but not across clusters.
-
Each cluster requires a virtual IP address associated with the cluster. The VCS installation and creation of the ClusterService group typically involves defining this IP address. If you did not configure the ClusterService group when you installed SF Oracle RAC, configure it when you configure global clustering.
-
One WAN (Wide Area Network) heartbeat must travel between clusters, assuming each cluster has the means to monitor the health of the remote cluster. Configure the heartbeat resource manually.
-
All oracle user and group IDs must be the same on all nodes.
-
The Oracle database, which VVR replicates from the storage on the primary site to the secondary site, must be defined in a global group having the same name on each cluster. Each resource in the group may differ from cluster to cluster, but clients redirected to a remote cluster after a wide-area failover must see the same application as the one in the primary cluster.
See the Veritas Cluster Server User's Guide for complete details on global clustering.
Modifying the global clustering configuration using the wizard
The global clustering wizard completes the following tasks:
-
Validates the ability of the current configuration to support a global cluster environment.
-
Creates the components that enable the separate clusters, each of which contains a different set of GAB memberships, to connect and operate as a single unit.
-
Creates the ClusterService group, or updates an existing ClusterService group.
Run the global clustering configuration wizard on each of the clusters; you must have the global clustering license in place on each node in the cluster.
To use the global clustering wizard
-
On a node in the primary site, start the global clustering configuration wizard:
# /opt/VRTSvcs/bin/gcoconfig
-
After discovering the NIC devices on the local node, specify or confirm the device for the cluster joining the global cluster environment.
-
Indicate whether the NIC you entered is for all cluster nodes. If you enter n, enter the names of NICs on each node.
-
Enter or confirm the virtual IP address for the local cluster.
-
When the wizard discovers the net mask associated with the virtual IP address, accept the discovered value or enter another value.
With NIC and IP address values configured, the wizard creates a ClusterService group or updates an existing one. After modifying the VCS configuration file, the wizard brings the group online.
-
Perform through step 1 through step 5 on the secondary cluster.
Modifying the global clustering configuration using the main.cf
Edit the main.cf file to specify the virtual IP address for the local cluster and define the ClusterService group for the local cluster.
The example global clustering configuration shows the rac_cluster101 cluster on the primary site. The additions to the configuration appear in bold text.
include "types.cf"
include "CFSTypes.cf"
include "CVMTypes.cf"
include "OracleTypes.cf"
include "VVRTypes.cf"
cluster rac_cluster101 (
UserNames = { admin = "cDRpdxPmHpzS." }
ClusterAddress = "10.10.10.101"
Administrators = { admin }
CounterInterval = 5
UseFence = SCSI3
)
system galaxy (
)
system nebula (
)
group ClusterService (
SystemList = { galaxy = 0, nebula = 0 }
AutoStartList = { galaxy, nebula }
OnlineRetryLimit = 3
OnlineRetryInterval = 120
)
Application wac (
StartProgram = "/opt/VRTSvcs/bin/wacstart"
StopProgram = "/opt/VRTSvcs/bin/wacstop"
MonitorProcesses = "/opt/VRTSvcs/bin/wac" }
RestartLimit = 3
)
IP gcoip (
Device =lan0
Address = "10.10.10.101"
NetMask = "255.255.240.0"
)
NIC csgnic (
Device =lan0
)
gcoip requires csgnic
wac requires gcoip
.
.
.
group cvm (
.
.
.
