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
Auxiliary Audit Trails
HP NonStop RDF System Management Manual—524388-003
12-2
Error conditions
values of 1 through 15 must protect volumes associated with configured auxiliary audit
trails AUX01 through AUX15, respectively.
A master extractor and receiver are required, because TMF control records are
required on the backup system in the event of an RDF takeover operation or a stop-
update-to-time operation. Auxiliary extractors and receivers are optional.
For each extractor, there must be a corresponding receiver with the same atindex
value.
Error conditions
•
It is an error not to have a master extractor (atindex value of 0).
•
It is an error not to have a master receiver (atindex value of 0).
•
It is an error if you do not have an auxiliary extractor and receiver with the same
atindex value. That is, if you have an auxiliary extractor with an atindex value
of 1, you must have an auxiliary receiver with an atindex value of 1.
•
It is an error if the specified atindex does not correspond to a valid index of a
configured auxiliary audit trail. That is, if you have configured two TMF auxiliary
audit trails with the respective audit trail numbers of 1 and 2, you cannot configure
an auxiliary extractor with an atindex value of 3.
•
It is an error to specify two extractors or two receivers with the same atindex
value.
Configuring Image Trails
Each image trail must be exclusively managed by a single receiver process, and all
audit records stored in an image trail must come from the same primary system audit
trail. Therefore, if your RDF environment is to protect primary system data volumes
that are configured to auxiliary audit trails, you must use the following command to
associate each image trail with the appropriate receiver:
SET IMAGETRAIL ATINDEX atindex
where atindex is an integer value from 0 through 15 specifying which receiver
manages the image trail. 0 specifies the receiver associated with the MAT; 1 through
15 specifies the receivers associated with auxiliary audit trails AUX01 through AUX15,
respectively.
The default value is 0.
After the SET IMAGETRAIL ATINDEX command, you must issue an ADD
IMAGETRAIL command.