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-12
File Recovery on the Primary System
Volume Recovery Failure
RDF cannot recover from a TMF subsystem crash if TMF cannot successfully perform
volume recovery. After the TMF crash has been resolved, you must perform the
following tasks:
1. Resynchronize the primary and backup databases, following procedures explained
in sections 6 and 7.
2. Reinitialize RDF.
File Recovery on the Primary System
A file recovery operation occurs whenever a TMFCOM RECOVER FILES command is
issued at the primary system. A simple file recovery operation does not affect RDF nor
does it require database synchronization. A file recovery operation to a timestamp, a
first purge, or TOMATPOSITION, however, does require you to stop RDF, reinitialize,
and resynchronize the affected files.
The file recovery TOMATPOSITION is a special usage that achieves synchronization
itself. If the primary system has failed, you have executed an RDF takeover operation
on your backup system without RDF/ZLT, and you have subsequently brought you
primary system back online, you can resynchronize the database on your recovered
primary system with file recovery TOMATPOSITION. When the takeover has
completed on your backup system, RDF normally logs an RDF event 888. This event
provides you with a master audit trail sequence number and relative byte address that
you can use for file recovery TOMATPOSITION on your recovered primary system.
The result of this operation puts the database on your primary system into
synchronization with the database on your backup system at the time when the
takeover operation completed. If you started application processing on your backup
system after the completion of the takeover operation, you then need to configure a
new RDF subsystem to replicate all changes made to the database on your backup
system to the database on your primary system.
File Recovery on the Backup System
You are encouraged to take online dumps on your backup database on a regular basis
for the following reasons:
•
If you have lost your primary system and have taken over on your backup system,
the online dumps can be used for any type of file recovery operation provided the
redo end point is located after all audit data that was generated during the RDF
takeover. For example, a file recovery to a timestamp must be to a timestamp after
the time when the RDF takeover completed.
•
If RDF is running from your primary to your backup system and you lose one or
more disks on your backup system, you should stop the RDF updating, perform a
simple file recovery on the backup system to recover the files on the affected disks,
and then restart RDF updating.