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
VVR event notification
VVR provides the vrnotify utility to notify administrators of VVR specific events, such as SRL full, resynchronization complete, etc. You can receive notification for a VVR event on the Primary or Secondary node, or both the nodes in an RDS.
The vrnotify command enables you to write a script that receives VVR event notification and notifies administrators of these events through email, pager, etc. See the examples in this section to see how event notifications can also be used to keep history of various events.
If you do not specify the local_rvgname in the vrnotify command, event notification is started for all the RDSs on the local host.
If any of the RDSs have RVGs in a shared disk group, vrnotify provides notification about events on the logowner for those RVGs.
Use the -g option to receive event notifications for RVGs in a specific disk group.
The vrnotify command displays the VVR events until you explicitly terminate or kill the command.
To receive event notifications on the Primary or Secondary, enter the following command:
# vrnotify -g diskgroup local_rvgname....
The argument local_rvgname... is a space-separated list of the names of the RVGs on the local host in the specified disk group.
The vrnotify command displays each event on a new line in the following format:
host_name:event_type:RDS_name:event message
For an RVG in a shared disk group, host_name is the logowner, and the displayed event information reflects activity on the logowner host.
The vrnotify command displays the following types of events:
Table: Event notifications
Event Type | Event Message |
---|---|
rvg_actsectosec | RVG role changed from acting secondary to secondary |
logowner_changed | Logowner role change for RVG |
rlink_paused | Rlink has paused |
rlink_resumed | Rlink has resumed |
rvg_passthru | RVG has become passthru |
sec_log_err | Replication stopped due to an error on Secondary SRL volume |
dcm_activated | DCM map has activated |
srl_flush_start | SRL to DCM flush has started |
srl_flush_end | SRL to DCM flush has completed |
dcm_replay_end | DCM replay has completed |
rlink_stale | Rlink has become stale |
rlink_detached | Rlink has detached |
dcm_replay_abort: | DCM replay was aborted |
resync_started | Resync started on Primary RVG |
resync_stopped | Resync stopped on Primary RVG |
resync_paused | Resync paused on Primary RVG |
lat_throttle_on | Latency throttling started |
lat_throttle_off | Latency throttling stopped |
lat_throttle_override | Latency throttling overridden |
lat_throttle_fail | Latency throttling caused I/O failures |
srlprot_throttle_on | SRL overflow protection throttling started |
srlprot_throttle_off | SRL overflow protection throttling stopped |
srlprot_override | SRL overflow protection overridden |
srlprot_fail | SRL overflow protection caused I/O failures |
srl_overflow | Replication stopped due to SRL overflow |
srlprot_dcm_on | Started using DCM for SRL protection |
srlprot_dcm_off | Stopped using DCM |
rlk_connect | RLINK connected to remote |
rlk_disconnect | RLINK disconnected from remote |
srl_log_warn | SRL percentage full has changed by 10% |
repmode_sync | Replicating in synchronous mode |
repmode_async | Replicating in asynchronous mode |
repibc_freeze | Replication on Secondary frozen due to IBC |
repibc_unfreeze | Replication on Secondary unfrozen after IBC |
rvg_pritosec | RVG role changed from Primary to Secondary |
rvg_sectopri | RVG role changed from Secondary to Primary |
rvg_pritoactsec | RVG role changed from Primary to acting Secondary |
rvg_actsectopri | RVG role changed from acting Secondary to Primary |
rlk_paused | Secondary RLINK paused because of a configuration error |
ibcmsg_discarded | IBC was discarded due to timeout on the Secondary. |
Example:
The following example script shows how to use the vrnotify utility to receive event notifications for the hr_rvg RDS in the hrdg disk group and send email to the alias vvradmin if the event srl_warning occurs.
#!/bin/sh IFS=: vrnotify -g hrdg hr_rvg | while read host event rvg msg do case $event in srl_log_warn) (echo "This message is sent by VVR notify mechanism" echo "$msg for RVG $rvg on host $host" ) | mailx -s "VVR SRL Log Warning" vvradmin;; esac done