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)
Migrating the Primary to a Secondary
Use the vxrds migrate command to interchange the Primary role with the specified Secondary. The new_Primary_hostname parameter specifies the Secondary host. The Primary role can only be migrated when the Secondary is active, consistent, and up-to-date. The data volumes in the RDS must be inactive, that is, the applications that are involved in replication must be stopped before you run the vxrds migrate command. After the migration is complete, the Primary and Secondary roles are interchanged.
If the original Primary has multiple Secondary hosts, and the RLINKs between every pair of Secondaries have not been created, then, after migrating the Primary role to one of the Secondaries or performing takeover on one of the Secondaries, all the remaining Secondaries in the RDS become orphan. You must manually delete these Secondaries and then again add them as Secondaries to the new Primary.
However, if RLINKs have been created between each pair of Secondaries in the RDS, then following steps can be used after migrate or takeover operation to add the orphaned Secondaries back in the RDS.
Syntax for vxrds migrate command
vxrds [-g <diskgroup>] migrate <local_rvg> <new_Primary_hostname>
Example
vxrds -g vvrdg migrate rvg sec_host
To migrate the Primary to a Secondary
- On each orphaned Secondary host, detach the RLINK on this orphan Secondary pointing to the original Primary (the Primary host before migrate or takeover).
- The orphan Secondaries join the RDS of the new Primary. Now, start replication with Automatic Synchronization on each of these orphans.
- Alternatively, you can use the vxrsync utility to bring the Secondaries up-to-date. To do this, Start a checkpoint using the Start Checkpoint option. Use the vxrsync utility to perform difference-based synchronization to the Secondaries from the new Primary host.
After the synchronization completes, End the checkpoint using the End Checkpoint option.
Select the Synchronize from Checkpoint option to start replication from checkpoint to synchronize the Secondary with the writes that happened when vxrsync was in progress
Because the RLINKs for the other Secondary hosts are still associated you do not need to use the vxrds addsec command to add the existing Secondary hosts to the new Primary after the migrate or takeover operation.
You can choose to perform Automatic Synchronization or difference-based synchronization depending on the amount of the data that exists on the volumes. For example, if you have large volumes, but the actual data on it is very small, then Automatic Synchronization can be used as the intellisync option synchronizes only those bits of data that changed. However, if you have large amounts of data with comparable changes then the vxrsync difference-based synchronization is a better option.
If the RVG is part of a VCS cluster and the RVGPrimary resource for the Primary RVG exists, then Volume Replicator fails the vxrvg migrate command for this RVG.