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)
Interpreting RLINK flag settings
The following table lists the various flags that can appear in the flags field of the vxprint -Pl output.
The Primary and Secondary RLINKs communicate only when the connected flag is on. However, replication takes place only if the following set of flags is displayed
write enabled attached consistent connected
In all other cases, corrective action may be needed. The following table explains the flags settings available for this command:
autosync | The RDS is in the process of Automatic Synchronization. |
attached | The RLINK is attached to the RVG. |
cant_sync | The RLINK is inconsistent, and this Secondary needs a complete resynchronization before it can take over or replicate. |
connected | The RLINK is connected to the corresponding RLINK on the remote host and replication can take place. |
consistent | The state of the data volumes on the Secondary is suitable for takeover. |
dcm_logging | DCM is in use, due to either autosync, failback sync, or a Replicator Log overflow. |
detached | The RLINK is STALE and not taking part in replication. |
disabled | The RLINK is not attached and is not replicating. |
disconnected | The two RLINKs are not connected and are not replicating. |
enabled | The RLINK is attached. If the connected flag is displayed, replication can take place. If the disconnected flag is displayed, replication is not taking place. |
inconsistent | The data in the Secondary volumes is not consistent and the Secondary cannot take over. |
needs_recovery | State after an import or system restart. The vxrecover command clears this state. |
Primary_paused | The Primary RLINK has been paused and the RLINKs are not replicating. |
resync_started | The resynchronization of the Secondary has been started. |
resync_paused | The resynchronization has been started but is not currently active because of some problem. |
Secondary_config_err | There is a mismatch between the configuration of the volumes on the Primary and the Secondary, either a volume is missing on the Secondary or its length is not the same as that of the corresponding volume on the Primary. |
Secondary_log_err | An I/O error has occurred on the Secondary Replicator Log; replication cannot continue until the Replicator Log has been dissociated and a new one associated. |
Secondary_paused | The Secondary RLINK has been paused and the RLINKs are not replicating. |
Bunker_sync | Indicates that the RVG to which the RLINK is associated can be synchronized from a Bunker host that the RLINK points to. |
Bunker | Indicates that the RVG to which the RLINK is associated is a Bunker RVG, or the RLINK points from a normal Primary to a Bunker Secondary. |