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)
Updating the Secondary from the Bunker
When disaster strikes and the Primary host becomes unavailable, update the Secondary from the Bunker using the following steps.
Note:
If the Primary Replicator Log has overflowed for a Secondary, or if the Secondary is inconsistent because it is resynchronizing, you cannot use the corresponding Bunker Replicator Log to recover the Secondary. Because the Bunker node does not have data volumes, it cannot use DCM to track overflows.
Note:
As the Bunker Replicator Log does not store Primary checkpoints, it does not support attaching the Secondary from a checkpoint.
To update the Secondary from the Bunker
- Activate the Bunker by using the following command from the Bunker host:
vxrds -g vvrdg activatebunker vvrrvg
This converts the Bunker RVG to a Primary, that is from receiving mode (Secondary) to replicating mode (Primary).
The activatebunker command needs to be run only once, even if you update multiple Secondaries.
- Start replication to the Secondary from the Bunker host.
vxrds -g vvrdg -b startrep vvrrvg VVRSEC
This command switches the RLINK on the Secondary that points to the original Primary to point to the Bunker node which is now the Primary and begins replaying the Bunker Replicator Log.
If you have more than one Secondary that uses this Bunker, repeat the vxrds startrep command for each Secondary.
- Monitor the status of the replication from Bunker to Secondary using the Monitor view.
- When the replay is complete, verify that the Secondary is up-to-date using the vxrlink status command.
- Stop replication to the Secondary. You can also stop the replication before the replay is finished, for example, if the Primary is restored or depending on your RTO.
vxrds -g vvrdg stoprep vvr_rvg seattle
You can also choose not to replay the Bunker Replicator Log, after a disaster at the Primary, if you want zero RTO. However, in this case the pending updates that were present on the Bunker Replicator Log are lost.
- After using the Bunker for replay, if it is no longer needed for any more replays, the Bunker should be deactivated. Deactivate the Bunker only after all the replays from the Bunker have been stopped.
To deactivate the Bunker, issue the following command from the Bunker node:
vxrds -g vvrdg deactivatebunker vvr_rvg
The command needs to be run only once.
- The Secondary is now ready for take over.
More Information