To configure the replication group

1. Create a hybrid service group (oragrp_rep) for replication. You can use the VvrRvgGroup template to create the service group.

2. Copy the DiskGroup resource from the application to the new group. Configure the resource to point to the disk group that contains the RVG.
3. Configure new resources of type IP and NIC.

4. Configure a new resource of type RVG in the service group. The RVG agent ships with the VVR software. If the RVG resource type is not defined in your configuration, import it, as instructed below.

   • On the File menu, click Import Types.

   • In the Import Types dialog box, Click the file from which to import the resource type. By default, the RVG resource type is located at the path /etc/VRTSvcs/conf/VVRTypes.cf.

   • Click Import.

5. Configure the RVG resource. See the VVR documentation for more information.

   Note that the RVG resource starts, stops, and monitors the RVG in its current state and does not promote or demote VVR when you want to change the direction of replication. The RVGPrimary agent manages that task.

6. Set resource dependencies as per the following information:

   • RVG resource depends on the IP resource

   • RVG resource depends on the DiskGroup resource

     IP resource depends on the NIC resource

7. Set the SystemZones attribute of the child group, oragrp_rep, such that all nodes in the primary RDC zone are in system zone 0 and all nodes in the secondary RDC zone are in system zone 1.

To configure the application service group

1. In the original Oracle service group (oragroup), delete the DiskGroup resource.
2. Add an RVGPrimary resource and configure its attributes.

   Set the value of the RvgResourceName attribute to the name of the RVG type resource that will be promoted and demoted by the RVGPrimary agent.

   Set the AutoTakeover and AutoResync attributes from their defaults as desired.

3. Set resource dependencies such that all Mount resources depend on the RVGPrimary resource. If there are a lot of Mount resources, you can set the TypeDependencies attribute for the group to denote that the Mount resource type depends on the RVGPRimary resource type.
4. Set the SystemZones attribute of the Oracle service group such that all nodes in the primary RDC zone are in system zone 0 and all nodes in the secondary RDC zone are in zone 1. The SystemZones attribute of both the parent and the child group must be identical.
5. If your setup uses BIND DNS, add a resource of type DNS to the oragroup service group. Set the Hostname attribute to the canonical name of the host or virtual IP address that the application uses on that cluster. This ensures DNS updates to the site when the group is brought online. A DNS resource would be necessary only if the nodes in the primary and the secondary RDC zones are in different IP subnets.