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 the status of a Secondary
Use the vxrlink status command to determine the status of a Secondary. This command displays different information depending on what state the replication is in for that Secondary. For example, whether the Primary is currently replicating to the Secondary, synchronizing the Secondary with a Storage Checkpoint, using the DCM to resynchronize the Secondary, or using automatic synchronization for the Secondary. To determine the state of the replication, use the vradmin repstatus command.
See Displaying consolidated replication status.
If the state is replicating, the vxrlink status command displays whether the Secondary corresponding to the specified RLINK is up-to-date and if not, how much the Secondary is behind.
Note that outstanding writes are shown even if the Secondary is replicating in synchronous mode. Although for synchronous mode, the write is considered complete to the application when the network acknowledgment is received from the Secondary, VVR still considers the write outstanding until it is written to the data volume on the Secondary.
If automatic synchronization or DCM resynchronization is in progress, the vxrlink status command shows the progress of the automatic synchronization.
To show the status of a Secondary
# vxrlink -g diskgroup status rlink_name
If replication is in progress, the output resembles:
VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (17%) on the SRL
If automatic synchronization is in progress, the output resembles:
VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 100864 Kbytes remaining.
If DCM resynchronization is in progress, the output resembles:
VxVM VVR vxrlink INFO V-5-1-12887 DCM is in use on Rlink rlink_name. DCM contains 7200 Kbytes (1%) of the Data Volume(s).
To display the Secondary status periodically, specify a time interval using the -I option. For example, to print the status of the Secondary every five seconds, use the command:
# vxrlink -g diskgroup -i5 status rlink_name
If replication is in progress, the output resembles:
VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (17%) on the SRL VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (19%) on the SRL
If automatic synchronization is in progress, the output resembles:
VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 100864 Kbytes remaining. VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 94464 Kbytes remaining.
If automatic synchronization is in progress and SmartMove is enabled, the output resembles:
VxVM VVR vxrlink INFO V-5-1-0 Rlink rlink_name is in SMART AUTOSYNC. 2425696 Kbytes remaining. VxVM VVR vxrlink INFO V-5-1-0 Rlink rlink_name is in SMART AUTOSYNC. 2367840 Kbytes remaining.
To display the status of an RLINK with a timestamp, use the vxrlink status command with the -T option. This is useful if the Secondary is not up-to-date. The output of the command displays a timestamp in the locale's appropriate time format to indicate the time by which the Secondary is behind.
For example, if there are pending writes in the Primary SRL, use the following command to check the status of the Primary:
# vxrlink -g diskgroup -T status rlink_name
The output resembles:
VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (20%) on the SRL VxVM VVR vxrlink INFO V-5-1-0 Rlink rlink_name is behind by 0:00:40 hours
The second message indicates the time by which the RLINK is behind.
Note:
If the system time is reset to a value different from that of the current system time, then, the output of the vxrlink -T status command will appropriately show a negative or an inaccurate value, until the updates that were done before resetting the system time get replicated.