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-6
Considerations When Synchronizing Entire
Databases
it, but now does not), and the audit information will not be applied to the backup
database. In this particular case the database is not corrupted, but data corruption
could occur for other NonStop SQL/MP DDL SHARED ACCESS operations.
If you did recently perform a NonStop SQL/MP operation with SHARED ACCESS on
the primary system and you want to initialize the RDF subsystem to a synchdbtime,
you must specify a synchdbtime such that the starting position in the MAT is after the
Stop-RDF-Updater record.
As a precaution, if RDFCOM encounters a Stop-RDF-Updater record during its
backward search of the MAT, it issues a warning message to that effect asking if you
want to proceed with initialization. If the extractor encounters such a record while
operating in database synchronization mode, it abends.
TMF Shutdown Records
TMF shutdown records in the MAT do not cause a problem, except that RDF shuts
down and you must then restart it.
CREATE/LOAD Issues
The LOAD command only works on tables and files that are nonaudited. If you create
the empty duplicate tables and files as audited entities, you must then use FUP ALTER
commands to turn off their audit attributes before you can load them.
For information about the SQLCI LOAD or FUP LOAD commands, refer to the HP
NonStop SQL/MP Reference Manual or the File Utility Program (FUP) Reference
Manual, respectively. The following information is general in nature and is not
intended as a substitute for the information contained in those two manuals.
General Considerations for Enscribe Files
•
Key-sequenced Files. To improve the performance of the load operations,
specify the SORTED option.
•
Relative Files. To ensure complete consistency with the source files, specify the
NO COMPACT option.
•
Entry-sequenced and Unstructured Files. Currently there is no reliable
mechanism to synchronize these file types online. Entry-sequenced and
unstructured files should be synchronized offline.
•
Partitioned Files (key-sequenced or relative). For partitioned files, you can
initiate the load operation with a single command by executing the LOAD
command against the primary partition.
•
Alternate Key Files (key-sequenced or relative). You should execute LOAD
commands against all alternate key files.