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
Operating and Monitoring RDF
HP NonStop RDF System Management Manual—524388-003
4-4
Using RDFCOM Interactively
When it begins your interactive session, RDFCOM displays its product banner followed
by the RDFCOM prompt:
RDFCOM - T0346A07 - 05JUL05
(C)2005 Hewlett-Packard Development Company, L.P.
]
The right-bracket (]) prompt indicates that RDFCOM is ready to accept your first
command. When you enter this command, RDFCOM processes it and then displays
another right-bracket prompt for your next command. You continue interacting with
RDFCOM in this way, repeatedly receiving a prompt and entering a command, until
you explicitly end the session.
You can also group two or more commands on an entry line, separated by semicolons.
The next example shows the INFO RDF and HISTORY commands entered in this way:
]INFO RDF; HISTORY
If it detects an error during startup, RDFCOM displays an error message between the
product banner and the right-bracket prompt. If it discovers an error in an RDFCOM
command, RDFCOM displays an error message immediately following the command.
Each error message line begins with the following text, even if the message continues
to more than one line:
*** Error ***
For example, if you issue an ADD RDF command without previously initializing RDF,
RDFCOM issues the following message:
*** Error *** RDF has not been initialized
Ending a Session
When you want to end your session with RDFCOM, you can either issue the EXIT
command or type Ctrl-Y.
Interrupting Command Processing
You can interrupt RDFCOM processing by pressing the BREAK key at your terminal.
RDFCOM responds as follows:
•
If you press BREAK at the RDFCOM input prompt (]), RDFCOM returns control of
the terminal to RDFCOM’s parent process (typically, TACL) but continues
execution. You can resume communication with RDFCOM by entering the
operating system command PAUSE at the TACL prompt.
Note. On most terminals, you enter Ctrl-Y by simultaneously pressing the control key and the
Y key. On some terminals, however, this escape function might be selected by a different key
combination or a single key. Before using RDFCOM, identify how this function is selected on
your terminal.