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
Secondary SRL header error cleanup and recovery
An SRL header failure on the Secondary puts the Secondary RVG into the fail state, and sets the RLINK state to the PAUSE state on both the Primary and Secondary. Because information about data volume errors is kept in the SRL header, the correct state of data volumes is not guaranteed in all cases. If a Secondary SRL header failure occurs during normal operation and is noticed before a reboot occurs, any data volumes that also failed will have a state of DETACHED. If the system is rebooted before the vxprint command shows the volumes to be in the DETACHED state, the status of any failed data volumes may be lost. Both these cases involve multiple errors and are unlikely, but it is important to understand that the state of Secondary data volumes can be suspect with this type of error.
To cleanup and recover the SRL header failure
- Dissociate the SRL volume.
# vxvol -g hrdg dis hr_srl
- Repair the SRL volume. Even if the problem can be fixed by repairing the underlying subdisks, the SRL volume must still be dissociated and re-associated to initialize the SRL header.
- Start the SRL volume. Then, re-associate it.
# vxvol -g hrdg start hr_srl # vxvol -g hrdg aslog hr_rvg hr_srl
- Start the RVG.
# vxrvg -g hrdg start hr_rvg
- If the integrity of the data volumes is not suspect, just resume the RLINK.
# vxrlink -g hrdg resume rlk_seattle_hr_rvg
OR
If the integrity of the data volumes is suspect, and a Secondary Storage Checkpoint backup is available, restore from the Secondary Storage Checkpoint.
# vxrlink -g hrdg det rlk_seattle_hr_rvg # vxrlink -g hrdg -f att rlk_seattle_hr_rvg # vxrlink -g hrdg -w pause rlk_seattle_hr_rvg
Restore the Secondary Storage Checkpoint backup data on to the data volumes.
# vxrlink -g hrdg -c secondary_checkpoint restore \ rlk_seattle_hr_rvg
OR
If the integrity of the data volumes is suspect and no Secondary Storage Checkpoint is available, synchronize the Secondary using a block-level backup and Primary Storage Checkpoint.
See Example - Synchronizing the Secondary using block-level backup.
As an alternative, you can also use automatic synchronization.
# vxrlink -g hrdg det rlk_seattle_hr_rvg
On the Secondary, restore the Primary Storage Checkpoint backup data to the data volumes.
# vxrlink -g hrdg -f att rlk_seattle_hr_rvg
On the Primary (seattle):
# vxrlink -g hrdg -c primary_checkpoint att \ rlk_london_hr_rvg