Support for Oracle RAC instances means that the RAC instances running
on the primary cluster will be restarted by Continentalclusters on
the recovery cluster to continue serving the clients' databases requests
upon a primary cluster failure. Figure 2-11 “Oracle
RAC Instances in a Continentalclusters Environment” is a sample of Oracle RAC instances running in the Continentalclusters
environment.
As shown in the above example, Oracle RAC instances are configured
to run in Serviceguard packages. The instance packages are running
on the primary cluster and will be recovered on the recovery cluster
upon a primary cluster failure. Figure 2-12 “Sample
Oracle RAC Instances in a Continentalclusters Environment After Failover” shows a recovery using an Oracle RAC configuration after
failover.
Oracle RAC instances are only supported in the Continentalclusters environment
for physical replication using HP StorageWorks Continuous Access
XP, or EMC Symmetrix Remote Data Facility (SRDF) using HP SLVM or Serviceguard
Storage Management Suite using CFS for volume management. Continentalclusters
support for Oracle instances using HP StorageWorks Continuous Access
EVA is supported only with SLVM software.
Continentalclusters Oracle RAC support is available for a
cluster environment configured with only Serviceguard (for example,
the environment running with Oracle 9i), or a cluster environment configured
with Serviceguard plus Oracle Clusterware (for example, the environment
running with Oracle 10g).
Starting with Continentalclusters version A.05.01, recovery
of an Oracle RAC instance in a cluster environment running Serviceguard
and Oracle Clusterware is supported. There is a special configuration
required for the environment running both Oracle Clusterware and Serviceguard/Serviceguard
Extension for RAC (SGeRAC) for the Continentalclusters RAC instance
recovery protection.
For more information refer to the following section, “Serviceguard/Serviceguard
Extension for RAC and Oracle Clusterware Configuration”.
Configuring
the Environment for Continentalclusters to Support Oracle RAC |
 |
In order to enable Continentalclusters support for Oracle
RAC, there needs to be a set of configurations, which include either
Continuous Access XP, or Continuous Access EVA, or EMC SRDF, Oracle
RAC, and Continentalclusters.
To support this feature, Continentalclusters must be configured
with an environment that has physical replication set up using HP StorageWorks
Continuous Access XP, HP StorageWorks Continuous Access EVA or EMC
Symmetrix Remote Data Facility (SRDF) using SLVM or Cluster Volume
Manager (CVM) or Cluster File System (CFS) for volume management.
For more information on specific Oracle RAC configurations that
are supported, refer .
For complete installation and configuration information of
Oracle and HP StorageWorks products, refer to the Oracle RAC and
HP StorageWorks manuals.
describes
configuration information for RAC support of Continentalclusters.
Table 2-8 Supported Continentalclusters and RAC Configuration
| Oracle RAC | Disk Arrays | Volume Managers | Cluster File System | Required Metrocluster |
|---|
Oracle RAC with/without Clusterware | HP StorageWorks XP Series with Continuous Access | HP SLVM Serviceguard Storage Management CVM | Serviceguard Storage Management Suite CFS | Metrocluster with Continuous Access with XP |
| HP StorageWorks EVA series with Continuous Access | HP SLVM Serviceguard Storage Management CVM | Serviceguard Storage Management Suite
CFS | Metrocluster with Continuous Access with EVA |
| EMC Symmetrix series with SRDF | HP SLVM Serviceguard Storage Management CVM | Serviceguard Storage Management Suite CFS | Metrocluster with EMC SRDF version |
Use the following set of procedures to enable Continentalclusters recovery
support for Oracle RAC instances:
Configure either
Continuous Access XP, or Continuous Access EVA or EMC SRDF for data
replication between disk arrays associated with primary and recovery
clusters. For more details, see Chapter 3 “Building
Disaster Tolerant Serviceguard Solutions Using Metrocluster with
Continuous Access XP” Chapter 4 “Building
Disaster Tolerant Serviceguard Solutions Using Metrocluster with
Continuous Access EVA” or Chapter 5 “Building
Disaster Tolerant Serviceguard Solutions Using Metrocluster with
EMC SRDF”
Configure the database storage using one of the
following software:
Shared Logical Volume Manager (SLVM)
Cluster Volume Manager (CVM)
Cluster File Systems (CFS)
You need to configure the SLVM volume groups or CVM disk groups on
the disk arrays to store the Oracle database. Configure the volume
groups or disk groups on both primary and recovery clusters. Ensure
that the volume groups names or disk group names on both clusters
are identical. You must also setup data replication between the
disk arrays associated with primary and recovery clusters.
Only the volume groups or disk groups configured to store
the database must be configured for replication across primary and recovery
clusters. In the environment running with Oracle Clusterware, you
must configure the storage used by Oracle Clusterware to reside
on disks that are not replicated.
If you use CVM or CFS in your environment for storage infrastructure,
you need to complete the following steps at both, primary and recovery
clusters.
Make sure that the primary and recovery
clusters are running.
Configure and start the CFS or CVM multi-node package
using the command cfscluster config -s. When CVM starts, it automatically selects the master
node. This master node is the node from which you must issue the
disk group configuration commands. To determine the master node,
run the following command from any node in the cluster.
# vxdctl -c mode
Create disk groups and mount points. For more information
on creating disk groups and mount points, refer to Using Serviceguard
Extension for RAC User’s Guide.
|
| |
|
 | NOTE: When you use CVM disk groups, Continentalclusters does
not support configuring the CVM disk groups in the RAC instance package
files using the CVM_ACTIVATION_CMD and CVM_DISK_GROUP variables. The instance packages should be configured
to have a dependency with the required CVM disk group multi-node
package. |
|
| |
|
Run the following commands of the CFS scripts to
add and configure the disk groups and file system mount points multi-node
packages (MNP) to the clusters. These multi-node packages manipulate
the disk group, and mount-point activities in the cluster.
cfsdgadm add <disk group name> all=SW
For example:
cfsdgadm add racdgl all=SW
cfsmntadm add <disk group name> <volume name> / <mount point> all=SW
For example:
cfsmntadm add racdgl vol4 /cfs/mntl all=SW
Set the AUTO_RUN flag to NO with the following commands:
cfsdgadm set_autorun <disk group name> NO
cfsmntadm set_autorun < mount point name> NO
Activate the disk group MNP using the following
command:
cfsdgadm activate <diskgroup>
Start the mount point MNP using the following command:
cfsmount <mount point>
|
| |
|
| NOTE: After you configure the disk group and mount point multi-node packages,
you must deactivate the packages on the recovery cluster. During
a recovery process, the cmrecovercl command automatically activates these multi-node packages. |
|
| |
|
Set the access rights for volumes and disk groups
to persistent using the following command:
vxedit -g <Disk Group Name> set user=<User Name> group=<User Group> set mode=<Permissions> <Logical Volumes>
This step is required because when you import disks or volume groups
to the recovery site, the access rights for the imported disks or
volume groups are set to root by default. As a result, the database instances
do not start. To eliminate this behavior, you must set the access
rights to persistent.
Configure Oracle RAC. You need to configure all
the database files to reside on SLVM volume groups, CVM disk groups
or CFS file systems that you have configured in your environment.
Ensure that the configuration of the Oracle RAC instances that must
be recovered in the Continentalclusters environment are identical
on the primary and recovery clusters. For more information on configuring
Oracle RAC, refer to the Oracle RAC installation and configuration user’s
guide.
If you have Oracle Clusterware and Serviceguard running in
your environment, you need to complete certain additional configuration procedures.
For more information on these configuration procedures, see “Serviceguard/Serviceguard
Extension for RAC and Oracle Clusterware Configuration”.
Configure Continentalclusters. For more information
on configuring Continentalclusters, see “Building
the Continentalclusters Configuration”.
Configure Oracle RAC instances in Serviceguard packages. Continentalclusters
supports recovery only for applications running in Serviceguard
packages. In a multiple recovery pair scenario, where more than
one primary cluster share the same recovery cluster, the primary
RAC instance package name must be unique on each primary cluster.
Configure the Oracle RAC instance packages on both primary
and recovery clusters based on the number of RAC instances configured to
run on that cluster. Ensure that the same number of Oracle RAC instances
are configured on both the primary and recovery clusters. This ensures
Continentalclusters recovery protection. Set the AUTO_RUN parameter in the package configuration file to NO.
For details on how to configure an Oracle RAC instance in
a Serviceguard package, refer to the Using Serviceguard
Extension for RAC user’s guide. In the Continentalclusters
environment, you can configure each RAC instance in a failover type
package or you can configure all RAC instances in a single multi-node
package.
Setup the environment file.
Instead of one environment file for each continental cluster application
package, there is only one environment file for each set of Oracle
RAC instance packages accessing the same database. This file can
be located anywhere except the directory where the Oracle RAC instance
package configuration and control files reside. Only one environment
file can reside under one directory. The setup of the file is the
same as what is described in section, “Physical
Data Replication using Special Environment files” of this chapter, with the exception
of the PKGDIR variable.
The value of the PKGDIR variable must be the directory where this environment
file resides.
For specific information on how to setup the environment file,
see Chapter 3 under section, “Configuring
Packages for Disaster Recovery” Chapter
4 under section, “Configuring
Packages for Automatic Disaster Recovery” or
Chapter 5 under section “Configuring
Serviceguard Packages for Automatic Disaster Recovery”.
Be sure to place this environment file in the same path on
all nodes of both the primary and recovery clusters in a recovery
pair. You must name the environment file using your package name
as the prefix. For example, <package name>_xpca.env. You must uncomment all the AUTO variables in the environment
file.
Based on the disk arrays in your environment, refer to the corresponding
chapters of this manual for more information on configuring the
environment file for your storage.
Set up the Continentalclusters Oracle RAC specification
file. The existence of file /etc/cmconcl/ccrac/ccrac.config servers as an enabler for Continentalclusters Oracle
RAC support. A template of this file is available in /opt/cmconcl/scripts directory.
Edit this file to suit your environment. After editing, move
the file to /etc/cmconcl/ccrac/ccrac.config directory on all nodes in the participating clusters.
Use the following steps to set up the file:
Login as root on one node of the primary cluster.
Change to your own directory:
# cd <your own directory>
Copy the file:
# cp /opt/cmconcl/scripts/ccrac.config \ ccrac.config.mycopy
Edit the file ccrac.config.mycopy to fit your environment.
The following parameters need to be edited:
CCRAC_ENV - fully qualified Metrocluster environment file name. This file naming convention as required by the Metrocluster software. It has to be appended with _<DataReplication>.env where <DataReplication> is the name of the data replication scheme being used. Refer to Metrocluster documents for the environment file naming convention.
This parameter is mandatory
CCRAC_SLVM_VGS - SLVM volume groups configured for the device specified in the above environment file for variable DEVICE_GROUP. These are the volume groups used by the associated RAC instance packages. It is important that all of the volume groups configured for the specified DEVICE_GROUP are listed. If only partial of the configured volume groups are listed, the device will not be prepared properly and the storage will result in an inconsistent state.
This parameter is mandatory when SLVM volume groups are used. This parameter should not be declared when only CVM disk groups are used.
CCRAC_CVM_DGS - CVM disk groups configured for the device specified in the above environment file for variable DEVICE_GROUP. These are the disk groups used by the associated RAC instance packages. It is important that all of the disk groups configured for the specified DEVICE_GROUP are listed. If only partial of the configured disk groups are listed, the device will not be prepared properly and the storage will result in an inconsistent state.
This parameter is mandatory when CVM disk groups or CFS are used. This parameter cannot be declared when SLVM volume groups are used.
CCRAC_INSTANCE_PKGS - the names of the configured RAC instance packages accessing in parallel the database stored in the specified volume groups.
This parameter is mandatory.
CCRAC_CLUSTER - Serviceguard cluster name configured as the primary cluster of the corresponding RAC instance package set.
This parameter is mandatory.
CCRAC_ENV_LOG - logfile specification for the storage preparation output.
This parameter is optional. If not specified, ${CCRAC_ENV}.log will be used.Sample setup:
CCRAC_ENV[0]=/etc/cmconcl/ccrac/db1/db1EnvFile_xpca.env |
CCRAC_SLVM_VGS[0]=ccracvg1 ccracvg2 |
CCRAC_INSTANCE_PKGS[0]=ccracPkg1 ccracPkg2 |
CCRAC_CLUSTER[0]=PriCluster1 |
CCRAC_ENV_LOG[0]=/tmp/db1_prep.log |
(Multiple values for CCRAC_SLVM_VGS and CCRAC_INSTANCE_PKGS should be separated by space).
If multiple sets of Oracle instances accessing different databases are configured in your environment and need Continentalclusters recovery support, repeat this set of parameters with an incremented index. For example,
CCRAC_ENV[0]=/etc/cmconcl/ccrac/db1/db1EnvFile_xpca.envCCRAC_SLVM_VGS[0]=ccracvg1 ccracvg2CCRAC_INSTANCE_PKGS[0]=ccracPkg1 ccracPkg2CCRAC_CLUSTER[0]=PriCluster1CCRAC_ENV_LOG[0]=/tmp/db1_prep.logCCRAC_ENV[1]=/etc/cmconcl/ccrac/db2/db2EnvFile_srdf.envCCRAC_CVM_DGS[1]=racdg01 racdg02CCRAC_INSTANCE_PKGS[1]=ccracPkg3 ccracPkg4CCRAC_CLUSTER[1]=PriCluster2CCRAC_ENV_LOG[1]=/tmp/db2_prep.logCCRAC_ENV[2]=/etc/cmconcl/ccrac/db3/db3EnvFile_xpca.envCCRAC_SLVM_VGS[2]=ccracvg5 ccracvg6CCRAC_INSTANCE_PKGS[2]=ccracPkg5 ccracPkg6CCRAC_CLUSTER[2]=PriCluster2 |
Copy the edited file to the
final directory:
# cp ccrac.config.mycopy \ /etc/cmconcl/ccrac/ccrac.config
Copy file /etc/cmconcl/ccrac/ccrac.config to all the other nodes of the cluster.
Login as root on one node of the recovery cluster and repeat steps “b” through “f” from
above. If the recovery cluster is configured to recover the Oracle
RAC instances for more than one primary cluster, the ccrac.config file on the recovery cluster should contain information
for all the primary clusters.
Configure Continentalclusters Recovery Group for
Oracle RAC instance. If you are using an individual package for
each RAC instance, define one recovery group for each Oracle RAC
instance recovery. The PRIMARY_PACKAGE specified for the Oracle RAC instance recovery
group is the name of the instance package configured on the primary
cluster. The RECOVERY_PACKAGE specified for the RAC instance recovery group
is the corresponding instance package name configured on the recovery
cluster. For example:
RECOVERY_GROUP_NAME instanceRG1 |
PRIMARY_PACKAGE ClusterA/instancepkg1 |
RECOVERY_GROUP_NAME instanceRG2 PRIMARY_PACKAGE ClusterA/instancepkg2 RECOVERY_PACKAGE |
Packages instancepkg1 and instancepkg2 are configured to run on primary cluster “ClusterA”. Packages instancepkg1’ and instancepkg2’ are configured to be restarted or recovered on the recovery
cluster “ClusterB” upon primary cluster failure.
If you are using one multi-node package to package all RAC instances,
define only one recovery group for the RAC MNP Package. For example.
RECOVERY_GROUP_NAME manufacturing_recovery |
PRIMARY_PACKAGE ClusterA/man_rac_mnp RECOVERY_PACKAGE ClusterB/man_rac_mnp |
When recovering a recovery group with multi-node packages, Continentalcluster
will start an instance in each cluster node configured in the MNP.
After editing the Continentalclusters configuration file to
add in the recovery group specification for Oracle RAC instance
packages, you must manually apply the new configuration by running
the cmapplyconcl command.
When you finish configuring a recovery pair with RAC support,
your systems must have sets of files similar to those shown in Figure 2-13 “Continentalclusters Configuration
Files in a Recovery Pair with RAC Support”.
|
| |
|
| NOTE: If you are configuring Oracle RAC instances in Serviceguard
packages in a CFS or CVM environment, do not specify the CVM_DISK_GROUPS, and CVM_ACTIVATION_CMD fields in the package control scripts as CVM disk group
manipulation is addressed by the disk group multi node package. |
|
| |
|
Serviceguard/Serviceguard
Extension for RAC and Oracle Clusterware Configuration |
|
The following are the required configurations for Continentalclusters RAC
instance recovery support for the cluster environment running with Serviceguard/Serviceguard
Extension for RAC and CRS (Oracle Cluster Software):
The Oracle RAC
environment running with Serviceguard/Serviceguard Extension for
RAC and Oracle Cluster Software should follow all the recommendations
listed in the Serviceguard and SGeRAC manuals for running with CRS
(Oracle Cluster Software).
CRS should not activate the
volume groups configured for the database automatically at startup
time. The file /var/opt/oracle/oravg.conf should not exist on any node of the primary and recovery
cluster.
The CRS storage (OCR and
voting disk) should be configured on a separate volume group than
the ones for the databases which are to be accessed by the RAC instances.
The RAC instance attribute
AUTO_START listed in the CRS service profile should be set to 2
on both primary and recovery clusters so that the instance will
not be automatically started when the node rejoins the cluster.
Login as the oracle administrator and use the following
steps to change the attribute value:
Generate
the resource profile.
crs_stat -p instance_name > $CRS_HOME/crs/public/instance_name.cap
Edit the resource profile
and set AUTO_START value to 2.
Register the value.
crs_register -u instance_name
Verify the value.
crs_stat -p instance_name
Initial
Startup of Oracle RAC Instance in a Continentalclusters Environment |
|
To ensure that the disk array will be ready for access in
shared mode for the Oracle RAC instances, it is recommended that
the user runs the Continentalclusters tool /opt/cmconcl/bin/ccrac_mgmt.ksh to initially startup the configured instance packages.
This tool ensures that the configured disk array will be ready in
writable mode for shared access before starting up the RAC instance
packages. If this tool is not used, manual checking is needed to
make sure the storage is ready in writable and shared access mode
before starting the RAC instance packages.
|
| |
|
| NOTE: It is recommended that ccrac_mgmt.ksh is used for the initial startup of the RAC instance
package, or for failing back the RAC instance packages. This tool
should not be used at the recovery site for recovering RAC instance
packages, instead cmrecovercl is used in this case. |
|
| |
|
After the initial startup, use Serviceguard commands cmhaltpkg, cmrunpkg, cmmodpkg as needed to halt and restart the packages on the primary
cluster.
Use the following steps on any node of the primary cluster
to do the initial startup of the Oracle RAC instance packages:
If the cluster
is running with Serviceguard and Oracle CRS, make sure that the
CRS daemons and the required Oracle services, such as listener,
GSD, ONS, and VIP are up and running on all the nodes the RAC database
instances are configured to run.
Make sure /etc/cmconcl/ccrac/ccrac.config exists and was edited to contain the appropriate information.
To start all the RAC instance
packages configured to run as primary packages on the local cluster.
# /opt/cmconcl/bin/ccrac_mgmt.ksh start
To start a specific set of RAC instance
packages.
# /opt/cmconcl/bin/ccrac_mgmt.ksh -i <indexNumber> start
<IndexNumber> is the index used in the /etc/cmconcl/ccrac/ccrac.config file for the target set of the Oracle RAC instance packages.
To stop all the RAC instance
packages configured to run as primary packages on the local cluster.
# /opt/cmconcl/bin/ccrac_mgmt.ksh stop
To stop a specific set of RAC instance
packages.
# /opt/cmconcl/ccrac_mgmt.ksh -i <indexNumber> stop
<IndexNumber> is the index used in the /etc/cmconcl/ccrac/ccrac.config file for the target set of the Oracle RAC instance packages.
Failover
of Oracle RAC Instances to the Recovery Site |
|
Upon a disaster that disables the primary cluster, to start
up a Continentalclusters recovery process, run the following command:
# cmrecovercl
For the cluster environment running with Serviceguard and
Oracle Clusterware, confirm that the Clusterware daemons and the
required Oracle services, such as listener, GSD, ONS, and VIP, are
started on all the nodes, which the database instance are configured
to run before initiating the recovery process.
If you have configured CFS or CVM in your environment, ensure
the following:
The SG-CFS-PKG (system multi-node package) is up and running.
The SG-CFS-PKG package is not part of the continentalclusters configuration.
The cmrecovercl command is run from the CVM master node. Use the following
command to display the CVM master node:
# vxdctl -c mode
Starting with Continentalclusters A.07.00, recovery groups
of applications using CFS or CVM can be recovered by running the cmrecovercl command from any node at the recovery cluster.
|
| |
|
| NOTE: Make sure that the primary site is unavailable and all
of the Oracle RAC instance packages are not running on the primary
cluster before initiating the recovery process. |
|
| |
|
The Continentalclusters command, cmrecovercl prepares the configured storage for Oracle RAC instances
shared access only when the file /etc/cmconcl/ccrac/ccrac.config exists. If this file does not exist, the configured
storage will not be prepared for shared access before recovering
the Oracle RAC instance packages. As a result, if Continentalclusters
recovery group configuration includes Oracle RAC instance packages,
these packages will not be able to start or operate successfully.
The recovery process will startup the configured Oracle RAC
instance packages as well as other application packages configured
in the Continentalclusters environment.
If the Continentalclusters Oracle RAC support is enabled (the /etc/cmconcl/ccrac/ccrac.config file exists), the following messages will be prompted
to the user when the command cmrecovercl is invoked and confirmations are needed for the process
to proceed.
WARNING: This command will take over for the primary cluster LACluster by starting the recovery package on the recovery cluster NYCluster. You must follow your site disaster recovery procedure to ensure that the primary packages on LACluster are not running and that recovery on NYCluster is necessary. Continuing with this command while the applications are running on the primary cluster may result in data corruption.
Are you sure that the primary packages are not running and will not come back, and are you certain that you want to start the recovery packages [y/n]? y
cmrecovercl: Attempting to recover Recovery Groups from cluster LACluster.
NOTE: The configuration file /etc/cmconcl/ccrac/ccrac.config for cluster shared storage recovery exists. Data storage specified in the file for this cluster will be prepared for this recovery process. If you choose "n" - not to prepare the storage for this recovery process, make sure that the required storage for this recovery process has been properly prepared. Is this what you intend to do [y/n]? y
The Oracle RAC instance package can be started in sequence.
# cmrecovercl -g <recoverygroupname>
Option -g is used to start up the first instance package, wait
until the disk arrays are synchronized before starting up the second
instance package.
If option -g is used with the command cmrecovercl, the following messages will be given instead:
WARNING: This command will take over for the primary cluster primary_cluster by starting the recovery package on the recovery cluster secondary_cluster. You must follow your site disaster recovery procedure to ensure that the primary packages on primary_cluster are not running and that recovery on secondary_cluster is necessary. Continuing with this command while the applications are running on the primary cluster may result in data corruption.
Are you sure that the primary packages are not running and will not come back, and are you certain that you want to start the recovery packages [y/n]? y
cmrecovercl: Attempting to recover RecoveryGroup subsrecovery1 on cluster secondary_cluster
NOTE: The configuration file /etc/cmconcl/ccrac/ccrac.config for cluster shared storage recovery exists. If the primary package in the target group is configured within this file, the corresponding data storage will be prepared before starting the recovery package. If you choose "n" - not to prepare the storage for this recovery process, make sure that the required storage for the recovery package has been properly prepared.
Is this what you intend to do [y/n]? y
Enabling recovery package racp-cfs on recovery cluster secondary_cluster
Running package racp-cfs\
Running package racp-cfs on node atlanta
Successfully started package racp-cfs on node atlanta
Running package racp-cfs on node miami
Successfully started package racp-cfs on node miami
Successfully started package racp-cfs.
cmrecovercl: Completed recovery process for each recovery group. Recovery packages have been started. Use cmviewcl or check package log file to verify that the recovery packages are successfully started.
These message prompts can be disabled by running cmrecovercl with option -y.
If you have configured the Oracle RAC instance package such
that there is one instance for every package, the instance or recovery
group can be recovered individually. If you have configured all
instances as a single multi-node package (MNP), recovering the recovery
group of this package starts all instances.
|
| |
|
| NOTE: At the recovery time, Continentalclusters is responsible
for recovering the Oracle RAC instance packages configured. The
data integrity and currency at the recovery site are based on your
data replication configuration in the Oracle environment. |
|
| |
|
Failback
of Oracle RAC Instances After a Failover |
|
After failover, the configured disk array at the old recovery
cluster becomes the primary storage of the database. The Oracle
RAC instances are running at the recovery cluster after a successful
recovery. To failback the Oracle RAC instances to the primary cluster,
follow the procedures listed below.
Before failing back the Oracle RAC instances, make sure that
the data in the original primary site disk array is in an appropriate
state. Follow the disk array specific procedures for data resynchronization
between two clusters, and the Oracle RAC failback procedures before
restarting the instance.
|
| |
|
| NOTE: Make sure the AUTO_RUN flag for all the configured Continentalclusters packages
is disabled before restarting the cluster. |
|
| |
|
Fix the problems
that caused the primary site failure.
Stop the Oracle RAC instance
packages running on the recovery cluster. On any node of the recovery
cluster.
# /opt/cmconcl/bin/ccrac_mgmt.ksh stop
If you have configured CVM or CFS in your environment, you
need to complete the following procedure:
Unmount the CFS mount points using
the following command:
cfsumount <Mount Point Name>
Deactivate the disk groups using the following command:
cfsdgadm deactivate <Disk Group Name>
Deport the disk groups using the following command:
vxdg deport <Disk Group Name>
The recovery cluster is now ready to failback packages and applications
to the primary cluster.
Synchronize the data between
the two participating clusters. Make sure that the data integrity
and the data currency are at the expected level at the primary site.
Verify that the primary cluster
is up and running.
# cmviewcl
If the cluster is running with Serviceguard and
Oracle CRS, make sure that CRS and the required services, such as
listener, GSD, ONS, and, VIP are up and running on all of the instance
nodes. By default, when CRS is started, these Oracle services are
initiated.
|
| |
|
| NOTE: Ensure that the SG-CFS-PKG (system multi-node) package
is running for the CFS/CVM environment. |
|
| |
|
Startup the Oracle RAC instance
packages on the primary cluster. If you have configured CFS or CVM
in your environment, issue the following command from the master
node:
# /opt/cmconcl/bin/ccrac_mgmt.ksh start
Alternatively, you can run the command on any node in the
primary cluster.
This command fails back all of the RAC instance packages configured
to adopt to this cluster as the primary cluster.
To failback only a specific set of the
Oracle RAC instance package set.
# /opt/cmconcl/bin/ccrac_mgmt.ksh [-i <indexNumber>] \ start
<indexNumber> is the index used in the /etc/cmconcl/ccrac/ccrac.config file for the target set of the Oracle RAC instance packages.
Rehearsing
Oracle RAC Databases in Continentalclusters |
|
Special precaution is required for running disaster recovery
(DR) rehearsal for Oracle RAC databases. For information on configuring
and running rehearsal for RAC databases, see Disaster
Recovery Rehearsal in Continentalclusters whitepaper
available at: http://www.docs.hp.com.
Printable version
