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-31
Configuring RDF
•
RTDWARNING
•
VOLUME
The ATINDEX parameter specifies an integer value from 0 through 15 specifying the
TMF audit trail on the primary system with which the extractor is associated. 0
specifies the MAT. 1 through 15 specify auxiliary audit trails AUX01 through AUX15.
The default is 0. If you omit this parameter, RDFCOM assumes the extractor is
associated with the MAT. For information about protecting auxiliary audit trails, see
Section 12, Auxiliary Audit Trails.
The CPUS parameter specifies the processors in the primary system in which the
extractor will run.
The PRIORITY parameter specifies the priority at which the extractor will run. You
should set the extractor’s priority slightly lower than that of the RDF monitor process.
The PROCESS parameter supplies a name for the extractor process. You should
specify a meaningful mnemonic such as $EXT. 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 RTDWARNING parameter specifies the RTD warning threshold (in seconds,
0 or greater) for the extractor. This threshold is used by the STATUS RTDWARNING
command to determine if the extractor is to be included in its display. The display
includes the monitor process and only those RDF processes (extractor or updaters)
whose RTD exceeds their configured RTD warning threshold.
The VOLUME parameter specifies a valid volume name in the current TMF
configuration on your primary system. When configuring RDF for ZLT, you must add
the complete set of audit-trail volumes to which protected data volumes are configured.
You use a SET EXTRACTOR VOLUME statement for each individual volume. You do
not need to specify whether the volume is an active volume, restore volume, or
overflow volume; you merely specify the volume name. For information about the ZLT
capability, see Section 16, Zero Lost Transactions (ZLT).
To configure an RDF extractor process named $EXT to run as a process pair in CPUs
5 and 3 of the primary system, at a priority of 185, with an RTD warning threshold of
360 seconds, issue the following commands:
]SET EXTRACTOR ATINDEX 0
]SET EXTRACTOR PROCESS $EXT
]SET EXTRACTOR CPUS 5:3
]SET EXTRACTOR PRIORITY 185
]SET EXTRACTOR RTDWARNING 360
]ADD EXTRACTOR
You can issue ADD EXTRACTOR commands only when RDF is stopped.