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
Additional Reference Information
HP NonStop RDF System Management Manual—524388-003
B-10
RDF File Codes
•
ZRCVnn files
One file is created for each auxiliary receiver in your RDF configuration, and the nn
is the two-digit ATINDEX of the receiver. These files store information about SQL
Shared Access DDL operations involving files protected by RDF.
The ZRCVnn files reside on the backup node and are named
$SYSTEM.control-subvolume. ZRCVnn.
•
UNDO List files
These files contain the lists of transactions that need to be undone either during a
stop-update-to-time operation or takeover operation. They can be read with the
READLIST utility, which creates a similarly named file in the MIT that can be read
with RDFSCAN. The ZNETUNDO file only exists in RDF network environments.
The undo list files resides on the backup node and are named:
$master-image-trail-volume.control-subvolume. ZTXUNDO
$master-image-trail-volume.control-subvolume.ZFILUNDO
$master-image-trail-volume.control-subvolume.ZNETUNDO
•
Network List files
These files contain the lists of transactions that need to be evaluated for possible
undo during a takeover operation if you have configured an RDF Network.
The Network list files resides on the backup node and are named:
$master-image-trail-volume.control-subvolume. ZRDFLCMT
$master-image-trail-volume.control-subvolume. ZRDFLCM2
$master-image-trail-volume.control-subvolume. ZRDFLCM3
$master-image-trail-volume.control-subvolume. ZRDFNMTX
$master-image-trail-volume.control-subvolume. ZRDFNMT2
$master-image-trail-volume.control-subvolume. ZRDFNMT3.
Each backup system of the RDF Network has its own ZRDFLCMT file. The other
files are only located in the MIT of the network master.
RDF File Codes
RDF image trail file code = 720
RDF configuration file code = 721
RDF primary context file code = 722
RDF remote context, ZFILEINC, and ZRCVnn file code = 723