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)
Network, process, and operating system checks
General problems like high latency, low-bandwidth, high collisions counts, and a high percentage of dropped packets also affects Volume Replicator.
Specific issues with networks are as follows:
Check the status of communication between the Primary and Secondary nodes by using the replication path. To do this ping from Primary to Secondary and Secondary to Primary using remote_host fields in the RLINKs. There should be very minimal packet loss, if any.
Run: ping <remote_host>Run: ping <remote_host_ip_address>
Confirm whether the network can handle large packets using the ping command. The packet loss should be similar to that mentioned in the preceding point. In the ping command, specify packet_size value that the vxprint -l <rlink-name> command displays.
Run: ping -l <packet_size> <remote_host> Run: ping -l <packet_size> <remote_ip_address>
Check whether the connection server is started or not. You can confirm this, by checking the system event log. You should see an entry similar to the one given below:
Connection Server started successfully (using port 6ae).
If you do not see this entry, make sure that vxsvc service for the Veritas Enterprise Administration (VEA) is started. If it is not started then start the service, and check the log again.
In the system event log, you may see entries similar to Connection Server already started. These messages do not indicate any problems.
Run the following command on each node to make sure that the Volume Replicator connection server uses the port that is mentioned in the vrport heartbeat command.
netstat -an | findstr <port-number mentioned in vrportheartbeat' output>
The default port number is 4145. Check the output of the vrport command.
More Information