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-33
Configuring RDF
The default is SLOWMODE off. For a complete discussion of SLOWMODE, see the
description of the SET RECEIVER command in section 8.
To configure an RDF receiver process named $RECV to run as a process pair in CPUs
0 and 2 of the backup system at a priority of 185 with SLOWMODE off, and to have the
RDF image trail file (with a primary extent size of 3000 pages and a secondary extent
size of 3000 pages) reside on the volume $IMAGE, issue the following commands:
]SET RECEIVER ATINDEX 0
]SET RECEIVER PROCESS $RECV
]SET RECEIVER CPUS 0:2
]SET RECEIVER PRIORITY 185
]SET RECEIVER RDFVOLUME $IMAGE
]SET RECEIVER EXTENTS (3000,3000)
]ADD RECEIVER
You cannot start RDF until you have configured a master receiver process.
You can issue ADD RECEIVER commands only when RDF is stopped.
Purger Process
Use SET PURGER and ADD PURGER commands to configure the following purger
parameters:
•
CPUS primary-CPU : backup-CPU
•
PRIORITY
•
PROCESS
•
RETAINCOUNT
•
PURGETIME
The CPUS parameter specifies the processors in the backup system in which the
purger is to run.
The PRIORITY parameter specifies the priority at which the purger will run. You should
set the purger’s priority higher than that of any application’s process and higher than
that of any RDF updater process.
The PROCESS parameter supplies a name for the purger process. You should specify
a meaningful mnemonic such as $PURG. 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 RETAINCOUNT parameter specifies how many of the most recent image trail files
will be retained on disk for each image trail. The default value is 2. For details about
the RETAINCOUNT parameter and triple contingency, see Section 10, Triple
Contingency.