InfoScale™ 9.0 Replication Administrator's Guide - AIX
- 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 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
- Configuring and administering VVR using System Management Interface Tool
- Accessing Volume Replicator interface in SMIT
- Setting up a simple Volume Replicator configuration using SMIT
- Displaying configuration information using SMIT
- Administering Volume Replicator using SMIT
- Taking instant snapshot of data volumes of an RVG using SMIT
- Associating a volume to a Replicated Data Set using SMIT
- Transferring the Primary role using SMIT
- 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. 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 IV. 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
Displaying consolidated replication status
The vradmin repstatus command displays the consolidated replication status of the specified Replicated Data Set (RDS). The vradmin repstatus command displays the following information about each RVG in the RDS:
Consolidated view of the RDS
Replication settings for all Secondary hosts in the RDS
Status of the data on each Secondary host in the RDS
Status of replication to each Secondary host in the RDS
To display consolidated replication information about an RDS:
# vradmin -g diskgroup [-l] repstatus local_rvgname
The argument local_rvgname is the name of the RVG on the local host. The local RVG name represents its RDS.
The option -l displays additional information, such as RLINK names, replication setting, compression mode, and so on. Similar to the vradmin -l printrvg command, the vradmin repstatus command also displays configuration errors in the RDS, if any.
Note:
If the vradmin repstatus command is run on a Secondary that has a few configuration errors or cannot reach the Primary, the output displays the status known to the Secondary before the above condition occurred and therefore might be out of date.
Example:
When the Primary is reachable from all the Secondary hosts and the vradmin repstatus command is run from any host:
# vradmin -g hrdg -l repstatus hr_rvg
Output resembles:
Replicated Data Set: hr_rvg Primary: Host name: seattle RVG name: hr_rvg DG name: hrdg RVG state: enabled for I/O Data volumes: 4 Vsets: 1 SRL name: hr_srl SRL size: 4.00 GB Total secondaries: 1 Secondary: Host name: london RVG name: hr_rvg DG name: hrdg Rlink from Primary: rlk_london_hr_rvg Rlink to Primary: rlk_seattle_hr_rvg Configured mode: asynchronous Latency protection: off SRL protection: autodcm Data status: inconsistent Replication status: resync in progress (smartsync autosync) Current mode: asynchronous Logging to: DCM (contains 169728 Kbytes) (autosync) Timestamp Information: N/A Bandwidth Limit: 30.00 Mbps Compression Mode: Off
Example:
When the Primary is unreachable from the Secondary hosts and the vradmin repstatus command is run from the Secondary host:
# vradmin -g hrdg -l repstatus hr_rvg
Output resembles:
VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has configuration error. Displayed status information is from Secondary and can be out-of-date. Replicated Data Set: hr_rvg Primary: Host name: seattle <unreachable> RVG name: hr_rvg DG name: hrdg RVG state: enabled for I/O Data volumes: 4 Vsets: 1 SRL name: hr_srl SRL size: 4.00 GB Total secondaries: 1 Secondary: Host name: london RVG name: hr_rvg DG name: hrdg Rlink from Primary: rlk_london_hr_rvg Rlink to Primary: rlk_seattle_hr_rvg Configured mode: asynchronous Latency protection: off SRL protection: autodcm Data status: consistent, up-to-date Replication status: replicating (connected) Current mode: asynchronous Logging to: SRL (0 updates behind, last update ID 18533.0) Timestamp Information: behind by 00:00:00 hours Bandwidth Limit: 30.00 Mbps Compression Mode: Off Last Update on Primary: Oct 10 04:32:21 Secondary up-to-date as of: Oct 10 04:32:21 Config Errors: seattle: Pri or Sec IP not available or vradmind not running, stale information
The following section describes the important fields displayed by the vradmin repstatus command. The values and meaning of each field are listed in tables:
: Displays the state of the Primary RVG. The following table lists the values for the RVG state field and their meanings.
acting_secondary
This Primary RVG is currently the acting Secondary as part of the fast failback process. Writes to the data volumes in this RVG are disabled independent of whether the RVG is started or stopped.
disabled for I/O
Primary RVG is disabled for I/O, that is, the RVG is stopped.
enabled for I/O
Primary RVG is enabled for I/O, that is, RVG is started.
needs recovery
State after an import or reboot.
The vxrvg recover rvg command clears this state.
passthru
The Primary RVG is in passthru mode because the Primary SRL is detached or missing.
: Shows the data status of this Secondary. The following table lists the values for the Data status field and their meanings:
consistent, behind
Secondary data is consistent but not up-to-date with the Primary data.
consistent, stale
The data on this Secondary is consistent. Replication to this Secondary has been stopped; the Primary RLINK is detached.
consistent, up-to-date
The Secondary data is consistent and is current or up-to-date with the Primary data. The Primary role can be migrated to this Secondary.
inconsistent
The data on the Secondary volumes is not consistent and the Secondary cannot take over.
needs recovery
State after an import or reboot.
The vxrlink recover command clears this state.
N/A
Current state of the Secondary data cannot be determined. This may occur because of a configuration error on this Secondary. For information about the state, use the vxprint -l rlink_name command on the Primary and Secondary.
: Displays the mode of replication, asynchronous or synchronous, that is being used to replicate data to the Secondary. This value can be different from the configured replication setting if the configured mode is synchronous=override.
: Displays the status of the replication to the Secondary. The following table lists the values for the Replication status field and their meanings:
Value
Meaning
logging to DCM
DCM is active for this Secondary, that is, new updates on Primary are tracked using DCM for this Secondary. The following information may be displayed:
needs dcm resynchronization - To continue replication, resynchronize the Secondary using DCM resynchronization.
See Incrementally synchronizing the Secondary after SRL overflow.
needs failback synchronization - To continue replication, start failback synchronization to this Secondary.
needs failback synchronization
This Primary RVG is acting as Secondary as part of the fast failback process. To continue replication, start failback resynchronization on the new Primary.
not replicating
Data is not being replicated to Secondary because Primary RLINK is in needs_recovery state.
primary needs_recovery - Primary RLINK in needs_recovery state and needs to be recovered before replication can resume.
paused by user
Replication to Secondary is paused because of some administrative action. This results in the following states:
primary paused - Primary RLINK is paused.
secondary paused - Secondary RLINK is paused.
paused due to error
Replication to Secondary is paused because of the following errors:
secondary config error - Secondary has some configuration error.
See Interpreting RLINK flag settings.
secondary log error - Secondary SRL has an I/O error.
paused due to network disconnection
Replication to Secondary is paused because of some network problem.
replicating
connected - Replication can take place if there are updates on the Primary data volumes
resync in progress
Resynchronization to the Secondary is in progress.
autosync - Resynchronization type is autosync.
dcm resynchronization - Resynchronization after an SRL overflow.
failback resynchronization - Resynchronization using failback logging.
smartsync - Resynchronization type is autosync using SmartMove.
resync paused by user
Resynchronization to Secondary is paused because of some administrative action. This results in the following states:
primary paused - Primary RLINK is paused.
secondary paused - Secondary RLINK is paused.
resync paused due to error
Resynchronization to Secondary is paused because of the following errors:
secondary config error - Secondary has some configuration error.
See Interpreting RLINK flag settings.
secondary log error - Secondary SRL has an I/O error.
resync paused due to network disconnection
Resynchronization to Secondary is paused because of some network problem.
stopped
Replication to Secondary is stopped because of the following:
Primary detached - Primary RLINK is detached.
Secondary detached - Secondary RLINK is detached.
N/A
The replication status cannot be determined. For information about the status, use the vxprint -l rlink_name command on the Primary and Secondary.
: Indicates whether updates for this Secondary are tracked on the Primary using the SRL or DCM. The following table lists the values for the Logging to field and their meanings:
Value
Meaning
DCM (contains xxx Kbytes) (log_type)
DCM is active (in use) for the replication to this Secondary. log_type can be autosync, failback logging, or SRL protection logging.
The yyy% value can sometimes reach beyond 100%. If synchronization is restarted and the DCM map is full, new incoming writes will cause the total yyy% to exceed 100%.
SRL (xxx Kbytes behind, yyy % full)
Updates to be transferred to Secondary are logged into the SRL and are currently occupying xxx Kbytes or yyy% of the SRL
SRL
SRL is used for logging. Check the Data status field for the status of the Secondary data.
If the vradmin repstatus command is run on a Secondary and the Secondary is disconnected from the Primary because of a configuration or network error, the Logging to field may show the following values:
Value
Meaning
DCM (log_type)
The last known information about logging type before the Secondary disconnected from the Primary is that it was logging to DCM.
SRL (xxx updates behind, last update ID yyy)
Before Secondary disconnected from the Primary, SRL was used for logging. Secondary was xxx updates behind the Primary, and the last update that was applied on the Secondary has update ID yyy. This information is similar to that displayed by the vxrlink updates command.
SRL (updates behind N/A)
Before Secondary disconnected from the Primary, SRL was used for logging. The number of updates this Secondary is behind with the Primary is not known.
These fields are the same as the output that is displayed for the vxrlink -T command.
Displays the mode of compression. The values are on or off.