The RVGPrimary agent enables migration and takeover of a VVR Replicated Volume Group (RVG) in a VCS environment. Bringing a resource of type RVGPrimary online causes the RVG on the local host to become a primary.
The agent is useful when hosts in both the primary and secondary side are clustered, in particular a VCS replicated data cluster or a VCS global cluster, to completely automate the availability of writable replicated disks to a VCS-managed application.
The RVGPrimary agent includes the following features:
Removes the manual steps of migrating a VVR primary and secondary roles when failing over applications across a wide area.
Minimizes the need for resynchronizing replicated volumes by attempting a migration before attempting a hard takeover.
Waits for the two sides of a replicated data set to become completely synchronized before migrating roles.
Supports an automatic fast failback resynchronization of a downed primary if it later returns after a takeover.
Allows you to distinguish the Primary site after network failure or disaster
Supports the ability to choose the Primary site after a site failure or network disruption is corrected.
After a successful migration or takeover of a Secondary RVG, the RVGPrimary agent ensures to automatically start the replication from the new Primary to any additional Secondary(s) that exists in the RDS.
Before a takeover, the RVGPrimary agent synchronizes the Secondary site with any bunker associated with the Primary site, when the Primary site is not available.
Refer to the Veritas InfoScale Replication Administrator's Guide for information on configuring the Replication agents for high availability.
A sample configuration file for this agent that you can use as a guide to create the configuration is located at /etc/VRTSvcs/conf/sample_vvr/RVGPrimary.