The following list gives the best practices for setting up the agents:

• Only one DiskGroup and one RVG resource must be present in a service group.

• If a disk group is configured as a DiskGroup resource, then all the RVGs in this disk group must be configured as RVG resources.

  If a disk group is configured as a CVMVolDG resource, then all the RVGs must be configured as RVGShared resources.

• When configuring failover applications, use the RVG and RVGPrimary agents.

• When configuring parallel applications, use the RVGShared and RVGSharedPri agents.

• When configuring parallel applications, use the RVGShared, RVGSharedPri, and RVGLogowner agents. If the configuration has multiple RVGLogowner resources, we recommend that you alternate the order of hosts in the AutoStartList attributes for the service groups containing the RVGLogowner resources. VCS then brings online the RVGLogowner resources on different nodes in the cluster, which facilitates load-balancing. For example, the first service group containing an RVGLogowner resource would appear as:

  AutoStartList = { seattle1, seattle2 }

  whereas the next service group would have:

  AutoStartList = { seattle2, seattle1 } and so on.

• Do not configure the RVGShared resource in the cvm group. Configure the RVGShared resource in a separate group which contains the RVGShared resource and the CVMVolDg resource.

• In a global clustering environment, you must also use the ClusterList attribute.

  ClusterList = { gco_primclus=1, gco_secclus=2 }

• If a volume set is fully associated to an RVG, that is, if all its component volumes are associated to the RVG, you can add the volume set to the agent configuration in the same way that a volume is added. Specify the volume set in the Mount resource instead of the component volume names.