Veritas InfoScale™ 7.4.1 Replication Administrator's Guide - Linux
- Section I. Getting started with Volume Replicator
- Introducing Volume Replicator
- Understanding how Volume Replicator works
- How VVR uses kernel buffers for replication
- Replication in a shared disk group environment
- Using SmartTier with VVR
- Understanding the VVR snapshot feature
- About VVR compression
- Planning and configuring replication
- Before you begin configuring
- Choosing the mode of volume replication
- Planning the network
- Sizing the SRL
- Understanding replication settings for a Secondary
- Configuring VVR in a VCS environment
- Using the primary-elect feature to choose the primary site after a site disaster or network disruption
- Requirements for configuring VVR in a VCS environment
- Example setting up VVR in a VCS environment
- Configuring the agents for a bunker replication configuration
- Section II. Setting up and administering VVR
- Setting up replication
- Creating a Replicated Data Set
- Creating a Primary RVG of an RDS
- Adding a Secondary to an RDS
- Changing the replication settings for a Secondary
- Synchronizing the Secondary and starting replication
- Starting replication when the data volumes are zero initialized
- Displaying configuration information
- Displaying RVG and RDS information
- Displaying information about data volumes and volume sets
- Displaying information about Secondaries
- Displaying statistics with the vrstat display commands
- Collecting consolidated statistics of the VVR components
- Displaying network performance data
- Administering Volume Replicator
- Administering data volumes
- Associating a volume to a Replicated Data Set
- Associating a volume set to an RDS
- Associating a Data Change Map to a data volume
- Resizing a data volume in a Replicated Data Set
- Administering the SRL
- Incrementally synchronizing the Secondary after SRL overflow
- Administering replication
- Administering the Replicated Data Set
- Administering Storage Checkpoints
- Creating RVG snapshots
- Using the instant snapshot feature
- About instant full snapshots
- Preparing the volumes prior to using the instant snapshot feature
- Creating instant full snapshots
- About instant space-optimized snapshots
- Creating instant space-optimized snapshots
- About instant plex-breakoff snapshots
- Administering snapshots
- Using the traditional snapshot feature
- Using Veritas Volume Manager FastResync
- Verifying the DR readiness of a VVR setup
- Backing up the Secondary
- Administering data volumes
- Using VVR for off-host processing
- Transferring the Primary role
- Migrating the Primary
- About taking over from an original Primary
- Failing back to the original Primary
- Choosing the Primary site after a site disaster or network disruption
- Troubleshooting the primary-elect feature
- Replication using a bunker site
- Introduction to replication using a bunker site
- Setting up replication using a bunker site
- Using a bunker for disaster recovery
- Replication using a bunker site in a VCS environment
- Troubleshooting VVR
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Tuning replication performance
- SRL layout
- Tuning Volume Replicator
- VVR buffer space
- Tuning VVR compression
- VVR buffer space
- Setting up replication
- Section III. Getting started with File Replicator
- Introducing File Replicator
- Administering File Replicator
- Displaying file replication job information
- Section IV. Analyzing your environment with Volume Replicator Advisor
- Introducing Volume Replicator Advisor (VRAdvisor)
- Collecting the sample of data
- About collecting the sample of data
- Collecting the sample of data on UNIX
- Collecting the sample of data on Windows
- Analyzing the sample of data
- About analyzing the sample of data
- Analyzing the collected data
- Understanding the results of the analysis
- Viewing the analysis results
- Recalculating the analysis results
- Installing Volume Replicator Advisor (VRAdvisor)
- Section V. VVR reference
- Appendix A. VVR command reference
- Appendix B. Using the In-band Control Messaging utility vxibc and the IBC programming API
- Using the IBC messaging command-line utility
- Examples - Off-host processing
- In-band Control Messaging API
- Appendix C. Volume Replicator object states
- Appendix D. Alternate methods for synchronizing the Secondary
- Using the full synchronization feature
- Using block-level backup and Storage Checkpoint
- Using difference-based synchronization
- Examples for setting up a simple Volume Replicator configuration
- Appendix E. Migrating VVR from IPv4 to IPv6
- Migrating VVR to support IPv6 or dual stack
- About migrating to IPv6 when VCS global clustering and VVR agents are not configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured
- About migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Migrating to IPv6 when VCS global clustering and VVR agents are configured in the presence of a bunker
- Appendix F. Sample main.cf files
Interpreting RLINK flag settings
The following table lists the various flags that can appear in the flags field of the vxprint -Pl output.
Note:
The Primary and Secondary RLINKs are communicating only when the connected flag is on. However, replication is taking place only if the following set of flags is displayed:
write enabled attached consistent connected
In all other cases, a corrective action may be needed.
The RDS is in the process of automatic synchronization. | |
attached | The RLINK is attached to the RVG. |
bunker_target | Indicates that this is the RLINK from the Secondary to the bunker node. |
can_sync | If the inconsistent and can_sync flags are set, there is enough information in the Secondary SRL volume to make the Secondary consistent again and capable of taking over. |
cant_sync | The RLINK is inconsistent, and this Secondary needs a complete resynchronization before it can take over or replicate. |
compression_enabled | Indicates that compression is enabled on the RLINK. |
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 an SRL 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. |
fail | An I/O error occurred while writing to a data volume on the Secondary. |
inconsistent | The data in the Secondary volumes is not consistent and the Secondary cannot take over. |
needs_recovery | State after an import or reboot. The vxrecover command clears this state. |
primary_paused | The Primary RLINK has been paused and the RLINKs are not replicating. |
The resynchronization of the Secondary has been started. | |
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 SRL; replication cannot continue until the SRL has been dissociated and a new one associated. |
secondary_paused | The Secondary RLINK has been paused and the RLINKs are not replicating. |
smartsync | Automatic synchronization is being used with SmartMove. |