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
Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-11
Command Overview
begins reading from the current image file at the same place that the receiver process
begins writing.
The master image trail identified by the RDFVOLUME parameter in the SET
RECEIVER command is reserved for use by the MAT receiver process. All updaters
must be configured to secondary image trails. Each image trail is stored on a separate
volume on the backup system. To add a secondary image trail, you specify the disk
volume intended for its use through the ADD IMAGETRAIL command. When you
configure your individual updater processes with the SET VOLUME command, you
assign each of these processes to a different image trail, reducing the number of
updaters contending for a specific trail.
Each secondary image trail contains only that audit data required by the associated
updaters. Image files in secondary image trails have the same extent sizes as image
files on the volume specified by RDFVOLUME. Because the extent sizes for
secondary image trails are obtained from the receiver’s configuration record, you do
not specify them through any RDFCOM commands.
With RDF/IMP, IMPX, or ZLT, if your RDF configuration is not particularly small (say, 30
volumes or more) and your performance requirements are not high, you can assign
one image trail per updater process, and you can place that image trail on the
updater’s UPDATEVOLUME. If you have the need for high performance, however,
even on a small system, it might be best to have a dedicated volume for your image
trails.
You cannot add secondary image trails until you have configured the receiver, because
the extent sizes for these trails depend on those specified for the receiver’s master
image files.
Examples
To configure the extractor process named $EXT to run in CPUs 0 and 1 at the default
priority of 165 with the default RTD warning threshold of 60 seconds, enter the
following commands:
]SET EXTRACTOR PROCESS $EXT
]SET EXTRACTOR CPUS 0:1
]ADD EXTRACTOR
Caution. After RDF is configured and running, do not add an updater process unless a STOP
TMF command has shut down RDF; otherwise, you cannot be sure that the data on the newly
added backup system volume is synchronized with the data on the corresponding primary
system volume.