Migrating a Service Group

In the RDC set up for the Oracle database, consider a case where the primary RDC zone suffers a total failure of the shared storage. In this situation, none of the nodes in the primary zone see any device.

The Oracle service group cannot fail over locally within the primary RDC zone, because the shared volumes cannot be mounted on any node. So, the service group must fail over, to a node in the current secondary RDC zone.

The RVGPrimary agent ensures that VVR volumes are made writable and the DNS agent ensures that name services are resolved to the DR site. The application can be started at the DR site and run there until the problem with the local storage is corrected.

If the storage problem is corrected, you can switch the application to the primary site using VCS.

Switching the Service Group

Before switching the application back to the original primary RDC zone, you must resynchronize any changed data from the active DR site since the failover. This can be done manually through VVR or by running a VCS action from the RVGPrimary resource.

1. In the Service Groups tab of the configuration tree, right-click the resource.
2. Click Actions.
3. Specify the details of the action:

   

   Click the thumbnail above to view full-sized image.

   1. From the Action list, choose fast-failback.
   2. Click the system on which to execute the action.
   3. Click OK.

   This begins a fast-failback of the replicated data set. You can monitor the value of the ResourceInfo attribute for the RVG resource to determine when the resynchronization has completed.

4. Once the resynchronization completes, switch the service group to the primary cluster.
   1. In the Service Groups tab of the of the Cluster Explorer configuration tree, right-click the service group.
   2. Click Switch To and select the system in the primary RDC zone to switch to and click OK.