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-44
Command Overview
Usage Guidelines
If your RDF subsystem is running and you do not include the TIMESTAMP, INITTIME,
or SYNCHDBTIME options in the INITIALIZE RDF command, then you must stop,
delete, and reconfigure TMF before entering the INITIALIZE RDF command.
Before issuing the INITIALIZE RDF command within an existing RDF configuration,
you must first purge all files from the control subvolume on both the primary and
backup systems.
TMF must be started on the primary system, but transaction processing need not be
enabled, when you enter the INITIALIZE RDF command either with or without the
TIMESTAMP, INITTIME, or SYNCHDBTIME options.
The INITIALIZE RDF command creates the configuration and context files for
establishment of a new RDF configuration. After issuing the INITIALIZE RDF
command, you must build the new configuration by entering the appropriate SET and
ADD commands or by executing a command file containing those commands. Only
then can you issue the START RDF command to start RDF.
The INITIALIZE RDF command also establishes the name of the RDF control
subvolume, which you subsequently specify when initiating RDFCOM sessions or
in OPEN commands.
If you include the SUFFIX parameter, the specified character becomes a permanent
part of the RDF control subvolume name and you can only alter that character by
issuing another INITIALIZE RDF command.
When using the INITIALIZE RDF command, follow these guidelines:
•
If you include the TIMESTAMP option in the INITIALIZE RDF command, then the
specified timestamp must correspond exactly to a TMF shutdown point.
Whenever TMF stops in response to a STOP TMF command, it writes a timestamp
in the Event Management Service (EMS) log. That is the timestamp you use with
the TIMESTAMP option of the INITIALIZE RDF command.
•
If you do not include the TIMESTAMP, INITTIME, or SYNCHDBTIME options in the
INITIALIZE RDF command, you must delete and reconfigure TMF before you
initialize RDF. In this case, the extractor will transmit audit from the beginning of
the first master audit trail (MAT) file (AA000001).
•
If you include the TIMESTAMP option in the INITIALIZE RDF command, RDFCOM
searches backwards in the MAT for a TMF shutdown record with the specified
timestamp. If you include the INITTIME or SYNCHDBTIME option, RDFCOM
searches backwards in the MAT for the first commit or abort record whose
timestamp is less than the specified timestamp. When it finds the shutdown record
or commit/abort record, RDFCOM sets the context of the extractor to the record
following that record.
•
When RDF is initialized, the contexts of the receiver and all updaters are initialized
to the beginning of the first image file (AA000001). When RDF is started for the
first time after it has been initialized, any existing image files are purged.