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 the utility works
Using the vxrsync utility, you can perform three different operations; full synchronization, difference-based synchronization, and data verification.
When performing full synchronization between volumes the utility copies all the data from the source to the destination volumes. For performing difference-based synchronization, the utility first calculates the checksum and then compares the checksums between volumes. Based on the result the utility copies only those blocks that have changed on to the target volumes.
When performing verify data operation, vxrsync first calculates the checksum for the volumes to find the change in data between the source and the target and then displays the difference on the console.
The vxrsync utility consists of two components, vxrclient and vxrserver. The vxrclient must be running on the source computer and the vxrserver must be running on the target computer. Note that the vxrserver must first be started before the vxrclient is started. The vxrclient and the vxrserver require either volume names, the RVG name, or a configuration file name as input. You must also specify the port number on which the vxrserver needs to listen for requests. If you use a configuration file as input, then, the port number that you specify for the vxrserver must be the same as that specified in the file. If no port number is specified for vxrserver, then, by default, it uses the port number 8989 and vxrclient uses this port to communicate with vxrserver.
If you choose to use the RVG name as input then you must ensure that the target or Secondary (RLINK) must be detached. Make sure that the target volumes are not in active use during the period the synchronization or verification is in progress. Otherwise, the synchronization process fails. If the -x option is specified with vxrclient then the source volumes are locked. Otherwise, a warning message is displayed, but synchronization still proceeds.
Also, note that all the specified volumes with the same names and sizes must be present on each host within the RDS.
The configuration file defines the relation between the source and target volumes which need to be synchronized or verified. If you want to use the configuration file as an input then you must first create it. Ensure that the file is created using a text editor and is available in the current directory from where you are running the command.
Note:
The configuration file must be named using the format <groupname>.cfg. The groupname is the name that you have given the set of related volumes within the configuration file. The file must have an extension .cfg.
The configuration file can be used both for synchronizing the data volumes or for verifying the data. However, for the utility to complete the specified operation successfully, the configuration file must be exactly the same on the source and the target. Blank lines and lines starting with a # character are considered as comments.
Note:
The vxrsync utility can accept only SFW volumes having a name as input. Any other volumes cannot be used.