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)
Adding a Bunker node
Use the vxrds addbunker command to add a Bunker to an existing RDS without interrupting replication from the Primary to the Secondary.
On the Bunker node, create only the Bunker Replicator Log volume. You do not require to create the data volumes. Make sure that the Bunker Replicator Log is of the same size and has the same name as the Primary Replicator Log. The vxrds addbunker command takes care of creating the Bunker Secondary RVG and establishing the required RLINKs. To create the RLINKs with the names of your choice between the Primary and Bunker Secondary RVG use the vxrds addbunker command with the prlink and srlink attributes.
Note:
Adding the Bunker RVG fails if the Replicator Log sizes differ. The Bunker Replicator Log must be of the same size and the same name as the Primary Replicator Log.
Syntax forvxrds addbunker command command:
vxrds [-g <diskgroup>] [-bdg <diskgroup>] addBunker <local_rvg><pri_host> <Bunker_host> [attribute=value..]
Example:
vxrds -g dg1 -bdg Bunker_dg addBunker local_rvg london london1protocol=storage
where dg1 is the Primary disk group and Bunker_dg is the Bunker disk group.
The following table describes the attributes that you can specify with vxrds addbunker command.
Table: Attributes for vxrds addbunker command
Attributes | Description |
---|---|
protocol | Specifies the protocol to be used for replication between the Primary and Bunker Secondary. If the storage on the Bunker Secondary is directly accessible from the Primary use the STORAGE protocol, otherwise use TCP/IP or UDP/IP. Note: If the replication protocol for the Bunker Secondary has been set to STORAGE, then you can change it only by deleting and recreating the Bunker with the required protocol; UDP/IP or TCP/IP. You cannot change the STORAGE protocol using the Change Replication Settings option. |
-bdg <diskgroup> | Specifies the Bunker disk group in a storage Bunker set up that is used for creating the Bunker RVG. |
prlink | Creates the Primary RLINK with the specified name. |
srlink | Creates the Bunker Secondary RLINK with the specified name. |