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
HP NonStop RDF System Management Manual—524388-003
1-1
1 Introducing RDF
This manual describes the Remote Database Facility (RDF) subsystem as
implemented in version 1, update 7 of the HP NonStop RDF/IMP, IMPX, and ZLT
independent products. Customers who install RDF 1.7 can use existing RDF
configuration scripts provided the scripts are not making use of new functionality.
This section of the manual, intended for all readers, discusses the following topics:
•
An overview of RDF, including its use in response to unplanned and planned
outages
•
A summary of the main RDF processes
•
A summary of the RDF user interfaces
•
A discussion of normal RDF operation, explaining in substantial detail how the
various RDF processes interact with one another to perform the subsystem’s work
RDF monitors changes made to a production database on a local (primary) system and
maintains a copy of that database on one or more remote (backup) systems. Because
it applies changes to the backup database as soon as they are detected on the primary
system, RDF keeps the backup database continuously up to date with changes made
by business applications on the primary system. You are able, therefore, to switch your
business operations from the primary system to the backup system with minimal
interruption and loss of data in the event of planned or unplanned outages of the
primary system. With NonStop RDF/ZLT, the failover involves no loss of data.
RDF also allows you to use backup databases as read-only resources to balance the
overall workload and improve response times. Activities at a backup system can
include querying the database, processing heavy batch-reporting loads, and
consolidating data from multiple sites into one central site.
Backup systems may be located far from the primary system for protection against
regional disasters, communicating with the primary system over an Expand network.
System managers and operators control RDF through RDFCOM, a utility much like the
TMFCOM command interpreter used to access TMF.
RDF/IMP, IMPX, and ZLT generate fully-tokenized command, event, error, and warning
messages in the Event Management System (EMS) log. System managers and
operators can monitor those messages online using Viewpoint or whatever other tool
they normally use for monitoring $0. In addition, they can use the supplied EMS filter
RDFFLTO with an EMS printing distributor to isolate the RDF messages to an entry-
sequenced file which they then can peruse using the RDFSCAN utility.
RDF works with the Transaction Management Facility (TMF) subsystem.