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-2
Where Issued
Where Issued
Some RDFCOM commands can be issued only from the primary system, others only 
from the backup system, and still others from either system. For each command, the 
allowed systems are listed under “Where Issued.” For your convenience, they are also 
summarized in Table 8-1.
Security Restrictions
Although several RDFCOM commands are available to all users, other commands 
impact the overall RDF environment and are, by default, restricted to members of the 
super-user group. For each command, the default security requirements appear under 
the heading “Security Restrictions.” In general, the default security restrictions for 
RDFCOM commands are as follows:
•
The EXIT, FC, HELP, HISTORY, INFO, OBEY, OPEN, OUT, SHOW, and STATUS 
commands can be used by all users.
•
The START RDF and TAKEOVER commands can only be used by the member of 
the super-user group who initialized RDF.
•
The other RDFCOM commands can be used only by members of the super-user 
group.
The default security restrictions for all RDFCOM commands are summarized in 
Table 8-2, Default User Security for RDFCOM Commands.
RDF State Requirement
Some RDFCOM commands can only be entered after RDF has been started; others 
must be entered before the subsystem has been started or after it has been stopped. 
In each command description, these constraints are listed under the heading “RDF 
State Requirement.”
Usage Guidelines
Details about the proper use of a command appear under “Usage Guidelines.” These 
details include information about when to apply the command, possible constraints and 
unexpected effects of the command, hints on enhancing performance and avoiding 
errors, and other considerations.
When a command is extremely basic or straightforward, the command description 
omits the “Usage Guidelines.”










