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
Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-24
Configuring RDF
UPDATERRTDWARNING Parameter
The UPDATERRTDWARNING parameter specifies the RTD warning threshold (in
seconds, 0 or greater) for all configured updaters. The default is 60 seconds.
This threshold is used by the STATUS RTDWARNING command to determine which
updaters, if any, are to be included in its display. The display includes the monitor
process and only those RDF processes (extractor or updaters) whose RTD exceeds
their configured RTD warning threshold.
UPDATEROPEN Parameter
The UPDATEROPEN parameter specifies the access mode (PROTECTED or
SHARED) that updaters use when opening database files. The default is
PROTECTED.
Protected access is strongly recommended at all times, except when you specifically
wish to take online dumps or do reloads of the backup database with the updaters
running. After the dumping or reloads have finished, you should change the access
mode from SHARED back to PROTECTED.
SOFTWARELOC Parameter
The SOFTWARELOC parameter specifies where the RDF software is installed on both
the primary and backup systems. The default is $SYSTEM.RDF.
NETWORK Parameter
The NETWORK parameter specifies whether or not you are configuring an RDF
network.
When set to OFF (the default value), RDF takeover operations execute and database
consistency is not guaranteed for user transactions that were replicated over more
than one RDF backup node.
When set to ON, the RDF subsystem guarantees database consistency across
multiple RDF backup systems configured within an RDF network.
When set to ON, you must either have the NETWORKMASTER attribute for the same
system also set to ON or have another system configured as the network master.
NETWORKMASTER Parameter
The NETWORKMASTER parameter specifies whether the particular system is the
master of the RDF network.
When set to OFF (the default value), the particular system is not the network master.
When set to ON, the particular system is the network master of the RDF network.
When this attribute is set to ON, the NETWORK attribute must also be set to ON.