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)
Renaming mirror-breakoff volumes on the Secondary host
If a volume with the same name as that on the Primary host does not exist on the Secondary then you need to rename the volumes. This can be done either using the VEA GUI or CLI.
Note:
Using the -f option without caution can cause data corruption as the Secondary may sometime miss the writes that may have been present on the Replicator Log but did not reach the Secondary. As there is no way of knowing whether the Replicator Log had some pending writes that have not reached Secondary, use this option only when the Secondary is completely up-to-date with the Primary.
To rename the mirror-breakoff volumes on the Secondary host seattle perform the following steps
- Identify the volume names from the volume view, with the help of the volume's drive letter. Assuming that the default name is default_vol01 and devault_vol02, prepare these volumes:
vxassist -g vvr_dg prepare default_vol01 <disk name> vxassist -g vvr_dg prepare devault_vol02 <disk name>
The disk name can be obtained by running the vxvol volinfo command.
- Perform the snapshot operation using the following command.
vxassist -g vvr_dg snapshot default_vol01 vvr_dv01 vxassist -g vvr_dg snapshot devault_vol02 vvr_dv02
- From the VEA GUI, expand the Volumes node in the tree view.
- Right-click the desired data volume node.
- Select Change Volume Internal Name from the context menu.
A dialog box appears.
- Enter the new internal name of the volume.
- Click OK to complete the operation through the VEA.
or
Open a command window and run the following command:
vxedit [-g DynamicDiskgGroupName] [-f] rename <OldName><NewName>
- Associate the volumes to the RVG by running the following commands
vxrvg -g vvr_dg assoc vvr_rvg vvr_dv01vxrvg -g vvr_dg assoc vvr_rvg vvr_dv02
- Select the Start Replication option from the Secondary RVG right-click menu. The Start Replication menu appears. Select the Synchronize from Checkpoint option to synchronize the Secondary from the checkpoint checkpt1 you had created.
- Verify that the replication state is Active by checking the Replication Status field in the right pane of the Secondary RVG view or using the command:
vxprint -PVl vvr_rvg