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)
Migrating VVR to support IPv6 or dual stack
Before you proceed, make sure that a new IPv6 address is plumbed on the primary and the secondary nodes, and that the new IP is reachable from the peer nodes.
To migrate VVR to a dual-stack configuration
- Configure an additional IPv6 address on each node at each of the sites, thereby making them dual stack. Make sure that the newly added IP is reachable from all the other peer nodes.
- Change the IP addresses for the RLINKs of the secondary and the primary by using the Change Replication Settings dialog box.
See Changing the Primary and Secondary IP.
Alternatively, use the CLI commands in the following order:
To change IP addresses for the RLINK of the secondary, perform these tasks on the secondary:
Change the secondary IP address.
vxrlink set local_host=newSecondaryIP rlinkToPrimary
For example:
vxrlink set local_host=2620:128:f0a2:9005::130 rlk_seattle_vvr_rvg
Change the primary IP address.
vxrlink set remote_host=newPrimaryIP rlinkToPrimary
For example:
vxrlink set remote_host=2620:128:f0a2:9005::140 rlk_seattle_vvr_rvg
To change IP addresses for the RLINK of the primary, perform these tasks on the primary:
Change the primary IP address.
vxrlink set local_host=newPrimaryIP rlinkToSecondary
For example:
vxrlink set local_host=2620:128:f0a2:9005::140 rlk_london_vvr_rvg
Note:
The new primary IP that you specify must exist on the local host. Run the ipconfig command on the primary host to verify that it exists
Change the secondary IP address.
vxrlink set remote_host=newSecondaryIP rlinkToSecondary
For example:
vxrlink set remote_host=2620:128:f0a2:9005::140 rlk_london_vvr_rvg
Note:
The new secondary IP that you specify must exist on the remote host. Run the ipconfig command on the secondary host to verify that it exists.