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)
RVG states
There are icons that represent all Volume Replicator objects. Of these, only the RVG icon changes to represent the current state of the RVG.
The following table explains the different RVG states. The icons column lists the various icons that are used to represent each state on the Primary and Secondary. The Primary and Secondary columns indicate the validity of the state for each of these hosts. The command line interface column represents the equivalent of the GUI states on the command line, that is, the output of the vxprint -l command.
Table: Volume Replicator object icons
Primary Icon | Secondary Icon | State | Description |
---|---|---|---|
Data Access Enabled CLI States: ACTIVE Valid for Primary and Secondary | Indicates that the data volumes under the RVG are enabled for Input/Output, that is, these volumes can be used for writing and reading data. | ||
Data Access Disabled CLI States: CLEAN Valid for Primary and Secondary | Indicates that the data volumes under the RVG are disabled for Input/Output and volumes are unavailable for reading or writing data. | ||
Failed CLI States: fail Valid for Primary and Secondary | The failed flag is set if the incoming Input/Output cannot be written to the underlying data volumes due to some problem with the data volumes. | ||
Autosynchronizing CLI States: autosync Valid for Secondary only | Indicates that Automatic Synchronization has started. | ||
Resynchronization Paused CLI States: resync_paused Valid for Secondary only | Indicates that resynchronization is paused. | ||
Resync Started CLI States: resync_started Valid for Secondary only | Indicates that resynchronization is in progress. | ||
Inconsistent CLI States: inconsistent Valid for Secondary only | This state is displayed only for the Secondary RVG, when the data on the Secondary volumes is inconsistent with respect to Primary RVG. The Secondary may become inconsistent when the resynchronization or autosynchronization is in progress. The Secondary may also become inconsistent when the RVG goes into Failed state. | ||
Replicator Log Header Error CLI States: srl_header_err Valid for Primary and Secondary | This error is encountered when attempts to access the header section of Replicator Log are unsuccessful. | ||
DCM Active CLI States: dcm_logging (only in case the Replicator Log overflows) Valid for Primary only | Indicates that the DCM is in use, either due to autosynchronization, resynchronization, fast-failback logging, or Replicator Log overflow. | ||
Fast-failback Logging CLI States: failback_logging Valid for Primary only | Indicates that Volume Replicator logs new updates to the Primary using the DCM logging. | ||
No Replicator Log CLI States: passthru Valid for Primary and Secondary | This state is encountered when the Replicator Log is not associated with the RVG. | ||
Primary Replicator Log error CLI States: passthru Valid for Primary only | This state is encountered if the Primary receives Input/Output error when attempting to read from or write to its log volume. | ||
Checkstarted CLI States: awaiting_checkend Valid for Primary only | Indicates that the checkpoint has started and awaits checkend. | ||
Not Recovered CLI States: needs_recovery Valid for Primary and Secondary | This state is encountered if the RVG does not recover automatically after a system restart. | ||
Acting as Secondary CLI States: acting_Secondary Valid for Primary only | Indicates that the original Primary RVG is currently the acting Secondary as part of the fast-failback process. Writes to the data volumes in this RVG are disabled irrespective of whether the RVG is started or stopped. |