RDF System Management Manual
Table Of Contents
- RDF System Management Manual
- What’s New in This Manual
- About This Manual
- 1 Introducing RDF
- RDF Subsystem Overview
- RDF Processes
- RDF Operations
- Reciprocal and Chain Replication
- Available Types of Replication to Multiple Backup Systems
- Triple Contingency
- Loopback Configuration (Single System)
- Online Product Initialization
- Online Database Synchronization
- Online Dumps
- Subvolume- and File-Level Replication
- Shared Access DDL Operations
- EMS Support
- SMF Support
- RTD Warning Thresholds
- Process-Lockstep Operation
- Support for Network Transactions
- RDF and NonStop SQL/MX
- Zero Lost Transactions (ZLT)
- Monitoring RDF Entities With ASAP
- 2 Preparing the RDF Environment
- 3 Installing and Configuring RDF
- 4 Operating and Monitoring RDF
- 5 Managing RDF
- Recovering From File System Errors
- Handling Disk Space Problems
- Responding to Operational Failures
- Stopping RDF
- Restarting RDF
- Carrying Out a Planned Switchover
- Takeover Operations
- Reading the Backup Database
- Access to Backup Databases in a Consistent State
- RDF and NonStop SQL/MP DDL Operations
- RDF and NonStop SQL/MX Operations
- Backing Up Image Trail Files
- Making Online Dumps With Updaters Running
- Doing FUP RELOAD Operations With Updaters Running
- Exception File Optimization
- Switching Disks on Updater UPDATEVOLUMES
- 6 Maintaining the Databases
- 7 Online Database Synchronization
- 8 Entering RDFCOM Commands
- 9 Entering RDFSCAN Commands
- 10 Triple Contingency
- 11 Subvolume- and File-Level Replication
- 12 Auxiliary Audit Trails
- 13 Network Transactions
- Configuration Changes
- RDF Network Control Files
- Normal RDF Processing Within a Network Environment
- RDF Takeovers Within a Network Environment
- Takeover Phase 1 – Local Undo
- Takeover Phase 2 – File Undo
- Takeover Phase 3 – Network Undo
- Takeover Phase 3 Performance
- Communication Failures During Phase 3 Takeover Processing
- Takeover Delays and Purger Restarts
- Takeover Restartability
- Takeover and File Recovery
- The Effects of Undoing Network Transactions
- Takeover and the RETAINCOUNT Value
- Network Configurations and Shared Access NonStop SQL/MP DDL Operations
- Network Validation and Considerations
- RDF Re-Initialization in a Network Environment
- RDF Networks and ABORT or STOP RDF Operations
- RDF Networks and Stop-Update-to-Time Operations
- Sample Configurations
- RDFCOM STATUS Display
- 14 Process-Lockstep Operation
- Starting a Lockstep Operation
- The DoLockstep Procedure
- The Lockstep Transaction
- RDF Lockstep File
- Multiple Concurrent Lockstep Operations
- The Lockstep Gateway Process
- Disabling Lockstep
- Reenabling Lockstep
- Lockstep Performance Ramifications
- Lockstep and Auxiliary Audit Trails
- Lockstep and Network Transactions
- Lockstep Operation Event Messages
- 15 NonStop SQL/MX and RDF
- Including and Excluding SQL/MX Objects
- Obtaining ANSI Object Names From Updater Event Messages
- Creating NonStop SQL/MX Primary and Backup Databases from Scratch
- Creating a NonStop SQL/MX Backup Database From an Existing Primary Database
- Online Database Synchronization With NonStop SQL/MX Objects
- Offline Synchronization for a Single Partition
- Online Synchronization for a Single Partition
- Correcting Incorrect NonStop SQL/MX Name Mapping
- Consideration for Creating Backup Tables
- Restoring to a Specific Location
- Comparing NonStop SQL/MX Tables
- 16 Zero Lost Transactions (ZLT)
- A RDF Command Summary
- B Additional Reference Information
- C Messages
- D Operational Limits
- E Using ASAP
- Index
HP NonStop RDF System Management Manual—524388-003
12-1
12 Auxiliary Audit Trails
In addition to the master audit trail (MAT), RDF/IMPX and ZLT support protection of up
to 15 auxiliary audit trails.
If you want to protect data volumes associated with an auxiliary audit trail, you must
configure an auxiliary extractor and an auxiliary receiver for that trail. Thus, for each
auxiliary audit trail, there will be one auxiliary extractor-receiver pair.
Auxiliary Extractor
An auxiliary extractor can only be configured to a single auxiliary audit trail. Such an
extractor will read only the designated auxiliary audit trail; it will never read any part of
the MAT or any other auxiliary audit trail. When reading the audit trail, it looks for any
audit records associated with the pool of volumes being protected by RDF (normal
filtering logic). All such records are sent to the backup system in accordance with
standard RDF architectural behavior. Each auxiliary extractor is associated with a
corresponding auxiliary receiver through the user-specified configuration. The auxiliary
extractor communicates only with that particular auxiliary receiver, and never sends
data to the master receiver or any other auxiliary receiver.
Auxiliary Receiver
An auxiliary receiver is associated with a specific auxiliary extractor. Because the
auxiliary extractor sends audit records associated only with its particular auxiliary audit
trail, the corresponding auxiliary receiver writes audit records to the image trails of
updaters associated only with volumes configured to the particular auxiliary audit trail.
For example, assume that $DATA1 on the primary system is configured as a data
volume in auxiliary audit trail AUX01, and an auxiliary extractor is configured for
AUX01. The auxiliary extractor sends all audit information for $DATA1 to a
corresponding auxiliary receiver on the backup system. The receiver writes the data to
an image trail that is, in turn, read and processed by an updater responsible for
replicating database changes for $DATA1.
Configuring Extractors and Receivers
The SET EXTRACTOR and SET RECEIVER commands include the following optional
syntax:
ATINDEX atindex
where atindex is an integer value corresponding to the audit trail number of the MAT
(0) or an auxiliary audit trail (1 through 15) on the primary system. The default is 0.
Because 0 is reserved for the MAT, the extractor and receiver with an atindex value
of 0 are the master extractor and receiver. The extractors and receivers with atindex