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-32
Configuring RDF
Receiver Process
Use SET RECEIVER and ADD RECEIVER commands to configure the following
receiver parameters:
•
ATINDEX
•
CPUS primary-CPU : backup-CPU
•
EXTENTS
•
PRIORITY
•
PROCESS
•
RDFVOLUME
•
SLOWMODE
The ATINDEX parameter specifies an integer value identifying a configured TMF audit
trail on the primary system. 0 specifies the MAT. 1 through 15 specify auxiliary audit
trails AUX01 through AUX15. The default is 0. For each configured extractor, there
must be a corresponding receiver with the same ATINDEX value. For information
about protecting auxiliary audit trails, see Section 12, Auxiliary Audit Trails.
The CPUS parameter specifies the processors in the backup system in which the
receiver is to run.
The EXTENTS parameter only applies to the master receiver. It specifies the size of
the primary and secondary extents for all image trail files on all image trails.
The PRIORITY parameter specifies the priority at which the receiver will run. You
should set the receiver’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 receiver process. You should
specify a meaningful mnemonic such as $RECV. 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 RDFVOLUME parameter applies only to the master receiver. It specifies which
volume on the backup system will contain the receiver’s master image trail. The file
naming convention for image trail files is $volume.control-subvolume.AAnnnnnn,
where n is a digit. For example, the first image file is named $volume.control-
subvolume.AA000001. You cannot specify the subvolume name because that name
is controlled by RDF.
The SLOWMODE parameter controls the frequency with which the receiver updates its
context records. With SLOWMODE on, the receiver updates its context records after
processing each extractor message buffer; this enables the updaters to have the
lowest possible RTD value at all times. The SLOWMODE parameter is intended for
use when customers have implemented their own pseudo-lockstepping environments.