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 3: Using mirrored plexes to synchronize the Secondary
Another method to synchronize the Secondary without using the
option is by using the mirrored plexes. Consider that on host london the data volumes vvr_dv01 and vvr_dv02 are created with mirrored plexes. The mirrored plexes are always synchronized with the source volumes.Note:
Veritas recommends creating mirrors for each volume on separate disks so as to avoid problems or issues when you perform a mirror-breakoff. Also make sure that the disks you use are clean disks.
To synchronize the Secondary using mirrored plexes on Primary host london
- Create additional mirrors for the volumes vvr_dv01 and vvr_dv02 under the RVG using the Mirror > Add option from the <volume-name> right-click menu.
- Start a checkpoint using the Start Checkpoint option from the Primary RVG right-click menu or using the command:
vxrvg -g vvr_dg -c checkpt1 checkstart vvr_rvg
- Break off the mirrors from the volumes: vvr_dv01 and vvr_dv02 using the Break Mirror option.
In the Break Mirror dialog box select the mirror that needs to be broken based on the disk on which they are located. The dialog lists the different disks. Select the one on which the mirror exists.
Specify a drive letter for the mirror-breakoff.
Click OK.
- The mirror-breakoff is created with the default name on the specified disk.
- Split the disk group to create a new disk group temp_dg with the mirror-breakoff volumes.
- End the checkpoint using the End Checkpoint option from the Primary RVG right-click menu or using the command:
vxrvg -g vvr_dg checkend vvr_rvg
- Deport the disk group temp_dg.
- Physically ship the disks that contain the mirror-breakoff volume to the Secondary host seattle.
To synchronize the Secondary using mirrored plexes on Primary host seattle
- Import the disk group temp_dg on which the mirror-breakoff volumes are present by selecting the Clear host ID option.
If you cannot see the newly added disk group temp_dg perform a rescan operation using the Rescan option from the Actions menu.
- Perform a disk group join operation by selecting the Join Dynamic Disk Group from the disk group right-click menu.
This adds the new temp_dg with the mirror-breakoff volumes to the vvr_dg disk group.
If a volume with the same name vvr_dv01 and vvr_dv02 as that on the Primary exists on the Secondary disk group vvr_dg then:
Stop replication on the Secondary RVG.
Dissociate the volumes from the RVG by running the following command:
vxrvg -g vvr_dg -r vvr_rvg dis vvr_dv01vxrvg -g vvr_dg -r vvr_rvg dis vvr_dv02
Delete the volumes vvr_dv01 and vvr_dv02 since you would need to recreate it from the Primary mirror-breakoff volumes.