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)
Performing RLINK Operations using the vxrlink command
RLINK objects are associated with RVGs. Each RLINK on a Primary RVG represents the communication link from the Primary RVG to a corresponding Secondary RVG. An RLINK on a Secondary RVG represents the communication link from the Secondary RVG to the corresponding Primary RVG.
An RLINK reads data from the Replicator Log volume and sends it to the Secondary. All the RLINKs in an RVG share the Replicator Log volume, and each RLINK reads data at its own rate. An update is removed from the Replicator Log volume when all the RLINKs have successfully sent the update to the Secondary.
The vxrlink command along with its keywords and options can be used to perform the Volume Replicator operations on the RLINKS.
The following table lists the keywords that are available with the vxrlink command and their respective descriptions.
Table: Keywords available for vxrlink command
Keyword | Description |
---|---|
assoc | Associates an RLINK to an RVG. |
att | Attaches an RLINK to an RVG. |
cplist | Displays the list of currently available Secondary checkpoints. |
checkdelete | Deletes the specified Secondary checkpoint. |
det | Detaches an RLINK from an RVG. See Detaching an RLINK. |
dis | Disassociates an RLINK from an RVG. |
make | Creates an RLINK. See Creating new RLINK. |
pause | Pauses an RLINK. See Pausing the RLINK. |
recover | Recovers an RLINK. See Recovering the RLINK. |
restore | Restores an RLINK. See Restoring the RLINK. |
resume | Resumes an earlier paused RLINK. See Resuming the RLINK. |
rm | Deletes an RLINK with the given name. See Removing the RLINK. |
set | Sets the attributes of the specified RLINK. |
stats | Displays the network statistics for the specified Secondary. |
status | Displays the replication status for a specific Secondary. |
updates | Displays the ID of the latest update the Secondary received and the number of updates by which the Primary is ahead. |
verify | Verifies the specified RLINK or all the RLINKs in the RVG for configuration errors. See Verifying the RLINK. |
startstats | Verifies the bandwidth usage by RLINKs in an RDS by starting the historic bandwidth data collection in the form of a graph file. See |
stopstats | Verifies the bandwidth usage by RLINKs in an RDS by stopping the historic bandwidth data collection in the form a graph file. See |
The following table lists the options that are available with the vxrlink command.
Table: Options available for the vxrlink command
Option | Description |
---|---|
-a | Automatically attaches and synchronizes the Secondary data volumes. Optionally used with the att command on the Primary. Note: The autosync operation proceeds only if all the data volumes in an RDS or Primary have DCM logs and if the RLINK is able to connect to the Secondary. |
-c <checkpoint> | Attaches an RLINK which is consistent up to the point indicated by the checkpoint string. The -c option can be used with the:
|
-f | Forces the attach of an RLINK to an RVG to succeed, even though the -a or -c <checkpoint> option was not specified. Note: This -f option can cause data corruption because the Secondary may miss the writes that may have been present on the Replicator Log but did not reach the Secondary. Because there is no way of knowing whether the Replicator Log had some pending writes that have not yet been sent to the Secondary, use this option only if you know that the Secondary is completely up-to-date. |
-g <diskgroup> | Specifies the local disk group for the operation. |
-i <interval> | Displays the network statistics or replication status at the specified intervals in seconds specified by this option. |
-r <rvg> | Specifies the name of the RVG with which the RLINK is associated. If the RVG name is not specified, the RLINK is examined to retrieve the name of the associated RVG. |
-t <timestamp> | This option specifies the number of lines in the output after which the timestamp is displayed. |
-T | Displays the actual difference in time by which the Secondary is behind. |
-w | Forces a Secondary RLINK into the FAIL state. Used only in special circumstances such as the Secondary online backup. The RLINK status is displayed as inconsistent. |