Volume Replicator 7.4.2 Administrator's Guide - Windows
- Understanding Volume Replicator
- About Volume Replicator
- Basic Volume Replicator terms
- Building blocks of Volume Replicator
- Understanding replication in the Volume Replicator environment
- Modes of replication
- Understanding data flow in Volume Replicator asynchronous mode
- Managing data during failure and recovery
- Replication concepts
- About using Volume Replicator as a disaster recovery tool
- Understanding how Volume Replicator logs writes to the Replicator Log
- Understanding replication settings for a Secondary
- Measures to protect log overflow and replication latency
- Pausing the replication
- Synchronizing the Secondary
- Understanding Volume Replicator support for FlashSnap
- About Synchronized Snapshots
- Understanding Bunker replication
- Understanding Volume Replicator Support for TCP Multi-Connection
- About Volume Replicator memory monitoring and control support
- About Volume Replicator Graphs
- Setting up replication
- Security considerations for Volume Replicator
- Setting up replication using the Setup Replicated Data Set wizard
- Setting up the Bunker RVG for replication
- Using the VEA Console for Volume Replication Operations
- Monitoring replication
- Interpreting the information in the Volume Replicator views
- Monitoring replication using the VEA console
- Checking replication performance using vxrlink stats
- Administering Volume Replicator
- Adding volumes
- Administering the RVG
- Administering replication
- Managing checkpoints
- Pausing replication using Volume Replicator
- Creating snapshots for the data volumes
- Creating synchronized snapshots using the VSS Snapshot wizard
- Administering Bunker replication
- Performing disaster recovery operation
- Deleting Volume Replicator objects
- Accessing data on Secondary host
- Performing automated system recovery (ASR)
- Alternative methods to synchronize the Secondary faster
- Obtaining statistical information through Volume Replicator Graphs
- Using the command line interface
- Administering the RDS using the vxrds command
- Resizing the data volumes
- Displaying the network statistics for the RLINK
- Administering the RVGs using the vxrvg command
- Displaying information using the vxprint command
- Creating snapshots using the vxsnap command
- Administering replicated volumes using the vxvol command
- Displaying and changing replication ports using the vrport command
- Administering the RVG using the vxedit
- Administering the RVG using the vxassist command
- Tuning Volume Replicator
- Examples: Using the command line
- Example 1: Setting up replication using the command line interface
- Example 3: Using Bunker node for disaster recovery
- Example 4: Using synchronized snapshots to restore data
- Configuring Volume Replicator in a VCS environment
- Components of a VCS cluster
- Illustrating a highly available Volume Replicator setup
- How the agents work
- Configuring the agents
- Working with existing replication service groups
- Configuring Volume Replicator with Hyper-V
- Advanced settings in Volume Replicator
- Troubleshooting Volume Replicator
- Recommendations and checks
- Recovering from problems in a firewall or NAT setup
- Recovering from problems during replication
- Error when configuring the VxSAS Service
- Operation time-out errors
- Problems when configuring Volume Replicator in a VCS environment
- Problems when setting performance counters
- Appendix A. Services and ports
- Appendix B. Using the vxrsync utility
- Appendix C. VR Advisor (VRAdvisor)
RVGPrimary agent-specific functions, state definitions, and attributes
This section provides information about RVGPrimary agent and state definitions.
The following table provides the RVGPrimary agent-specific information with agent and state definitions.
Table: RVG Primary agent-specific information
Description | Agent Functions(Entry Points) | State Definitions |
---|---|---|
Enables taking over of the Primary role by the Secondary if the Primary becomes unavailable. Enables the migration of the Primary role to the Secondary. |
|
|
Review the following information to become familiar with the agent attributes required for an RVGPrimary resource type. This information assists you during the agent configuration.
The following table describes the agent attributes for the RVGPrimary resource.
Table: Agent attributes for RVGPrimary resource type
Attribute | Type and Dimension | Definition |
---|---|---|
RvgResourceName | string-scalar | The name of the VvrRvg resource in the replication group on which the application group depends. |
AutoTakeover | int | If set to 1, the agent automatically enables the Secondary to take over the Primary role when it detects that the Primary has become unavailable. If set to 0, no automatic takeover is performed. In that case you must manually perform the takeover operation on the Secondary |
AutoResync | int | If set to 1, the agent automatically performs a resynchronization operation to synchronize the failed Primary with the new Primary when it becomes available after a takeover operation with fast-failback. If set to 0, manually resynchronize the original Primary with the new Primary, after it becomes available again. |
BunkerSyncTimeout | int | If set to Null (no value), the RVGPrimary agent considers this as infinite time-out value. It replays all the writes on the Bunker Replicator Log to the Secondary and only after all the writes are sent the takeover is performed on the Secondary. If set to 0 indicating a zero RTO, the RVGPrimary agent immediately performs a take over on the Secondary and no pending writes from the Bunker are sent to the Secondary. If the value is set to a specific integer, <T> seconds, then the RVGPrimary agent makes sure that writes for <T> seconds are sent to the Secondary before performing a takeover on the Secondary. Thus, the RTO in this case is equal to <T> seconds. |
The following table describes the factors affecting the RVGPrimary resource on the Primary and Secondary nodes.
Table: Factors affecting the RVGPrimary resource on Primary and Secondary nodes
Node on which RVGPrimary is online | Factors affecting the RVGPrimary resource actions | Action that the RVGPrimary agent performs during online operation |
---|---|---|
Primary | None | The resource is online. |
Secondary | The Secondary is connected and is up-to-date. | The resource performs a migrate operation and the RVGPrimary resource becomes online. If there are multiple Secondaries in the RDS, and RLINKs between the Secondaries have been created, then, the RVGPrimary agent adds these Secondaries back into the RDS and synchronizes them with the new Primary. This happens in the background once the resource has come online. |
Secondary | The Secondary is connected but is not up-to-date. | The resource waits until the online time-out period is reached, for the Secondary to become up-to-date. If the Secondary becomes up-to-date then the resource performs a migrate operation and the RVGPrimary resource is brought ONLINE, else it will fault. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected, and the following attributes are set: AutoTakeover=1 AutoResync=1 | If the original primary node has a bunker RVG associated with it, then the resource first synchronizes the secondary node from the Bunker before performing a takeover with fast-failback logging. When the original Primary becomes accessible, it is converted to a secondary and is automatically synchronized with the new Primary. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected, and the following attributes are set: AutoTakeover=1 AutoResync=0 | The resource performs a takeover with fast-failback, but without performing the automatic synchronization. In the case of a Bunker setup, the resource first synchronizes the secondary node from the Bunker node before performing a takeover with fast-failback logging. You need to manually resynchronize the original Primary when it becomes available again using:
The fbsync action is very useful as it enables you to perform synchronization from the VCS console itself without having to switch to the VEA console. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary. |
Secondary | The Secondary is not connected and the Primary cluster state has been declared as disaster or replica. For more information, see Cluster Server Administrator's Guide. In this you have set the following attributes: AutoTakeover=1 AutoResync=0 | The resource performs a takeover without fast-failback. If there are multiple secondaries in the RDS, and RLINKs between the secondaries are created, then, the RVGPrimary agent adds these secondaries back into the RDS and synchronizes them with the new Primary |
Secondary | The Secondary is inconsistent. | The resource fails to come online. |
Acting Secondary | The resource fails to come online. |