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
Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-6
Handling Disk Space Problems
Handling Disk Space Problems
When creating a new image file, the receiver preallocates 16 disk extents. If there is
not enough disk space, the receiver encounters a file system error 43 when it tries to
preallocate these extents. The receiver retries the allocation every 5 seconds and
reports the problem at approximately 60-second intervals. The receiver continues
trying to preallocate the disk space indefinitely.
While the error 43 condition exists, the receiver can only:
•
Provide information for STATUS RDF commands
•
Respond to STOP RDF commands
The error 43 condition persists until enough disk space is available for an image file.
During an error 43 condition, the receiver cannot accept any more images from the
extractor.
If you free enough disk space on the image volume to clear the error 43 condition,
however, processing can resume. You can do this by moving any files that might not
be needed (be sure, however, to restore them before the receiver and updaters need
them). Alternatively, you can accomplish this goal by backing up (with the BACKUP
utility) an unopened image file, then purging that file, and finally restoring it (with the
RESTORE utility) when the first file system error 11 (file not in directory) is reported for
the file by an RDF process on the backup system.
Because the receiver cannot accept any more images from the extractor, an error 43
condition on the backup system causes the extractor to stop progressing through the
audit trail files and RDF to fall behind TMF (TMF, however, continues to generate audit
data).
If an error 43 persists on the disk when you issue the STOP RDF command, the
subsystem shuts down successfully without requiring allocation of extents for the new
file. In this case, however, before you restart the subsystem with the START RDF
command, you must make this space available for at least two files per image trail;
otherwise, the START RDF command aborts.
If the error 43 condition is cleared before it becomes necessary to stop RDF, both the
primary and backup systems continue their normal operations.
Responding to Operational Failures
RDF can recover from any of the following events, as described in detail in the next
few pages:
•
Communications line failure on the primary or backup system
•
Processor failure on the primary or backup system
•
Crash of a TMF audited volume on the primary system