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-9
Backing Up Application Programs and Files
For an Enscribe file, you can use the FUP DUP command or the BACKUP and
RESTORE utilities to copy the individual indexes and partitions. Then use FUP ALTER
to incorporate the other partitions and any alternate indexes into the primary partition.
If the volume names for partitions on the backup system are different from the volume
names on the primary system, you need to change the volume references for those
partitions.
Backing Up Application Programs and Files
To enable the backup system to take over in the event of a primary system failure, you
need to put usable copies of all program files, OBEY command files, and other files
your applications use on the backup system. You can do this by using the Autosync
product. After copying these files, you might need to change names to reflect the
backup system’s naming conventions, and you might need to recompile some
programs.
The following practices are recommended:
•
SQL compile all NonStop SQL/MP programs after moving them to the backup
system. A static recompilation reduces the applications’ startup costs after an RDF
takeover operation.
Alternatively, you can use the late binding feature. To do this, the SIMILARITY
CHECK attribute for all referenced tables and protection views must be enabled
and the program compiled with the CHECK INOPERABLE PLANS parameter.
•
Use DEFINEs for all NonStop SQL/MP objects where possible; this simplifies the
commands for your OBEY command files and the commands for your NonStop
SQL/MP DDL operations.
Installing RDF
The RDF/IMP, IMPX, or ZLT software, and all related documentation, is distributed on
three independent product release compact disks (CDs). After loading a CD, double
click on the Readme icon for complete instructions on how to install the RDF/IMP,
IMPX, or ZLT software. Before installing this product, use HP NonStop SPR Scout to
obtain access to all applicable software product revisions (SPRs).
RDF/IMP (T0346) Product Components
The release CD includes the following components for the RDF/IMP product:
CHEKDOC Documentation for RDFCHEK (an EDIT file)
RDFAFXO The RDF audit-fixup object code file
RDFCHEK An RDF file comparison utility
MD5CHEK An RDF file comparison utility
MD5SRVO The server component of MD5CHEK