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-2
Command Syntax for Starting an RDFCOM Session
Command Syntax for Starting an RDFCOM Session
To enter an RDFCOM session, use the following general command syntax. The
specific parameters you enter depend, of course, on the options you desire.
RDFCOM
is an implicit RUN command, instructing the TACL command interpreter to run the
RDFCOM utility program.
IN command-file
specifies a command file from which RDFCOM commands are to be read.
RDFCOM reads 132-byte records from the specified file until it encounters either
the end-of-file mark or an EXIT command.
If you do not specify the IN option, TACL automatically supplies the name of its
current default input file—usually the terminal from which you issued the RDFCOM
command.
OUT output-file
specifies a file to which all output (other than prompts for entering RDFCOM
commands) is to be written. This file might receive listings requested by INFO,
SHOW, and STATUS commands, for example. It might also receive RDFCOM
commands generated by the OBEYFORM option of the INFO command.
If you do not specify the OUT option, TACL supplies the name of its current default
output destination—usually the terminal from which you issued the RDFCOM
command.
If you specify a disk file that does not exist, an EDIT file (file code 101) having the
name you specified is automatically created, and RDFCOM output is directed to it.
If you specify a disk file that exists, this must be an EDIT file (file code 101);
RDFCOM output is appended to that file. If you omit the volume or subvolume
portions of the file name specifier, the default is your current volume or subvolume,
respectively.
control-subvolume
is the name of the RDF control subvolume on $SYSTEM on the primary and
backup systems, as well as the subvolume on the image trail volumes on the
backup system in which the image trail files reside.
The control subvolume name is the same as the name of the primary system
without the backslash (and with a one-character suffix appended to it, if you
included the suffix in the INITIALIZE RDF command).
RDFCOM [/[IN command-file ] [,OUT output-file ]/ ]
[control-subvolume] ; [command [; command ]... ]