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-95
Command Overview
STATUS RDF Command Output Display
The STATUS RDF command presents its display in the following format:
RDFCOM - T0346A07 - 18JAN05
(C)2005 Hewlett-Packard Development Company, L.P.
Status of \RDF04 -> \RDF05 RDF 2005/01/22 16:26:49.082
Control Subvol: $SYSTEM.RDF04
Current State : Normal
RDF Process Name RTD Time Pri Volume Seqnce Rel Byte No Cpus Error
------------------ ----- --------- --- ------- ------ ------------- ----- -----
Monitor $RMOR 185 $AUDIT 56 1: 2
Extractor (0) $RE01 0:00 185 $AUDIT 56 928000 1: 2
Extractor (1) $RE02 0:00 185 $DATA17 4 10435580 1: 2
Receiver (0) $RR01 0:00 185 $DATA01 44 1: 2
Receiver (1) $RR02 0:00 185 $DATA02 3 1: 2
Imagetrail (0) $DATA03 22
Imagetrail (1) $DATA04 3
Purger $RPRG 185 1: 2
RDFNET $MNET 165 0: 2
$DATA06 -> $DATA06 $RU01 0:06 185 $DATA03 20 749568 1: 2
$DATA07 -> $DATA07 $RU02 0:00 185 $DATA04 3 811008 2: 3
$DATA08 -> $DATA08 $RU03 0:06 185 $DATA04 3 749568 3: 0
In the STATUS RDF display, the first line gives the name of the primary system
(\RDF04 in this example), the name of the backup system (\RDF05 in this example),
and the timestamp that shows when the STATUS RDF command was issued. The
second line specifies the fully-qualified name of the control subvolume. The third line
specifies the current state of the subsystem; any of the following entries are possible:
•
Normal
•
Normal - Update Stopped
•
Start Update Pending
•
Stop Update Pending
•
Stop Update, Timestamp Pending
•
* STOP RDF In Progress *
•
* TMF STOP In Progress *
•
* TAKEOVER In Progress *
•
WRONG PROGRAM VERSION
•
NSA Stop Update Pending
•
Update NSA Stopped
The rest of the display provides current information about each RDF process
configured.