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
Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-29
Access to Backup Databases in a Consistent State
If the specified timestamp is not at least five minutes greater than the current time,
RDFCOM aborts the command and displays the following message:
The specified timestamp must be at least five minutes greater
than the current time.
The STOP UPDATE command itself is logged to the EMS event log under the general
RDF message 835. As each updater shuts down because it has reached a
commit/abort record generated after the specified timestamp, it logs the following
shutdown message to the EMS event log:
785 Redo pass ending on reaching timestamp timestamp.
Because some audit data will not have been applied, the updaters must reexamine that
audit data when they restart. Consequently, when restarting the updaters after a STOP
UPDATE to a timestamp, the initial RTD times of the updaters will be greater than the
duration of time they were actually stopped.
The example that follows illustrates the effect of a STOP UPDATE, TIMESTAMP
command. In the example, tn indicates a transid, and the timestamp below reflects the
time of most recent commit or abort record in the audit trail.
RDFCOM; STOP UPDATE, TIMESTAMP 20JUN2004 12:00
commit update update update update update update commit update update commit commit
t0 t1 t2 t3 t1 t2 t3 t1 t2 t3 t2 t3
11:50 11:50 11:50 11:50 11:50 11:50 11:50 11:59 11:59 11:59 12:01 12:02
The updater applies the updates associated with t1 because that transaction
committed before the specified timestamp. It does not, however, apply the updates
associated with t2 and t3 because those transactions did not commit until after the
specified timestamp. The updater does not actually shut down until it encounters the
commit record for t2 (12:01). As soon as it encounters a commit or abort record whose
timestamp is greater than the specified timestamp, the updater will have processed all
audit data for transactions that committed or aborted up to the specified timestamp.
Thus, the database is in a completely consistent state with regard to transaction
boundaries.
The updater keeps track of the first record it could not apply because its transaction
committed or aborted after the specified timestamp. In the above example, the
updater’s restart position in the image trail will be the first update record for t2. Thus,
when restarted, the updater will backtrack to that record. This practice ensures that no
audit data is lost during the STOP UPDATE to a timestamp operation.
If you erroneously set the timestamp too far into the future (for example, 26DEC3000),
the only way to correct this mistake is to enter a STOP RDF command, restart RDF,
and reenter the STOP UPDATE command with the correct timestamp.
See also the description of the STOP UPDATE command in section 8.