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-26
Reading Log Messages
The following is a sample display for a backup system. (The column numbers in the
top line do not appear in the display, and are included only for reference. )
(1) (2) (3) (4) (5) (6)
2004/06/09 16:11:02 \NYC $Z011 771 RDF Remote Receiver Started
2004/06/09 16:11:25 \NYC $Z012 773 RDF Remote Updater Started
$LOST -> $BLOST
2004/06/09 16:11:32 \NYC $Z013 773 RDF Remote Updater Started
$BIG -> $BBIG
2004/06/09 16:11:52 \NYC $Z014 773 RDF Remote Updater Started
$POPPY -> $BPOPPY
In the preceding displays, the individual columns present the following information:
The following sample RDFSCAN session shows another example of how you might
use RDFSCAN to examine messages in an RDF message file. The actual line length
for RDFSCAN is 132 columns (not 58 as shown in this example). On the terminal
screen, lines over 80 columns long wrap to the next line. User input appears in
boldface type. Notice also that record numbers, which do not appear in the previous
display, have been enabled for this one.
>RDFSCAN
RDFSCAN - T0346A06 - 14MAR04
(C)1988 Tandem (C)2004 Hewlett Packard Development Company, L.P.
File: $SYSTEM.RDF.RDFLOG, current record: 891, last record: 903
Enter HELP ALL for instructions
Enter the RDFSCAN function you want: AT 750
File: $SYSTEM.RDF.RDFLOG, current record: 750, last record: 903
Enter the next RDFSCAN function you want: MATCH
Enter pattern to match: *REMOTE*
File: $SYSTEM.RDF.RDFLOG, current record: 750, last record: 903,
Pattern: *REMOTE*
Enter the next RDFSCAN function you want: DISPLAY ON
File: $SYSTEM.RDF.RDFLOG, current record: 750, last record: 903,
Pattern: *REMOTE*
Enter the next RDFSCAN function you want: LIST 5
Record number: 751
2004/06/04 11:20:16 \LAB1 $Z049 771 RDF Remote Receiver Started
Record number: 752
2004/06/04 11:20:26 \LAB1 $Z050 773 RDF Remote Updater Started
$LOST -> $BLOST
Record number: 756
2004/06/04 11:20:30 \LAB1 $Z051 771 RDF Remote Receiver Started
(1) Date—is the date the message occurred, as reflected on the sending system.
(2) Time—is the time the message occurred, as reflected on the sending system.
(3) System—is the name of the system where the RDF process to which this message
pertains is running.
(4) RDF Process—is the name of the RDF process to which the message pertains.
(5) Message Number—is the number that identifies the RDF message and its meaning.
(6) Message Text—is the descriptive text that appears in the message.