Volume Replicator 7.4.1 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 dynamic disk group while importing
When importing a dynamic disk group, you may need to rename it, if a dynamic disk group of the same name has already been imported on the host. If the dynamic disk group that needs to be renamed contains Volume Replicator objects, then replication does not restart after importing the renamed disk group.
Warning:
Volume Replicator objects are created even if some disks are unavailable while importing the dynamic disk group. However, the Volume Replicator configuration in such a case may be invalid and replication may not restart even after performing the steps that are given below. Importing a partial dynamic disk group after resetting the disk group Host ID may result in losing the integrity of dynamic disk group organization.
Use the following steps to enable replication after the disk group is imported. Ensure that all disks and volumes of the imported dynamic disk group are accessible and in a HEALTHY state before proceeding.
This example assumes that the following setups are already set:
host_imp
The host on which you import the dynamic disk group after renaming.
dg_name_imp
The new name of the dynamic disk group.
All other hosts in the Volume Replicator configuration are referred to as remote host(s).
To enable replication after the disk group is imported
- On host host_imp, find the RLINK objects to remote host(s) for the Volume Replicator configuration, using:
vxprint -g dg_name_imp -P
This displays the list of RLINKs (among other things), in the following format:
rl <rlink_name> attributes
- For each RLINK object in the dg_name_imp dynamic disk group, find the corresponding remote objects, using:
vxprint -g dg_name_imp -l <rlink_name> | findstr "remote_"
This displays the remote objects in the following format:
remote_host = <remote-host-name or ip> remote_dg = <name of the remote disk group> remote_rlink = <name of the corresponding remote rlink>
- For every RLINK on the remote host change the remote_dg attribute of the corresponding remote RLINK using the following commands:
Pause and Resume operations are permitted only on RLINK objects in ACTIVE state. If any of the remote RLINKs are not ACTIVE, then, the Pause operation fails. In such a case, do not perform the Resume operation.
vxrlink -g <remote_dg> pause <remote_rlink> vxrlink -g <remote_dg> set remote_dg=dg_name_imp <remote_rlink>
If the pause operation above succeeded then run the following command:
vxrlink -g <remote_dg> resume <remote_rlink>
Run these commands on each of the remote hosts.
- Verify the changes on every remote host, using:
vxrds -g <remote_dg> printrvg
This command should list the RVGs on host_imp as part of the RDS(s).