and that recovery on secondary_cluster is necessary. Continuing with this command while the applications are running on the primary cluster might 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 prepared before starting the recovery package. If you choose "n" - not to prepare the storage for this recovery process, ensure 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
Running package
Running package
Successfully started package
Running package
Successfully started package
Successfully started package
cmrecovercl: Completed recovery process for every recovery group. Recovery packages have been started. Use cmviewcl or verify package log file to verify that the recovery packages are successfully started.
These message prompts can be disabled by running the cmrecovercl command with the option
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
NOTE: At the recovery time, Continentalclusters is responsible for recovering the configured Oracle RAC instance packages. The data integrity and currency at the recovery site are based on the 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.
Before failing back the Oracle RAC instances, ensure 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: Ensure the AUTO_RUN flag for all the configured Continentalclusters packages is disabled before restarting the cluster.
To failback the Oracle RAC instances to the primary cluster:
1.Fix the problems that caused the primary site failure.
2.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
134 Configuring Oracle RAC in Continentalclusters in Legacy style
