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-15
Command Overview
RDF State Requirement
While RDF is running, the only configuration parameters you can alter are the log file,
the purge time, the RDF updater delay, and the priority of each RDF process. You can
also change the RDF updater open while RDF is running, but updating must be
stopped. To change the setting of any other parameter, you must first stop RDF.
Usage Guidelines
Before entering the ALTER command, you can display the current configuration
parameters with the INFO RDF command. After entering ALTER, you can confirm
your changes by again entering INFO RDF.
If you use an ALTER RECEIVER command to change the EXTENTS parameter, the
change will occur on the next RDF image file rollover, unless RDF has never been
started since its last reinitialization.
Although you can use the SET RECEIVER RDFVOLUME command to specify the disk
volume used for the master image trail, you cannot respecify this volume by entering
an ALTER RECEIVER RDFVOLUME command. To change this volume, you must
reinitialize RDF and use another SET RECEIVER RDFVOLUME command followed by
an ADD RECEIVER command.
If you need to change an updater’s image trail volume, it is recommended that you
stop TMF; wait for RDF to stop; delete the volume; re-add the volume back into the
configuration, associating it to a different image trail volume; and then restart the TMF
and RDF subsystems. This is the only way to ensure that the backup database will
remain synchronized with the primary database.
Examples
To change the priority at which an extractor process is currently running, issue an
ALTER EXTRACTOR PRIORITY command. For example, the following command
changes the execution priority of the master extractor process to 170:
]ALTER EXTRACTOR PRIORITY 170
The following command changes the execution priority of the auxiliary extractor
process associated with the auxiliary audit trail AUX02 to 170:
]ALTER EXTRACTOR ATINDEX 2 PRIORITY 170
Note. Altering the RDF UPDATERDELAY value is not recommended unless you have a very
specific reason for doing so; any value less than the default (10 seconds) may affect updater
performance.