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
Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-12
Security Guidelines
The following summarizes the reasons for the various security requirements of each
RDF program:
•
RDFAFXO. The RDFAFXO process uses privileged TMF procedures to fix the
audit trail files and reset the CRASHOPEN flag in the audit trail file label and must
be licensed with FUP or by running the RDFINST macro. RDFAFXO can be owned
by any user ID.
•
RDFCOM. The RDFCOM program communicates with the TMP in privileged
mode and must be licensed with FUP or by running the RDFINST macro.
RDFCOM can be owned by any user ID; however, it must be run by a member of
the super-user group (user ID 255,nnn) to change the running state of RDF.
Alternatively, RDFCOM supports the use of the SAFEGUARD PROGID attribute to
enable any user to start, stop, and manage RDF. Once the PROGID attribute is
set, you must limit EXECUTE access to the RDFCOM object so that only those
persons authorized to manage RDF can run RDFCOM.
•
RDFEXTO. The RDF extractor program communicates with the TMP in privileged
mode and must be licensed with FUP or by running the RDFINST macro.
RDFEXTO can be owned by any user ID.
MD5SRVO NO NO
RDFCOM YES; 255,nnn +YES
RDFEXTO YES ++ YES
RDFMONO YES ++ YES
RDFNETO YES ++ NO
RDFPRGO YES ++ YES
RDFRCVO YES ++ YES
RDFSCAN NO++++ NO
RDFSNOOP YES +++ YES
RDFUPDO YES ++ YES
READLIST NO NO
RDIMAGE YES ++ YES
+ RDFCOM operational commands require super-user group access; however, INFO and STATUS
commands can be issued by all users.
++ The RDF processes run under the userid of the user who set the PROGID attribute, or the RDF OWNER.
+++ RDFSNOOP requires super-user group access to read image files.
++++ Depends upon security of entry-sequenced file being accessed.
Table 3-1. RDF Process and Program Security Attributes
Program Name
Run Under a
Specific Logon ?
LICENSE Required
for Object File?