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
Introducing RDF
HP NonStop RDF System Management Manual—524388-003
1-23
Updater Processes
Audited Database Files
All database files on the backup system are audited files.
Each updater maintains a file status table to keep track of the files it has open. An
updater closes any database file that has not been updated recently. Updaters also
close database files when a STOP RDF or STOP UPDATE command is issued, or
when the updater restarts because of error conditions.
An updater process can have up to 500 files open simultaneously. When it has the
maximum number of files open and needs to open another file, it first determines if
there are any files that have not been accessed recently and closes just them; if all of
the open files have been accessed recently, then the updater closes all of them before
it continues processing. For the SMF ramifications of this file limit see the note under
Using SMF With RDF in Section 2.
UNDO Pass
Updaters perform an UNDO pass over the image trail during final processing of RDF
takeover and stop-update-to-time operations. This is because data already applied to
the backup database must be undone if the associated transaction(s) did not commit
prior to the start of the takeover operation or prior to the specified timestamp.
For takeover operations there are three phases of undo: local undo, file undo (if file-
incompletes from the primary system are still unresolved), and network undo (if you are
operating in an RDF network). For stop-update-to-time operations there is only local
undo (file-incompletes cause abend, and network undo is not supported).
Restart Information
RDF has a CONTEXT file in which each updater process maintains a context record. A
context record specifies the position (referred to as the restart position) in the image
trail where the updater was at the last context save point. All data for the associated
data volume in the backup database prior to the specified restart position is safe on
disk (has been applied to the backup database).
If an updater detects a restartable error, it restarts. Upon being restarted, an updater
reads its context record and restarts processing in the image trail at the specified
restart position.
Partitioned Files, Alternate Key Files, and Indexes
Each updater is responsible for applying audit data to partitions corresponding to the
volume on the primary system that updater is protecting. Updates are applied directly
to the specific partition, regardless of whether it is a primary or secondary partition.
RDF does not use the file system for partition mapping.
Furthermore, because updates to the backup database are applied by logical
REDO/UNDO operations, alternate key files and NonStop SQL/MP and NonStop
SQL/MX indexes are not affected by an update to a file or table. Alternate key files or