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)
Understanding how Volume Replicator logs writes to the Replicator Log
Volume Replicator receives writes from the application and queues them in the Primary Replicator Log for transmission to the Secondary hosts. If a Primary RVG is connected to multiple Secondary RVGs, the Replicator Log on the Primary is used to manage the writes for these Secondary hosts. The Replicator Log header contains a specific set of pointers for each Secondary which indicates the writes that have not been sent to the corresponding Secondary.
This section explains the working of the Replicator Log as a circular buffer.
The first write that comes in is Write 1, which also represents the start of log for the Secondary. Volume Replicator logs Write 2, Write 3, Write m one after the other until it reaches the end of the Replicator Log. Because the Replicator Log is a circular log the next write, Write m+1 wraps around and logging continues. When the Primary receives the data acknowledgment from this Secondary host for Write 1, Volume Replicator marks the Write 1 as complete in the Replicator Log. Volume Replicator then processes Write 2, Write 3, and so on.
Secondary1 is 200 writes or updates behind, whereas Secondary2 is 150 writes behind. If the end of log pointer reaches the start of log pointer of the Secondary, the Replicator Log overflows for this Secondary.
The Secondary hosts for which the replication is configured in synchronous mode are usually up-to-date. Typically, the number of simultaneous I/O operationsthat the application performs separates the start and the end of log pointers of synchronous RLINKs (Secondaries). For asynchronous RLINKs, the difference between the start of log pointer and end of log pointers reflect how many outstanding writes have yet to be processed, that is, how behind is the RLINK. Different RLINKs usually have start of log pointers indicating different places in the Replicator Log; this reflects the difference in the rate at which data is sent to the Secondary. After the Primary receives the data acknowledgment from all the Secondary hosts, Volume Replicator marks the write as complete in the Replicator Log volume.