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)
Checking replication performance using vxrlink stats
The vxrlink stats command reports detailed information about replication statistics, which can be used to assess network problems. This information about the network performance can be used to determine the optimum network configuration for efficient use of system resources. The vxrlink stats command can be executed only from the Primary. The Monitor view option from the VEA is the parallel for the vxrlink stats command output in the GUI and is available both from the Primary and Secondary.
Note:
All the statistics that the vxrlink stats command displays, are reinitialized when the replication is restarted, either because of a user command or because of the network or server outage.
The following table describes the output of the vxrlink stats command.
Table: vxrlink stats command output: Information Messages
Field Name | Description |
---|---|
# | Displays the number of messages transmitted. |
Blocks | Displays the number of blocks that are transmitted to the Secondary RVG. One block consists of 512 bytes. |
RT (msec) | Displays the average round-trip time. |
Delays | Displays the delay that Volume Replicator introduces while sending the packets, if it is flow controlled. Usually, delays are introduced when there are errors on the link or the outstanding bytes for flow control have been exceeded for a single message. |
The following table describes the output of the vxrlink stats command.
Table: vxrlink stats command output: Error Information
Field Name | Description |
---|---|
Timeout | Displays the number of time-out errors. A time-out error occurs when an acknowledgement for a message is not received from the remote host within the computed time-out period. The time-out period is automatically adjusted for optimum performance based on round-trip time (RT). |
Stream | Displays the errors that occur while sending the updates on the network, which can include errors due to insufficient memory, errors returned by the underlying protocol driver and so on. |
Memory | Displays the number of memory errors. Memory errors generally occur when the Secondary is unable to store the out of order packets that it receives. One reason for this may be because the Secondary has insufficient buffer space to handle incoming messages or the earlier messages still have some packets pending. This can be fixed by increasing the NMCOM_POOL_SIZE tunable on the Secondary. |
The following table describes how the flow control reacts to the errors that are displayed for vxrlink stats command.
Table: vxrlink stats command output: Flow control
Field Name | Description |
---|---|
NW Bytes | Displays the number of bytes that can be transmitted without flow controlling and introducing any intervening delays. If an RLINK does not experience network errors, Volume Replicator steadily increases the NW Bytes to permit more data to be transmitted. If an RLINK experiences network error, Volume Replicator tries to perform flow control by reducing this number. The minimum value is 5000 bytes. |
NW Delays | Displays the delay that Volume Replicator may introduce while sending the packets, if it was flow controlled. Usually, delays are introduced when there are errors on the link or the outstanding bytes for flow control have been exceeded for a single message. |
Timeout | Displays the current time-out value in milliseconds. This value is computed dynamically. If an acknowledgement for a message is not received from the remote host within this value, the message is considered lost and is retransmitted. |