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)
Peak usage constraint
For some configurations, it might be common for replication to fall behind the application during certain period and catch up during others. For example, an RLINK might fall behind during business hours and catch up overnight if its peak bandwidth requirements exceed the network bandwidth. However, for synchronous RLINKs this does not apply as a shortfall in network capacity would cause each application write to be delayed. This in turn causes the application to run more slowly.
For asynchronous RLINKs, the only limit to how far replication can fall behind is the size of the SRL. If it is known that the peak write rate requirements of the application exceed the available network bandwidth, then it becomes important to consider this factor when sizing the SRL.
Assuming that data is available providing the typical application write rate over a series of intervals of equal length, it is simple to calculate the SRL size that is needed to support this usage pattern:
- Calculate the network capacity over the given interval (BWN).
- For each interval n, calculate the SRL log volume usage (LUn) as the excess of application write rate (BWAP) over network bandwidth (LUn = BWAP(n) - BWN).
- For each interval, accumulate all the SRL usage values to find the cumulative SRL log size (LS):
The largest value that is obtained for any LSn is the value that should be used for SRL size as determined by the peak usage constraint. For an example of this calculation, The third column, Application, contains the maximum likely application write rate per hour. The fourth column Network shows the network bandwidth. The fifth column SRL Usage shows the difference between application write rate and network bandwidth that is obtained for each interval. The sixth column Cumulative SRL Size shows the cumulative difference every hour. The largest value in column 6 is 37 gigabytes. The SRL should be at least this large for this application.
Several factors can reduce the maximum size to which the SRL can fill up during the peak usage period. The factors that need to be considered are:
The latencyprot characteristic can be enabled to restrict the amount by which the RLINK can fall behind, slowing down the write rate.
The network bandwidth can be increased to handle the full application write rate. In this example, the bandwidth should be 15 gigabytes/hour - the maximum value in column three.
Table: Example calculation of SRL size required to support peak usage period
Hour Starting | Hour Ending | Application (GB/hour) | Network (GB/hour) | SRL Usage (GB) | Cumulative SRL Size (GB) |
---|---|---|---|---|---|
7:00 A.M. | 8:00 A.M. | 6 | 5 | 1 | 1 |
8 | 9 | 10 | 5 | 5 | 6 |
9 | 10 | 15 | 5 | 10 | 16 |
10 | 11 | 15 | 5 | 10 | 26 |
11 | 12:00 P.M. | 10 | 5 | 5 | 31 |
12:00 P.M. | 1 | 2 | 5 | -3 | 28 |
1 | 2 | 6 | 5 | 1 | 29 |
2 | 3 | 8 | 5 | 3 | 32 |
3 | 4 | 8 | 5 | 3 | 35 |
4 | 5 | 7 | 5 | 2 | 37 |
5 | 6 | 3 | 5 | -2 | 35 |