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-17
Initializating RDF Without Stopping TMF
Initializating RDF Without Stopping TMF
The INITIALIZE RDF command includes a parameter, INITTIME inittime , that you
can use to initialize the RDF product without stopping TMF or your applications.
There are two cases where you would use this capability:
1. If you want to install a new version of the RDF product and you cannot afford to
stop TMF even momentarily to get a TMF shutdown timestamp.
2. If you are running RDF and encounter a problem for which you would like to
reinitialize it without having to resynchronize your databases.
Determining a Valid inittime Value
When using the INITTIME parameter without the NOW clause, it is important that you
specify a valid inittime value.
To do so, first issue a STATUS RDF command and take note of the highest updater
RTD time. Then round that RTD time up to the next higher minute (0:43 becomes 1:00,
1:27 becomes 2:00, 3:04 becomes 4:00, and so forth). Finally, subtract that rounded-
up time from the current system time shown in the status display.
inittime := (current-system-time — rounded-highest-updater-RTD-time)
RDFCOM then subtracts an additional three minutes from the specified timestamp.
This is to ensure that the extractor’s starting position is at a point in the MAT where
RDF had previously sent audit information to the backup system and the updaters had
applied it to the backup database. This practice guarantees that no audit information
will be lost during initialization.
When you include the INITTIME parameter in the INITIALIZE RDF command,
RDFCOM initiates a backward scan of the MAT searching for the first commit or abort
record whose timestamp is less than the specified inittime . When RDF is
subsequently restarted, some of the audit information will be reapplied to the backup
database. This does not cause any inconsistencies between the primary and backup
databases, but rather ensures that they stay completely synchronized with one
another.
The NOW clause of the INITTIME parameter causes RDF to be initialized at the
current date and time. The NOW clause simplifies initialization and configuration of a
reverse RDF environment created in response to a reverse trigger. See the Example
under the description of the SET TRIGGER command.
Special Considerations
When using this form of the INITIALIZE RDF command, there are three special cases
which you might encounter.