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-22
Updater Processes
•
Bundles the REDO and UNDO requests into batch TMF transactions, the duration
of which is specified by the UPDATERTXTIME configuration parameter.
•
For Enscribe files only, performs the following DDL operations:
CREATE
PURGE (if REPLICATEPURGE is enabled)
PURGEDATA
ALTER MAXEXTENTS (used only for increasing MAXEXTENTS)
•
For NonStop SQL/MP and NonStop SQL/MX files only, performs the following DDL
operation: PURGEDATA
An updater cannot always respond immediately to the STOP UPDATE and STOP RDF
commands. If an updater has audit information queued for the disk process, the
updater must wait until all of that information is processed before it can shut down.
You specify the primary and backup CPUs for each updater. If the original backup
process has to take over because the primary CPU failed, this backup process runs by
itself. When it determines that the primary CPU has come back up, it creates a new
backup process in that CPU.
When it has to take over, the original backup process becomes the primary process,
and remains so even after it creates a new backup process; that is, the updater does
not switch back to the original CPU configuration after the new backup process is
created. If you stop the updaters by way of a STOP RDF or STOP UPDATE
command, however, when you restart the updaters, your original configuration is once
again used.
The updaters will shut down if any of the following occurs:
•
You issue a STOP RDF, STOP TMF, or STOP UPDATE command on the primary
system.
•
You issue a STOP RDF command on the backup system when the
communications lines between the two systems are down.
•
The monitor detects the unexpected termination of any RDF process and sends
out abort RDF messages.
•
You perform a NonStop SQL/MP and NonStop SQL/MX DDL operation on the
primary system that includes the WITH SHARED ACCESS option (for information
about this, see Performing Shared Access DDL Operations.
•
A takeover operation completes on the RDF backup system.