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
Adding the IP and NIC resources for IPv6 addresses in the RVG agent group when VCS global clustering and VVR agents are configured in the presence of a bunker
Currently, replication between the Primary and Secondary sites uses an IPv4 network. Before you can migrate the network to IPv6, you must add the IP and NIC resources to VCS control. You can do this in one of the following ways:
Add new IP and NIC resources for IPv6 in the RVG group.
Modify the current IP and NIC resources in the RVG group.
The first method, adding new IP and NIC resources for IPv6, ensures high availability. For example, suppose you add resources for IP and NIC resources for IPv6 addresses in the main.cf
on the node in the Primary site from where replication is active. If the Primary site crashes before VVR migration to IPv6 from IPv4, the application service group fails over to the other node in the Primary site and replication continues using the IPv4 address. The existing IP and NIC resources are still in the main.cf
file.
The second method, modifying the current IP and NIC resources, hampers replication. If a node in the Primary site crashes as you modify the existing IP resource, the original IPv4 virtual IP is lost. The application service group fails over to the other node, but the IPv4 IP address does not come online on the other node because you changed the IP resource from an IPv4 address to an IPv6 address. Instead, the IPv6 IP comes online. However, VVR is not configured use the IPv6 IP for replication, and replication pauses or stops. The IPv4 IP is not available on the other node.
To add the IP and NIC resources on the Primary and Secondary sites
- Make the VCS configuration writeable. Enter the following:
# haconf -makerw
- Add the NIC resource for the IPv6 address and configure the related attributes:
# hares -add nicres_v6 NIC VVRGRP VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors # hares -modify nicres_v6 Enabled 1 # hares -modify nicres_v6 Device en2 # hares -modify nicres_v6 NetworkHosts \ fd4b:454e:205a:111:211:43ff:feaa:af71 # hares -modify nicres_v6 Protocol IPv6 # hares -probe nicres_v6 -sys swax25 # hares -probe nicres_v6 -sys swax26
- Add the IP resource for the IPv6 address and configure the related attributes:
# hares -add ipres_v6 IP VVRGRP VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors # hares -modify ipres_v6 Enabled 1 # hares -modify ipres_v6 Device en2 # hares -modify ipres_v6 Address \ fd4b:454e:205a:111:211:43ff:feaa:af70 # hares -modify ipres_v6 PrefixLen 64 # hares -probe ipres_v6 -sys swax25 # hares -probe ipres_v6 -sys swax26 # hares -online ipres_v6 -sys swax25 # hares -link ipres_v6 nicres_v6 # hares -link res_rvg ipres_v6
- Save your configuration changes. Enter the following:
# haconf -dump -makero
- After you add the IP and NIC resources to the Primary and Secondary sites, display the RVG agent group in the
main.cf
file to verify your changes.group VVRGRP ( SystemList = { swax25 = 0, swax26 = 1 } AutoStartList = { swax25, swax26 } ) DiskGroup res_dg ( DiskGroup = hrdg ) IP ipres_v6 ( Device = en1 Address = "fd4b:454e:205a:111:211:43ff:feaa:af70" PrefixLen = 64 ) IP ipres ( Device = en0 Address = "10.209.87.170" NetMask = "255.255.252.0" ) NIC nicres_v6 ( Device = en1 NetworkHosts = { "fd4b:454e:205a:111:211:43ff:feaa:af71" } Protocol = IPv6 ) NIC nicres ( Device = en0 NetworkHosts = { "10.209.121.1" } ) RVG res_rvg ( RVG = hr_rvg DiskGroup = hrdg ) ipres_v6 requires nicres_v6 ipres requires nicres res_rvg requires ipres_v6 res_rvg requires res_dg res_rvg requires ipres
- Verify the new network configuration. Enter the following:
# ifconfig -a
- Display a summary of all the HA groups. Enter the following:
# hastatus -sum
- Add the IP and NIC resources in the VCS configuration on the Secondary site. Use a different IP address on the Secondary site for IPv6 resources. For example, the IPv4 virtual IP address could be 10.209.87.171 and the IPv6 virtual IP address could be fd4b:454e:205a:111:211:43ff:feaa:af71.
To add the IP and NIC resources for IPv6 in the VCS configuration on the bunker site
- Optionally, display information on your current configuration.
To display a summary of the HA groups on the bunker site, enter the following:
# hastatus -sum
To display the current network configuration on the bunker site, enter the following:
# ifconfig -a
Display the Service Group of the virtual IP on the bunker site. The following is a sample configuration:
group VVRGRP ( SystemList = { swax29 = 0 } AutoStartList = { swax29 } ) IP ipres ( Device = en0 Address = "10.209.87.202" NetMask = "255.255.252.0" ) NIC nicres ( Device = en0 NetworkHosts = { "10.209.84.1" } ) ipres requires nicres // resource dependency tree // // group VVRGRP // { // IP ipres // { // NIC nicres // } // }
- Make the VCS configuration writeable. Enter the following:
# haconf -makerw
- Add the NIC resource for the IPv6 address and configure the related attributes. Enter the following:
# hares -add nicres_v6 NIC VVRGRP VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors # hares -modify nicres_v6 Enabled 1 # hares -modify nicres_v6 Device en1 # hares -modify nicres_v6 NetworkHosts \ fd4b:454e:205a:111:211:43ff:feaa:af28 # hares -modify nicres_v6 Protocol IPv6 # hares -probe nicres_v6 -sys swax29 # hares -link ipres_v6 nicres_v6 # hares -online ipres_v6 -sys swax29
- Add the IP resource for the IPv6 address and configure the related attributes. Enter the following:
# hares -add ipres_v6 IP VVRGRP VCS NOTICE V-16-1-10242 Resource added. Enabled attribute must be set before agent monitors # hares -modify ipres_v6 Enabled 1 # hares -modify ipres_v6 Device en1 # hares -modify ipres_v6 Address \ fd4b:454e:205a:111:211:43ff:feaa:af72 # hares -probe ipres_v6 -sys swax29
- Save your configuration changes. Enter the following:
# haconf -dump -makero
- Verify your changes on the bunker site. To display the updated network configuration, enter the following:
# ifconfig -a