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
Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-19
Command Overview
unknown at the time of the original takeover. Because RDFCOM added more audit
information to the image trail, there is a chance that the outcome of some of these
transactions is now known. Therefore, RDFCOM repositions the updater’s restart
location back to the first record that it could not previously apply. (If there were no
exception records, then RDFCOM leaves the updater’s restart location unchanged.)
Finally, RDFCOM turns off the receiver’s takeover completed flag and issues a
message telling you that the COPYAUDIT operation has completed successfully and
you must initiate another takeover on \C. Issue a TAKEOVER command on \C. If the
takeover completes successfully (the receiver logs an RDF message 724 followed by a
735 message containing the same detail as in the 735 message associated with the
takeover on \B), the two databases are logically identical.
At that point you can initialize, configure, and start RDF on both systems, and then
resume application processing on the new primary system with full RDF protection.
COPYAUDIT Restartability
The COPYAUDIT command is restartable.
If an error condition aborts execution of a COPYAUDIT command, you merely correct
the condition and then reissue the command. Upon restart, RDFCOM quickly checks
the local system image files it had previously created to be sure they are still correct,
deletes the file it was working on at the time of the error condition, and then resumes
copying. Because it keeps track of where it was in the COPYAUDIT operation,
RDFCOM does not have to recopy the previously copied image files.
RDFCOM abends if it encounters network problems while searching the remote image
trails for missing audit information. If that happens, RDFCOM logs a message to the
EMS event log, but not to the home terminal.
If RDFCOM encounters network problems during any other phase of COPYAUDIT
execution, it does not abend. Instead, it logs a message to the home terminal and
aborts the COPYAUDIT command.
Example
Assume you have established two RDF configurations to provide triple contingency
protection (\A to \B and \A to \C) and that the RDF control subvolume of the \A to \B
configuration is A1 and the RDF control subvolume of the \A to \C configuration is A2.
Assume further that, after failure of the primary system (\A), you do a takeover on both
\B and \C and determine that \B was further ahead in its RDF processing.
To copy the missing audit information from \B to \C, issue the following command on
\C:
]COPYAUDIT , REMOTESYS \B, REMOTECONTROLSUBVOL A1