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-37
Command Overview
INFO VOLUME Command
Suppose that you configured an updater process named $UP1 to back up all changes
made to audited files on the primary volume named $DATA01, and that the
corresponding volume on the backup system is $DATA1. Also suppose $UP1 was
configured to the secondary image trail $SECIT1 on the backup system (and that
$SECIT1 was previously added to the RDF configuration using an ADD IMAGETRAIL
command).
To display the current configuration parameters for that updater process, enter:
]INFO VOLUME $DATA01
RDF displays the following:
VOLUME $DATA01
VOLUME ATINDEX 0
VOLUME CPUS 0:1
VOLUME IMAGEVOLUME $SECIT1
VOLUME PRIORITY 170
VOLUME PROCESS $UP1
VOLUME UPDATEVOLUME $DATA1
Now, suppose you configured three updater processes (named $UP01, $UP02, and
$UP03) and that those processes are backing up the primary system volumes
$DATA01, $DATA02, and $DATA03, respectively, onto the volumes $DATA1, $DATA2,
and $DATA3 on the backup system. The updaters $UP01 and $UP02 are accessing
the secondary image trail $SECIT1; updater $UP03 is accessing the secondary image
trail $SECIT2.
To display the current configuration parameters for all of the updater processes, enter:
]INFO VOLUME *
RDF displays the following:
VOLUME $DATA01
VOLUME ATINDEX 0
VOLUME CPUS 0:1
VOLUME IMAGEVOLUME $SECIT1
VOLUME PRIORITY 160
VOLUME PROCESS $UP01
VOLUME UPDATEVOLUME $DATA1
VOLUME $DATA02
VOLUME ATINDEX 0
VOLUME CPUS 2:3
VOLUME IMAGEVOLUME $SECIT1
VOLUME PRIORITY 160
VOLUME PROCESS $UP02
VOLUME UPDATEVOLUME $DATA2
VOLUME $DATA03
VOLUME ATINDEX 0