Veritas InfoScale™ 8.0.2 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
- VVR event notification
- 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 as a log plex
- 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
About adaptive synchronous replication
When the synchronous attribute is set to override, synchronous mode switches to asynchronous mode during a temporary network outage. After the outage passes, the Secondary catches up and replication reverts to synchronous.
The override option allows VVR to continue receiving writes from the application in asynchronous mode even when RLINK is disconnected. However, in case of high network latency, replication continues to run in synchronous mode with degraded application performance.
The adaptive synchronous mode in VVR is an enhancement to the existing synchronous override mode. In the adaptive synchronous mode, replication switches from synchronous to asynchronous based on cross-site network latency. This allows replication to take place in synchronous mode when network conditions are good, and automatically switch to asynchronous mode when there is an increase in cross-site network latency. You can also set alerts to notify you if the system undergoes network deterioration. The alerts are logged in the system log file and the /etc/vx/log/vxloggerd.log
file.
Note:
The adaptive synchronous replication mode does not support replication over multiple secondary sites.
You must define the following attributes to enable the adaptive synchronous replication.
Table: Required attributes for adaptive synchronous replication
Attribute | Description |
---|---|
synchronous | Set the synchronous attribute of the RLINK to override. By default, VVR sets the synchronous attribute to off. Setting the synchronous attribute to override puts the RLINK in synchronous mode and specifies override behavior if the RLINK is disconnected. |
iotimeout | Define the iotimeout attribute to specify the time interval, in microseconds (μs), for which the Primary waits for an acknowledgment from the Secondary, before considering an update to be timed out. The iotimeout attribute must be defined by the user and is required by VVR to replicate to a Secondary in the adaptive synchronous mode. |
Additionally, you can define the following attributes to modify the override behavior of the adaptive synchronous replication.
Table: Optional attributes for adaptive synchronous replication
Attribute | Description | Default Value |
---|---|---|
threshold | Maximum permissible value, in percentage, of the updates that were sent to the Secondary and were timed out within a user-defined time interval. VVR uses the threshold value to determine when to switch from synchronous to asynchronous mode. | 30% |
interval | Time interval, in seconds, that is used for calculating the percentage of timed out updates. | 60 seconds |
switch_timeout | Minimum time interval, in seconds, for which the system must remain in asynchronous mode, before switching back to synchronous mode. | 300 seconds |
threshold_monitor | Threshold value, in percentage, of timed out updates. This attribute is used to notify the user in advance of a potential degradation in the network. When the percentage of timed out updates exceeds this value, it is considered as an early indication of network deterioration, and an email alert is sent to the user. | 5% |
async_backlog_threshold | If replication is running in the asynchronous mode for period longer than the value specified in this attribute, an email notification is sent to the user. | 300 seconds |
autowitch | This attribute specifies whether the system automatically switches between synchronous and asynchronous replication mode based on the threshold value, that is, the network conditions. By default, this value is set to off. Set the autowitch value to on, if you want the system to switch to the asynchronous mode when the network is degraded and switch back to synchronous mode when network conditions improve. Note: Email notifications for threshold_monitor and async_backlog_threshold attributes are sent by the system irrespective of whether autowitch is set to on or off. | off |