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
HP NonStop RDF System Management Manual—524388-003
9-1
9 Entering RDFSCAN Commands
All RDF messages are directed to an EMS event log (collector). To examine that log
without looking at all events for the entire system, you first use the standard EMS filter
RDFFLTO to create an intermediate entry-sequenced file copy of the RDF log, and
then enter commands through the RDFSCAN online utility.
This section, which is addressed to system managers and operators, describes the
RDFSCAN commands and their attributes. In this section, you will find:
•
An overview of the EMS event log
•
A brief description of the RDFFLTO filter
•
A brief discussion of the elements that appear in all RDFSCAN command
descriptions
•
The command descriptions themselves, presented in alphabetic order by
command name
File names entered as parameters in RDFSCAN commands are subject to the same
syntax rules as those used in RDFCOM commands. For these rules, see File Names
and Process Identifiers in section 8.
About the EMS Log
The EMS log receives all messages from RDF, including those dealing with RDF
startup and shutdown, RDF events, errors, and informative data. In an RDF
configuration, an EMS log exists, and is assigned the same name, on both the primary
and backup nodes.
The EMS log is specified as the global RDF parameter LOGFILE in the RDF
configuration file. At configuration time, you can either
•
Supply the name of the desired collector in a SET RDF LOGFILE command, and
add it to the configuration file with an ADD RDF command
•
Let RDF use $0 by default
At any later time, you can change the collector specified in the configuration file by
entering an ALTER RDF LOGFILE command.
You can use RDFSCAN to examine the RDF messages in the EMS log by way of an
intermediate entry-sequenced file produced by the RDFFLTO filter. You must specify
the name of the intermediate file in the RDFSCAN command that begins your session.
For more information about EMS event log content, format, and scanning methods,
see the following discussions:
•
Scanning the EMS Event Log in section 1
•
Running RDFSCAN and Performing Routine Operational Tasks in section 4