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)
Creating new RLINK
Use the vxrlink make command to create a new RLINK based on the attributes that have been specified.
Syntax for vxrlink make command
vxrlink -g <diskgroup> make <name> attribute=value
Example
vxrlink -g vvrdg make rlk_sechost synchronous=override \ local_host=prihost remote_host=sec_host remote_dg=vvrdg \ remote_rlink=rlk_prihost srlprot=off latencyprot=fail \ latency_high_mark=10000 latency_low_mark=9950 protocol=TCP
The following table lists the attributes that can be specified for the vxrlink make command.
Table: Attributes for the vxrlink make command
Attribute | Description |
---|---|
synchronous | Indicates the mode in which the RLINK should operate; synchronous, asynchronous, or synchronous override mode. The attribute can be set to one of the following values:
|
local_host | Sets the name or IP address of the local host. |
remote_host | Sets the name or IP address of the remote host. |
remote_dg | Sets the name of the remote disk group. |
remote_rlink | Sets the name of the remote RLINK. |
latencyprot | Indicates whether latency protection is enabled for the RLINK. The attribute can have one of following values:
|
srlprot | Enables or disables log protection. The data volumes must have a DCM log for srlprot to be set to DCM or AutoDCM. This attribute can be set to the following values: srlprot=autodcm enables log protection. The DCM logs are used to synchronize the data when the Replicator Log overflows, even when the Primary and Secondary are connected. srlprot=dcm enables log protection. The DCM logs are used to synchronize the data if the Replicator Log overflows, when the Primary and Secondary are disconnected. srlprot=override enables log protection. If the Secondary is still connected and the Replicator Log is about to overflow then the writes are stalled until a predetermined amount of space, (that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log. The log protection is automatically disabled if the Secondary becomes inactive due to a disconnection or administrative action, and Replicator Log will overflow. srlprot=fail enables log protection. If the log is about to overflow the writes are stalled until a predetermined amount of space, that is, 5% or 20 MB (whichever is lesser) becomes available in the Replicator Log. If the connection between Primary and Secondary RVG is broken, then, any new writes to the Primary RVG are failed. srlprot=off disables log protection. |
latency_high_mark | Specifies the maximum number of outstanding requests that are allowed when latency protection is enabled. |
latency_low_mark | Specifies a value such that, when the writes are stalled because the number of outstanding write requests is higher than latency_high_mark value, then, the number of outstanding requests must drop to this value before latency protection is disabled. |
packet_size | Specifies the size of packets in which data can be sent over the network during replication. |
bandwidth_limit | Specifies a value that can be used to control the bandwidth that Volume Replicator needs to use for replication. If this attribute is not specified,Volume Replicator uses the entire available bandwidth for replication. To disable bandwidth throttling, set this attribute to none. Note that the specified bandwidth value must be at least 56 Kbps. You can specify the value in units of Kbps, Mbps, Gbps, or bps. The default is Kbps. If no value is specified then bandwidth throttling is disabled. |
protocol | Specifies the protocol to be used for replication between the Primary and Secondary. Specify TCP or UDP. |
bunker | Specifies the bunker flag. The value can be either true or false. |
bunker_target | Specifies the bunker_target flag. The value can be either true or false. |
Compression | Specifies whether compression is enabled or disabled and as such takes the value of true or false respectively. |