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-9
RDF System Files
•
RDFLOCK file
The RDFLOCK file is an unstructured, semaphore lock file that exists only to
protect RDFCOM from performing multiple critical operations at the same time. A
semaphore lock is the software mechanism that prevents other processes from
executing certain functions until the process that initiated the semaphore lock has
finished its processing. For example, if you issue any one of the following
RDFCOM commands, RDFCOM tries to lock the RDFLOCK file:
COPYAUDIT
INITIALIZE RDF
START RDF
STOP RDF
START UPDATE
STOP UPDATE
TAKEOVER
If the RDFLOCK file is not already locked, RDFCOM locks this file and executes
the critical type of operation. If another RDFCOM user tries to execute a critical
type of operation and RDFCOM finds the RDFLOCK file already locked, RDFCOM
issues the following message:
Another RDFCOM is performing a CRITICAL operation.
•
ZFILEINC file
This is a key-sequenced file that stores information about transactions and files
involved in transactions that aborted on the primary system, but TMF Backout
could not undo the audit because the volumes were down. A record for each
transaction and file is stored in the ZFILEINC file. If a volume is re-enabled on the
primary system and TMF Backout is able to undo the audit data it could not
previously undo, then the corresponding records are removed from the ZFILEINC
file.
The ZFILEINC file resides on the backup node and is named
$SYSTEM.control-subvolume.ZFILEINC.
•
RDFTKOVR file
This file records whether an RDF Takeover operation has completed successfully.
This file is empty under normal circumstances (eof = 0). If, however, you have
executed an RDF Takeover operation and it completes successfully, then they key
word "DONE" is written in the file by RDF. This file can be used for executing fast
business takeover operations. See in Tips for Executing Fast Business Takeover
Operations in section 1 for more details.
The RDFTKOVR file resides on the backup node and is named
$SYSTEM.control-subvolume.RDFTKOVR.