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-3
Configuring Updaters
Configuring Updaters
The SET VOLUME command includes the following optional syntax:
ATINDEX atindex
where atindex is an integer value from 0 through 15 specifying the audit trail to
which that data volume is mapped on the primary system. 0 specifies the MAT, and the
data volume on the primary system must be mapped to the MAT. 1 through 15
specifies auxiliary audit trail AUX01 through AUX15, respectively, and the data volume
on the primary system must be mapped to the designated auxiliary audit trail.
The default value is 0.
Error Conditions
•
It is an error if the specified image trail atindex does not map to a receiver with
the same atindex.
•
It is an error if the updater’s atindex does not equal the same audit trail index to
which the data volume on the primary system is mapped.
•
It is an error if the atindex of the updater and its image trail are not the same.
STOP TMF Ramifications
Under normal circumstances, auxiliary extractors always run ahead of the master
extractor. Abnormal situations, such as CPU failures, can cause auxiliary extractors to
fall behind the master extractor.
If an auxiliary extractor is running behind the master extractor when you issue a STOP
TMF command, the TMF shutdown operation cannot complete until the auxiliary
extractor has caught up with the master extractor. When that happens, RDF (or more
specifically, the master receiver process) may falsely appear to be hung. As soon as
the auxiliary extractor has caught up, however, the TMF shutdown operation proceeds.
Note. Data volumes on the backup system need not be mapped to the same audit trail as on
the primary system. If a data volume on the primary system is mapped to the MAT, for
example, the corresponding updater volume on the backup system can be mapped to an
auxiliary audit trail.
Note. The information in this and the next topic do not apply to RDF/ZLT configurations. For
information about RDF/ZLT functionality, see Section 16, Zero Lost Transactions (ZLT)
.