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)
Analyzing Volume Replicator performance
You can now analyze the Volume Replicator performance through the performance monitor (perfmon), which is a utility that the Windows operating system provides. This utility can be launched by executing the perfmon command.
To be able to monitor the Volume Replicator performance, the performance objects that have been added to perfmon are as follows:
Volume Replicator Memory
Volume Replicator Remote hosts
Each of these performance objects includes a set of performance counters, which are used for logging the Volume Replicator performance-related information. For logging information you must create the log file with the required parameters. To do this, right-click the Counter Log from the tree view and select form the menu that appears.
For more information about using the performance monitor, refer to the help that is available from the Help button on the performance monitor console.
Note:
When setting the properties for a new log file on a system running Windows Server, you must specify an account with administrative privileges to run the log. Otherwise, the log file fails to gather the required information.
The Volume Replicator Memory object includes the parameters available with the vxmemstat command, whereas the Volume Replicator remote hosts object includes a combination of parameters available with the vxrlink stats command and the vxrlink status.
The Volume Replicator objects can be viewed using the different graphical view options that perfmon provides.
The following types of Volume Replicator objects can be viewed:
Volume Replicator Remote Host object
Volume Replicator creates the Volume Replicator Remote host object.
Volume Replicator Memory Object
Volume Replicator creates the Volume Replicator Memory Object.
Table: Performance object counters and their descriptions for Volume Replicator Remote Host object
Performance Counter Names | Description |
---|---|
Data Transmitted (KB) | The amount of data that is successfully transmitted to the remote host. The following table lists the performance object counters with their descriptions for Volume Replicator Remote Host object. |
DCM Usage (%) | Indicates the percentage of DCM that is used, based on the number of bits marked in the DCM log. |
Delays | The total amount of delay that has been introduced so far after flow control was enforced. |
Flow Control NW Bytes | Number of bytes which can be transmitted without imposing flow control measures. |
Flow Control NW Delay | The delay that is introduced while sending data, so as to enforce flow control. |
Flow Control Timeout | Indicates a dynamically computed time-out value for the acknowledgement of a message that has already been sent. If no acknowledgement is received within the time-out period, then retransmission is attempted. |
Lost Packets | Displays the rate at which replication data packets are lost. |
Memory Errors | Displays the errors due to insufficient memory. |
Round Trip Time (msec) | Displays the average round-trip time that is required for transmitting and acknowledging the replication messages. |
SRL Requests | Displays the number of updates pending on the Replicator Log. |
Stream Errors | Displays the errors due to insufficient bandwidth. |
Used SRL (%) | Displays the percentage of the Replicator Log used for recording updates or the writes that need to be replicated. |
The following table lists performance counters with their descriptions for Volume Replicator Memory object.
Table: Performance counters and description associated with Volume Replicator Memory Object
Field Name | Description |
---|---|
Allocated NMCOM Pool (KB) | Memory that the Secondary allocates to hold the updates that are received from the Primary. |
Allocated READBACK Memory Pool (KB) | Memory that is allocated for holding updates after reading them from the Replicator Log. |
Allocated VOLIO Memory Pool (KB) | Memory that is allocated by the Primary to hold the updates for replicating them. |
Used NMCOM Pool (KB) | Displays the currently used portion of the allocated NMCOM Pool. |
Used READBACK Pool (KB) | Displays the currently used portion of the allocated READBACK Pool. |
Used VOLIO Memory Pool (KB) | Displays the currently used portion of the allocated VOLIO memory Pool. |
WaitQ for VOLIO Memory | Displays the number of updates waiting for free memory in the VOLIO Memory Pool. |