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
Setting up the VVR configuration
This section shows how to set up a sample VVR configuration. The VVR configuration in this example applies to the RVG Agent.
It uses the names that are used in the sample configuration file of the RVG agent. The procedure to configure VVR is the same for all the VVR agents. Use the sample configuration files located in /etc/VRTSvcs/conf/sample_vvr directory to configure the other agents.
The example uses the names listed in the following table.
Name of Cluster: Seattle
Disk group | hrdg |
Primary RVG | hr_rvg |
Primary RLINK to london1 | rlk_london_hr_rvg |
Primary data volume #1 | hr_dv01 |
Primary data volume #2 | hr_dv02 |
Primary volume set (with data volumes hr_dv03, hr_dv04) | hr_vset01 |
Primary SRL for hr_rvg | hr_srl |
Cluster IP address | 10.216.144.160 |
Name of Cluster: London
Disk group | hrdg |
Secondary RVG | hr_rvg |
Secondary RLINK to seattle | rlk_seattle_hr_rvg |
Secondary data volume #1 | hr_dv01 |
Secondary data volume #2 | hr_dv02 |
Secondary volume set (with data volumes hr_dv03, hr_dv04) | hr_vset01 |
Secondary SRL for hr_rvg | hr_srl |
Cluster IP address | 10.216.144.162 |
In this example, each of the hosts (seattle1 and london1) has a disk group named hrdg with enough free space to create the VVR objects.
Set up the VVR configuration on seattle1 and london1 to include the objects used in the sample configuration files, main.cf.seattle and main.cf.london, located in the /etc/VRTSvcs/conf/sample_vvr/RVG directory.
To set up the VVR configuration
- On london1:
Create the Secondary data volumes.
# vxassist -g hrdg make hr_dv01 100M \ layout=mirror logtype=dcm mirror=2 # vxassist -g hrdg make hr_dv02 100M \ layout=mirror logtype=dcm mirror=2
Create the data volumes for the volume set on the Secondary and create the volume set.
# vxassist -g hrdg make hr_dv03 100M \ layout=mirror logtype=dcm mirror=2 # vxassist -g hrdg make hr_dv04 100M \ layout=mirror logtype=dcm mirror=2 # vxmake -g hrdg vset hr_vset01 \ appvols=hr_dv03,hr_dv04
Create the Secondary SRL.
# vxassist -g hrdg make hr_srl 200M mirror=2
- On seattle1:
Create the Primary data volumes.
# vxassist -g hrdg make hr_dv01 100M \ layout=mirror logtype=dcm mirror=2 # vxassist -g hrdg make hr_dv02 100M \ layout=mirror logtype=dcm mirror=2
Create the data volumes for the volume set on the Primary and create the volume set.
# vxassist -g hrdg make hr_dv03 100M \ layout=mirror logtype=dcm mirror=2 # vxassist -g hrdg make hr_dv04 100M \ layout=mirror logtype=dcm mirror=2 # vxmake -g hrdg vset hr_vset01 \ appvols=hr_dv03,hr_dv04
Create the Primary SRL.
# vxassist -g hrdg make hr_srl 200M mirror=2
Create the Primary RVG.
# vradmin -g hrdg createpri hr_rvg \ hr_dv01,hr_dv02,hr_vset01 hr_srl
Uncomment the plus symbol from /etc/vx/vras/.rdg file from the nodes in the secondary site, or configure security accordingly.
Determine the virtual IP address to be used for replication. Get the IP up using the OS-specific command. This IP address that is to be used for replication must be configured as the IP resource for this RVG service group.
Create the Secondary RVG.
# vradmin -g hrdg addsec hr_rvg 10.216.144.160 \ 10.216.144.162 prlink=rlk_london_hr_rvg \ srlink=rlk_seattle_hr_rvg
Note:
The RLINKs must point to the virtual IP address for failovers to succeed. The virtual IP address 10.216.144.160 must be able to ping virtual IP address 10.216.144.162 and vice versa. IPv6 addresses are supported.
Start replication.
# vradmin -g hrdg -f startrep hr_rvg
- Create the following directories on seattle1 and seattle2. These directories will be used as mount points for volumes hr_dv01 and hr_dv02 and the volume set hr_vset01 on the seattle site.
# mkdir /hr_mount01 # mkdir /hr_mount02 # mkdir /hr_mount03
- On seattle1, create file systems on the volumes hr_dv01 and hr_dv02 and on the volume set hr_vset01.
More Information