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
Preparing the RDF Environment
HP NonStop RDF System Management Manual—524388-003
2-6
Configuring TMF for RDF Operations
Configuring TMF for RDF Operations
TMF attempts to purge old audit trail files each time it rolls over to a new one. The
purge is performed only if the audit trail file is not pinned on behalf of RDF.
RDF automatically pins audit trail files. The only ways TMF can purge an old audit trail
file that is still required by RDF are as follows:
1. If you issue an UNPINAUDIT command while RDF is not running.
2. If you stop TMF and restart it without restarting RDF. TMF does not retain pinning
on behalf of RDF when TMF is stopped and then restarted. If you must stop and
restart TMF, be sure to restart RDF before you restart your applications. This
causes RDF to re-pin the audit trail files it needs, and thereby prevents TMF from
purging the files before RDF has finished processing them.
If you issue an UNPINAUDIT command while audit dumping is disabled and TMF
purges an audit trail that has not yet been processed by RDF, you will have to
reinitialize RDF and resynchronize the databases. If you have configured TMF for
audit dumping, however, you will not need to reinitialize RDF or resynchronize the
databases (the extractor will wait until the needed audit trail is restored and then
resumes).
TMF Configuration With Dump Process
When you configure TMF with audit dump on, that subsystem dumps an audit trail to
tape or disk before purging the audit trail. This approach is strongly recommended on
the primary system.
Note that audit trail files are pinned by the RDF extractor and TMF cannot purge
pinned files until the extractor has finished processing them. TMF will keep these files
pinned on behalf of the RDF extractor even if you stop RDF. Audit trail pinning is lost if
you stop TMF. See also the description of the UNPINAUDIT command in section 8.
You can control when TMF dumps an audit trail by configuring TMF for dump to tape.
For example, when configured with a tape dump process, TMF issues a prompt for the
operator to mount a tape when TMF is ready to dump and purge an old audit trail file.
Because TMF cannot execute the dump and purge of the audit trail file until a tape is
mounted, the operator can wait until the RDF extractor finishes that file before
mounting the tape.
For more information on configuring TMF, see the HP NonStop Transaction
Management Facility (TMF) Planning and Configuration Guide.