Volume Replicator 7.4.1 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)
Understanding latency protection
When you replicate in asynchronous mode, it is normal for the Replicator Log to have writes waiting to be sent to the Secondary. If your network has been sized based on the average update rate of the application on the Primary node, the number of writes waiting in the Primary Replicator Log is likely to be within an acceptable range.
The number of writes in the Replicator Log that would grow under the following circumstances are as follows:
A temporary burst of writes or a temporary congestion in the network, which causes the current update rate to exceed the currently available bandwidth between the Primary and the Secondary.
A temporary failure of the Secondary node or the network connection between the Secondary and the Primary.
Performing the pause operation.
Inability of the network bandwidth to keep up with the update rate at the Primary, on a sustained basis. This is not a temporary condition and can be corrected only by increasing the network bandwidth or reducing the application update rate, if possible.
If the Primary Replicator Log has a large number of writes waiting to be transferred to the Secondary, the Secondary data is considerably behind the Primary. If a disaster strikes the Primary and the Secondary takes over, the Secondary does not contain all the data in the Primary Replicator Log. In this case, the data on the Secondary is consistent but out of date when the Secondary takes over. In such a scenario, to prevent the Secondary from being too far behind the Primary, you can limit the number of writes waiting in the Primary Replicator Log for transmission to the Secondary, by setting up latency protection.
Latency protection has two components, its mode, and the latency_high_mark and latency_low_mark values which specify when the protection is active or inactive. The latency_high_mark specifies the maximum number of pending updates by which the Secondary can be behind the Primary. If the number of such updates in the Replicator Log reaches the specified latency_high_mark value, then, further writes to the Primary are stalled or failed, depending on the mode of latency protection. In this situation, the writes continue to be stalled or failed until the number of pending updates in the Replicator Log falls to the specified latency_low_mark value. Hence, the latency_low_mark value must be a number lower than the latency_high_mark value.
You can enable latency protection by setting the latencyprot attribute to either override or fail. Setting the attribute to latencyprot=off, which is the default, disables latency protection.
The following table summarizes how the state of the RLINK affects the latency protection.
Table: The state of RLINK and latency protection
Value of latencyprot Attribute | When RLINK is Connected | When RLINK is Disconnected |
---|---|---|
override | Protect | Drop protection |
off | No protection | No protection |
fail | Protect | I/O error to application |
The following sections explain how Volume Replicator controls replication depending on the setting of the latencyprot attribute of the RLINK when the Primary and Secondary are either connected or disconnected.