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-13
Using the OWNER Attribute to Allow Super Group
Users to Start, Stop, and Manage RDF
•
RDFMONO. The RDF monitor program communicates with the TMP in privileged
mode and must be licensed with FUP or by running the RDFINST macro.
RDFMONO can be owned by any user ID.
•
RDFNETO. The RDFNETO program opens and writes to the network
synchronization file on each of the primary systems participating in the RDF
network. RDFNETO can be owned by any user ID.
•
RDFPRGO. The RDF purger program purges image files in privileged mode and
must be licensed with FUP or by running the RDFINST macro. RDFPRGO can be
owned by any user ID.
•
RDFRCVO. The RDF receiver program opens the image files in privileged mode
and must be licensed with FUP or by running the RDFINST macro. RDFRCVO can
be owned by any user ID.
•
RDFSCAN. The RDFSCAN program contains no privileged calls or privileged
code and need not be licensed. RDFSCAN can be owned and run by any user ID.
•
RDFSNOOP. The RDFSNOOP program opens the image files in privileged mode
and must be licensed with FUP or by running the RDFINST macro. RDFSNOOP
can be owned by any user ID. RDFSNOOP must be run by a member of the super-
user group (user ID 255,nnn) to read the image files.
•
RDFUPDO. RDF updater programs open image files in privileged mode and must
be licensed with FUP or by running the RDFINST macro. RDFUPDO also must be
able to open database files for protected write access. When querying the backup
database files, users should always open the files for shared read access.
•
RDIMAGE. The RDIMAGE program opens the image files in privileged mode and
must be licensed with FUP or by running the RDFINST macro. RDIMAGE can be
owned by any user ID. RDIMAGE must be run by a member of the super-user
group (user ID 255,nnn) to read the image files.
Using the OWNER Attribute to Allow Super Group Users to Start,
Stop, and Manage RDF
By setting the OWNER global configuration parameter in a SET RDF configuration
command, you are specifying the primary owner of your RDF environment (such as
SUPER.RDF, for example). Doing so enables other super group userids to start, stop,
and manage RDF.
Once the OWNER attribute is set, you must use SAFEGUARD to limit EXECUTE
access to the RDFCOM object so that only those super group users authorized to
manage RDF can run RDFCOM. Failure to do so is a serious security risk because,
thereafter, all RDF objects run as the userid of the RDF OWNER.