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-35
Configuring RDF
trail with the ADD IMAGETRAIL command. Also, the ATINDEX of this updater must 
match the ATINDEX of the associated image trail.
The PRIORITY parameter specifies the priority at which the updater will run. You 
should set the updater’s priority higher than that of any application’s process but less 
than the priority of the RDF receiver process.
The PROCESS parameter supplies a name for the updater process. You should 
specify a meaningful mnemonic such as $UP01. The process name can be any unique 
valid process name up to 5 characters, including the $ symbol. However, you cannot 
specify HP reserved process names that are of the form $X*, $Y*, or $Z*, in which * 
is any alphanumeric string.
The UPDATEVOLUME parameter specifies the name of the disk volume on the 
backup system that corresponds to a particular volume on the primary system. This 
parameter enables you to use different volume names on the backup system than are 
being used on the primary system, if you so desire.
The following guidelines are strongly recommended:
•
There should be an identical one-to-one volume relationship between volumes on 
the primary system and those on the backup system.
•
Each backup volume should have the same name as the associated primary 
volume.
If the backup volume names are not identical to the corresponding primary volume 
names, then you will have to update every partitioned file and every file that has 
alternate keys on the backup system so that each points to the correct volume name.
You can use INCLUDE and EXCLUDE lists to specify which files are to be, or are not 
to be, protected by RDF. For a description of INCLUDE and EXCLUDE lists, see 
Section 11, Subvolume- and File-Level Replication.
The following RDFCOM commands configure an updater named $UP01 to run as a 
process pair in CPUs 2 and 4 at a priority of 180. The updater will be associated with 
an secondary image trail on the volume $IMAGA1. The name of the backup volume 
and the primary volume being protected is $DATA01.
]SET VOLUME ATINDEX 0
]SET VOLUME PROCESS $UP01
]SET VOLUME CPUS 2:4
]SET VOLUME IMAGEVOLUME $IMAGA1
]SET VOLUME PRIORITY 180
]SET VOLUME UPDATEVOLUME $DATA01
]ADD VOLUME $DATA01
Note that the mapping between the configured updater process and a particular 
primary volume is accomplished by the ADD VOLUME command.










