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)
Restoring the Secondary
Use this option to restore the Secondary when its replication status is displayed as Failed.
During active replication if you find that the data on the Secondary is inconsistent or corrupted then you can rollback the Secondary to a known good state with the help of the restore feature. You can first restore the Secondary volumes from the backup and then restore the Secondary from a known Secondary or RLINK checkpoint that is associated with the backup.
To restore the Secondary, it is essential that the Replication status of the Secondary must be in the Failed state. Hence, if the replication status is Active then you can forcefully fail the Secondary before restoring it. If there are writes on the Primary node that have not been copied to the Secondary node, then the Restore operation displays a message stating that there may be a loss of writes temporarily. The Restore option enables you to reestablish the link between the Primary and the Secondary and then writes the data on to the Secondary. After the restore operation completes, the Secondary is up-to-date. This option is enabled only if any checkpoints are available for the selected Secondary.
To restore the Secondary
- Select Restore from Secondary RVG right-click menu or select the Restore option from the toolbar. The Restore Replicated Volume Group dialog box appears.
Select the Confirm this operation on the Secondary option to forcefully fail the Secondary. The OK option is enabled only when you select this option. Click OK to proceed.
- The Restore Replicated Volume Group dialog box appears.
- Specify the checkpoint from which to update the Secondary data volumes in the Checkpoint field by selecting the appropriate one from the list.
- Click OK to restore the connection between the Primary and the Secondary nodes and synchronize the Secondary data volumes from the required checkpoint.