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)
Displaying the RLINK status
Use the vxrlink status command to display the replication status of the Secondary, represented by the specified RLINK. This command can be run only on the Primary. During normal replication, if the Secondary is not up-to-date, the command displays the number of outstanding writes, and the percentage of the Replicator Log used by this RLINK. The command also displays the status of the autosynchronization process when it is in progress.
Use the -i <interval> option to display the replication status at the specified time intervals.
The -t <timestamp> option specifies the number of lines after which the current date and time is displayed.
Use the -T option to display the units of time by which the Secondary lags if it is not up-to-date.
When failback logging is enabled this command can be used on the new Primary and the original Primary. If the vxrlink status command is used on the new Primary, the command displays the status of the RLINK corresponding to the original Primary.
After takeover, if the vxrlink status command is used on the original Primary (acting Secondary) then the command appropriately displays the status of the Replicator Log or DCM replay being performed to the new Primary.
Syntax for vxrlink status command
vxrlink [-g <diskgroup>] [-r <rvg>] [-i <interval>] \[-t <timestamp>] [-T] status <rlink>
Example
vxrlink -g vvrdg -r rvg -i 5 status rlink_sec_host
Note:
Interval must be specified in seconds. If the interval (-i option) value is not specified, then the statistics are displayed only once.
vxrlink -i1 -t 10 -T status rlink_sec_host
The output resembles:
4/6/2005 11:38:21 AM RLINK is up to date. RLINK is up to date. RLINK has 47 outstanding writes, occupying less than 1% (2994 KB) of the Replicator Log. RLINK rlink_sec_host is behind by 0 hrs 0 mins 0 secs with respect to Primary. RLINK has 56 outstanding writes, occupying less than 1% (3591 KB) of the Replicator Log. RLINK rlink_sec_host is behind by 0 hrs 0 mins 0 secs with respect to Primary. RLINK has 102 outstanding writes, occupying less than 1% (6371 KB) of the Replicator Log. RLINK rlink_sec_host is behind by 0 hrs 0 mins 0 secs with respect to Primary. 4/6/2005 11:38:31 AM RLINK has 101 outstanding writes, occupying less than 1% (6371 KB) of the Replicator Log. RLINK rlink_sec_host is behind by 0 hrs 0 mins 0 secs with respect to Primary. : : : : : : : RLINK has 40 outstanding writes, occupying less than 1% (2600 KB) of the Replicator Log. RLINK rlink_sec_host is behind by 0 hrs 0 mins 15 secs with respect to Primary. RLINK is up to date. RLINK is up to date. RLINK is up to date. 4/6/2005 11:38:54 AM RLINK is up to date.
More Information