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

Introducing RDF
HP NonStop RDF System Management Manual—524388-003
1-8
Features
•
Flexibility in protection
You can run RDF with updating on the backup system either enabled or disabled.
RDF is also very flexible with regard to system interrelationships and to disk usage 
requirements on backup systems. Besides the most basic configuration of a single 
primary system protected by a single backup system, you can have configurations 
such as the following (see Figure 1-2, RDF Topologies):
•
Multiple primary systems protected by one backup system.
•
Reciprocal protection between two systems, where each is the backup to the 
other (different databases on the two systems).
•
A single primary system whose database changes are replicated to databases 
on multiple backup systems. Such an environment makes possible 
simultaneous read-only access to all of the backup databases (this is desirable 
for query-intensive applications such as telephone directory assistance).
•
Triple contingency—a special instance of the database replication feature 
whereby a single primary system is protected by two identical backup systems. 
This feature allows your applications to resume, with full RDF protection, within 
minutes after the loss of your primary system, provided the two backup 
systems are not too far behind.
•
Loopback configuration—where the primary and backup systems are the same 
system. This has no value from a disaster protection standpoint, but can be 
useful for testing purposes. Data from a set of volumes can be replicated to a 
different set of volumes on the same node.
RDF does not require an identical one-to-one volume relationship between 
volumes on the primary system and those on the backup system. Backup volume 
names do not have to match primary volume names. The subsystem can direct 
audit information from more than one audited volume on the primary system to a 
single volume on the backup system, provided that no more than one partition of a 
file exists on any backup volume. (For information on partitioned files, see the 
Guardian User’s Guide.)
•
Application independence
RDF is application-independent; it can protect data for any application that uses 
NonStop SQL/MP and NonStop SQL/MX tables and indexes or Enscribe record 
manager files audited by TMF.
RDF supports the following audited file types: key-sequenced, entry-sequenced, 
and relative (for NonStop SQL/MP or Enscribe) and Enscribe queue files. 
Unstructured Enscribe files are not supported.










