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-4
Synchronizing the Primary and Backup Databases
The backup system should also have copies of the following files in case an RDF
takeover operation is necessary:
•
OBEY command files and TACL scripts containing NonStop SQL/MP or NonStop
SQL/MX DDL commands that define the database
•
SQLCI or MXCI report definitions
To make it easy to compare catalogs on the primary and backup systems, it is strongly
recommended that you register objects protected by RDF in separate catalogs from
objects not protected by RDF. Either all the tables in a catalog should be protected or
none of the tables should be protected.
Every NonStop SQL/MP or NonStop SQL/MX object maintained on the backup system
must be registered in a catalog, even if the object is not protected by RDF.
Synchronizing the Primary and Backup Databases
For databases to be synchronized in an RDF environment, the database on the backup
system must be logically identical to the database on the primary system. There are
two ways to synchronize your databases: offline and online. This topic covers offline
database synchronization. For a description of online database synchronization, see
Section 7, Online Database Synchronization.
To ensure consistency between the primary and backup databases, you should copy
the primary database to the backup system before RDF updating starts. The most
effective way to synchronize the databases follows:
1. Stop TMF auditing on the primary system by turning off the applications and
stopping TMF.
2. Create a copy of the primary database on the backup system.
The tools for synchronizing databases on HP NonStop systems are as follows:
•
The TACL OBEY command enables you to create the same database structures
on the primary system and the backup system by using commands in an EDIT file
to create reusable TACL macros and routines.
•
The SQLCI or MXCI CREATE CATALOG command can re-create NonStop
SQL/MP or NonStop SQL/MX catalogs on the backup system.
•
The SQLCI or MXCI DUP utility can copy NonStop SQL/MP or NonStop SQL/MX
objects and Enscribe files from one system to another.
•
The BACKUP and RESTORE utilities can copy NonStop SQL/MP or NonStop
SQL/MX objects and Enscribe files to and from tape.
•
The FUP DUP command can copy Enscribe files from one system to another.
•
The HP NonStop Autosync product can replicate all application programs and files
other than your RDF database.