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)
Adding or removing the DCM logs from the data volumes
By default, Volume Replicator adds DCM logs to all the volumes that are part of the RVG. The DCM log is used for automatically synchronizing the Secondary, when a new Secondary is added to the RDS. If the Replicator Log overflows when the Replicator Log protection has been set to DCM or AutoDCM then the DCM logs are used for resynchronizing the Secondary. The DCM log is also used for fast-failback logging and resynchronizing the original Primary when it comes up after a disaster.
If the RVG is part of a cluster setup, then from the VEA you must connect to the host which is the cluster virtual server by using the virtual name or address that was used when configuring the server.
If a volume has a DCM log, then the right-click menu displays only the Remove DCM Log option. However, if the volume does not have a DCM log then the Add DCM Log option is available.
Note:
The Add DCM Log or Remove DCM Log option is available only if the hosts to which the volumes belong is connected to VEA.
To remove the DCM log
- Select the data volume and right-click. Select the Remove DCM Log option from the menu that appears.
- The Remove DCM Log dialog box appears.
Click Yes to Remove the DCM Log from the selected volume. Click No to cancel the operation.
This option is a toggle and only if the volume has a DCM log is the Remove DCM Log option displayed.
To add a DCM log
- Select the data volume and right-click. Select the Add DCM Log option from the menu that appears.
- The Add DCM Log dialog box appears.
Click Yes to add the DCM Log from the selected volume. Click No to cancel the operation.
This option is a toggle and only when the volume does not contain a DCM log, the Add DCM Log option displayed.