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
Preparing the RDF Environment
HP NonStop RDF System Management Manual—524388-003
2-5
Preparing Software and Database Files for
RDF Operations
Preparing Software and Database Files for
RDF Operations
The software requirements for the RDF/IMP, IMPX, and ZLT products appear in
Table 2-2.
Mixed-Product Installation
RDF/IMP, IMPX, and ZLT are not compatible with RDF, RDF/MP, and RDF/MPX.
Therefore, if you already have any of those earlier RDF products installed, you cannot
install RDF/IMP, IMPX, or ZLT on just one of your systems; you must install it on both
the primary and backup systems.
The primary and backup systems need not have the same operating system release
version update (RVU) installed. The only requirement is that the installed RVU on
either system be at least D46 or G06.03.
Table 2-2. Software Requirements
Software Requirement
Files The RDF/IMP, IMPX, and ZLT products protect only files on the
primary system that are audited by the TMF subsystem.
Auditing The RDF/IMPX and ZLT products support the use of TMF auxiliary
audit trails on the primary system (volumes protected by RDF can
store audit data in either the MAT or an auxiliary audit trail).
The backup database files are audited, and therefore must also reside
on TMF data volumes.
Communications The RDF/IMP, IMPX, and ZLT products use Expand software to
connect the primary system to the backup system.
Operating System On the primary and backup systems, the installed release version
update (RVU) of the operating system must be D46 or later or G06.03
or later.
TMF Subsystem On both the primary and backup systems, the installed RVU of the
TMF subsystem must be compatible with the installed RVU of the
operating system.
NonStop SQL/MP
and NonStop
SQL/MX
On both the primary and backup systems, the installed RVU of the
NonStop SQL/MP or NonStop SQL/MX product must be compatible
with the installed RVU of the operating system.
Caution. The block size of a file or table on the backup system should be identical to the size
on the primary system. If the block sizes differ, you risk corrupting your backup database.