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
Messages
HP NonStop RDF System Management Manual—524388-003
C-138
RDFCOM Messages
Effect. This parameter no longer has any effect. The KMSF subsystem controls the
placement of the RDF processes’ swap files.
Recovery. This is an informational message; no recovery is required.
Cause. You entered an INITIALIZE RDF command that attempted to initialize RDF at
a specific TMF shutdown timestamp.
Effect. RDF is ready to start reading the Master Audit Trail (MAT).
Recovery. This is an informational message; no recovery is required.
Cause. You are attempting to initialize RDF in conjunction with a complete database
synchronization.
Effect. If an audit record can be found whose timestamp is less than the specified
timestamp, RDF is initialized to that record.
Recovery. This is an informational message; no recovery is required.
Cause. You are attempting to initialize RDF to a timestamp that is earlier than the
current time, and database synchronization is not involved.
Effect. If an audit record can be found whose timestamp is less than the specified
timestamp, RDF is initialized to that record. Note that if you were running RDF prior to
this initialization command, you should take into consideration the highest updater
RTD. In addition, RDFCOM subtracts another three minutes from the specified
timestamp to ensure that the starting position in the audit trail is a safe one.
Recovery. This is an informational message; no recovery is required.
* * * WARNING * * * RDF will start at the first record in
the TMF master audit trail beyond the specified shutdown
timestamp. RDF will ignore all audit generated before this
timestamp.
* * * WARNING * * * RDF will start at the first record in
the TMF master audit trail whose timestamp is less than the
specified timestamp. The timestamp you specified must follow
the documented guidelines.
* * * WARNING * * * RDF will start at the first record in
the TMF master audit trail whose timestamp is less than the
specified timestamp. The timestamp you specified must follow
the documented guidelines. Please note that RDFCOM will
subtract an additional three minutes from the specified
timestamp to ensure a safe restart position.