Configuring replication resources in VCS
Prev	Connecting clusters-Creating global clusters	Next

---

Configuring replication resources in VCS

This section describes how to set up replication using Veritas Volume Replicator (VVR.)

VCS supports several replication solutions for global clustering. Contact your Symantec sales representative for the solutions that VCS supports.

To create the RVG resources in VCS

1. Create a new service group, say appgroup_rep.
2. Copy the DiskGroup resource from the appgroup to the new group.
3. Configure new resources of type IP and NIC in the appgroup_rep service group. The IP resource monitors the virtual IP that VVR uses for replication.
4. Configure a new resource of type RVG in the new (appgroup_rep) 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 about the resource.

   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. That task is managed by the RVGPrimary agent.

6. Set 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.

     The service group now looks like:

Click the thumbnail above to view full-sized image.

7. Delete the DiskGroup resource from the appgroup service group.
8. In the appgroup service group, add a resource of type RVGPrimary and configure its attributes:
   • RVGResourceName—The name of the RVG resource that this agent will promote.
   • AutoTakeover—A flag that indicates whether the agent should perform a takeover in promoting a Secondary RVG if the original Primary is down. Default is 1, meaning a takeover will be performed.
   • AutoResync—A flag that indicates whether the agent should configure the RVG to perform an automatic resynchronization after a takeover and once the original Primary is restored. Default is 0, meaning automatic resynchronization will not occur.
9. Set resource dependencies such that the Mount resource depends on the RVGPrimary resource.

   The appgroup now looks like:

Click the thumbnail above to view full-sized image.

10. If your setup uses BIND DNS, add a resource of type DNS to the appgroup service group and configure its attributes:
    • Domain—Domain name. For example,symantec.com.
    • Alias—Alias to the canonical name. For example, www.
    • Hostname—Canonical name of a system. For example, mtv.symantec.com.

      On AIX, Linux, or Solaris, you can enter an IP address.

    • TTL—Time To Live (in seconds) for the DNS entries in the zone being updated. Default value: 86400.
    • StealthMasters—List of primary master name servers in the domain. This attribute is optional if the primary master name server is listed in the zone's NS record. If the primary master name server is a stealth server, the attribute must be defined.

      Note that a stealth server is a name server that is authoritative for a zone but is not listed in the zone's NS records.