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
Online Database Synchronization
HP NonStop RDF System Management Manual—524388-003
7-24
When Is Online Database Synchronization
Complete?
When Is Online Database Synchronization
Complete?
The following RDF messages assist you in knowing when the various phases of online
database synchronization are complete:
Extractor Messages
Messages 766, 767, and 768 in combination report the completion of phase 1.
Message 782 reports the completion of phase 2. Message 782 indicates that the
extractor has finished its involvement in the online synchronization operation.
Updater Messages
Message 782 reports the completion of phase 2 and indicates that the updater has
finished its involvement in the online synchronization operation. Please note that even
in a partial database synchronization, all updaters will log event 782 because, in a
partial database synchronization, you follow the guildelines of a complete database
synchronization, except that you are only loading the specific volumes, table, and files
you need. Therefore all updaters log the 782 event.
Additionally, the STATUS RDF display has been enhanced to identify which database
volumes are still being synchronized. That information is reported in the error column
of the display. If a volume is still being synchronized, its entry in the error column is
sync. As soon as a volume is successfully synchronized, its entry in the error column
is blank. If an updater encounters an error during synchronization, the associated
entry in the error column is ****.
The following sample display shows that the updater process $MUP1 for the data
volume $DATA1 has successfully completed synchronization while the updater process
$MUP2 for the data volume $DATA2 is still doing the synchronization:
RDF Process Name RTD Time Pri Volume Seqnce Rel Byte Addr Cpus Error
------------------ ----- --------- --- ------- ------ ------------- ----- -----
Monitor $MMON 185 $TRAILS 5 2:3
Extractor (0) $MEXT 0:00 185 $TRAILS 5 7110636 2:3
Receiver (0) $MRCV 0:00 185 $TRAILS 37 806912 1:2
$DATA1 -> $DATA2 $MUP1 0:00 185 $TRAILS 37 806912 1:2
$DATA2 -> $DATA3 $MUP2 1:58 185 $TRAILS 32 712704 1:2 sync