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)
Replicator Log overflow protection - srlprot attribute
Volume Replicator provides the following modes of overflow protection: Override, Fail, DCM, and AutoDCM. You can also turn off the Replicator Log overflow protection feature by setting the attribute to off.
If the network is down or the Secondary is unavailable, the number of writes in the Replicator Log waiting to be sent to the Secondary could increase until the Replicator Log fills up. When the Replicator Log cannot accommodate a new write without overwriting an existing one, the condition is called Replicator Log overflow. The new writes are held up, DCM is activated, or the Replicator Log overflows depending on the srlprot setting.
Circumstances that can cause the Replicator Log to overflow when you replicate in the asynchronous mode are as follows:
A temporary burst of writes, or a temporary congestion in the network, causing 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.
An administrator pauses the RLINK from the VEA GUI or by executing a vxrlink pause command.
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 Replicator Log overflows, the Secondary becomes out-of-date and must be completely synchronized to bring it up-to-date with the Primary. The Replicator Log protection feature of Volume Replicator enables you to either prevent the Replicator Log from overflowing or tracks the writes using Data Change Map (DCM) in the case of Replicator Log overflow. You must weigh the trade-off between allowing the overflow or affecting the application. You can prevent Replicator Log overflow by using the srlprot setting.
Volume Replicator provides the following modes of Replicator Log overflow protection: AutoDCM, DCM, Override, and Fail. These modes are activated only when the Replicator Log is about to overflow. You can set up Replicator Log protection by setting the srlprot attribute of the corresponding RLINKs to AutoDCM, DCM, Override, or Fail. You can turn off the Replicator Log protection by setting the srlprot attribute to off.
The following table describes the effect of the RLINK state on the Replicator Log protection.
Table: Effect of RLINK state on the Replicator Log Protection
Value of the srlprot Attribute | When RLINK is Connected | When RLINK is Disconnected |
---|---|---|
autodcm | Convert to DCM logging | Convert to DCM logging |
dcm | Protect Note: SRL protects writes by stalling application writes until Replicator Log drains 5% to become 95% full or drains 20 MB, whichever is smaller. | Convert to DCM logging |
override | Protect | Overflow |
fail | Protect | I/O error to application |
Note:
When srlprot=off, the Replicator Log overflows irrespective of whether the RLINK is connected or disconnected.
If the Replicator Log overflow protection is enabled and if a write is about to cause the log to overflow, then the Replicator Log protection is turned on.