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)
Method 1: Moving the Secondary RVG disk group on to a spare server within the same LAN as the Primary
For example, consider the following scenario in a sample setup where the Primary host name is london and the Secondary host name seattle. The host cambridge is a spare server that exists on the same LAN as the Primary host london.
To move the Secondary RVG disk group on to a spare server
On the Secondary host seattle:
Select the vvr_dg disk group and right-click.
Select the Deport Dynamic Disk Group option from the menu that appears, to deport the disk group vvr_dg on which Secondary RVG vvr_rvg is created.
- Physically ship the disks under this disk group to the system cambridge that is present on the same LAN as that of Primary host: london.
The host cambridge is a spare server that exists on the same LAN as the Primary host london.
On the host cambridge:
Select the vvr_dg disk group and right-click.
Select the Import Dynamic Disk Group option from the menu that appears. Import the disk group vvr_dg on which Secondary RVG vvr_rvg exists on another host by selecting the Clear host ID option.
- Considering that the host IP of cambridge is 10.212.80.252 change the RLINK IP addresses using the commands:
On Primary london vxrlink set remote_host=10.212.80.252 rlk_seattle_vvr_rvg On Secondary Cambridge vxrlink set local_host=10.212.80.252 rlk_london_vvr_rvg
- On host cambridge:
Select the Start Replication operation to start the replication using the Synchronize Automatically option. The operation is much faster over a LAN as compared to that over a WAN.
After synchronization is complete,
On host london
vxrlink pause rlk_seattle_vvr_rvg vxrvlink set remote_host=10.256.88.126 rlk_seattle_vvr_rvg
On host cambridge
vxrlink pause rlk_london_vvr_rvg vxrvlink set local_host=10.256.88.126 rlk_london_vvr_rvg
- Deport the disk group from host cambridge and ship the disks back to the original Secondary host seattle. Now, import the disk group on host seattle. Import the disk group on another host by selecting the Clear host ID option.
- Resume the RLINKs that were paused in step 6.