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 a bunker to an RDS
This section describes adding a bunker to an existing RDS. If the RDS already includes a Secondary, adding a bunker does not interrupt replication from the Primary to the Secondary. You can also add the bunker to the RDS before adding the Secondary. Each bunker can support one or more Secondaries. An RDS can only contain one bunker.
A bunker can be configured in one of the following ways:
Using network (IP) connectivity to the bunker host
If the bunker host has IP connectivity to the Primary, the Primary replicates to the bunker SRL using standard VVR replication over the network using TCP or UDP protocol.
Using direct access to bunker storage
This configuration uses any direct connectivity such as IP over Fiber Channel, Direct Attached Storage (DAS) or Network Attached Storage (NAS) between the bunker storage and the Primary. In this case, the disk group containing the bunker SRL is imported on the Primary host, and the Primary writes to the bunker storage.
Note:
You cannot add data volumes to a bunker.
To add a bunker when the bunker host is accessible by IP
The steps for adding a bunker are the same whether the Primary uses a private disk group.
- Create a new disk group, hrdg2, containing only an SRL.
Note:
The bunker SRL must be the same size and the same name as the Primary SRL, or adding the bunker fails.
- To add the bunker, type the following command:
# vradmin -g hrdg -bdg hrdg2 addbunker hr_rvg seattle portland
where hr_rvg is the name of the RVG; seattle is the name of the Primary; and portland is the name of the bunker.
This command creates RLINKs between the bunker and the Primary, and also between the bunker and each Secondary in the RDS.
Note: Assume the following configuration:
# vradmin printrvg Replicated Data Set: hr_rvg Primary: HostName: seattle-v6 <localhost> RvgName: hr_rvg DgName: hrdg Secondary: HostName: london-v6 RvgName: hr_rvg DgName: hrdg
In this configuration, replication is already setup between london-v6 and seattle-v6. The bunker host can be added to the RDS using it's IPv6 address or a host name which resolves to an IPv6 address. For example, the bunker host can be added to the RDS using the following command:
# vradmin -g hrdg -bdg hrdg2 addbunker hr_rvg seattle-v6 \ portland-v6
where
hr_rvg
is the name of the RVG;seattle-v6
is the name of the Primary; andportland-v6
is the name of the bunker.
To add a bunker when the bunker storage is directly accessible
- Create a new disk group for the bunker, containing only an SRL. We recommend that this disk group has a different name than the main disk group for the RDS. For example, hrdg2.
Note:
The bunker SRL must be the same size and the same name as the Primary SRL, or adding the bunker fails.
The disk group must be available to the Primary and the bunker host. That is, the disk group can be imported on either the Primary or the bunker host.
- Deport the bunker disk group on the bunker portland and import it on the Primary seattle.
If the bunker disk group has the same name as the main disk group name, import it with a temporarily different name on the Primary, using the following command:
# vxdg import -t -n newdgname bunkerdgname
See Automating local cluster failover for a bunker.
If the VCS agents for VVR are not configured, you must deport the bunker disk group from the previous logowner and import it on the new logowner node each time the logowner fails over.
- Add the bunker:
# vradmin -g hrdg -bdg hrdg2 addbunker hr_rvg seattle \ portland protocol=STORAGE
where hr_rvg is the RVG name; seattle is the Primary name; portland is the bunker name.
- To display the configuration, use the following command:
# vradmin printrvg Replicated Data Set: hr_rvg Primary: HostName: seattle <localhost> RvgName: hr_rvg DgName: hrdg Secondary: HostName: london RvgName: hr_rvg DgName: hrdg Bunker (Secondary): HostName: portland RvgName: hr_rvg DgName: hrdg2