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-2
Stopping the Software
2. Prepare your NonStop SQL/MP tables and Enscribe files for RDF protection as
follows:
a. Separate the tables to be protected by RDF from the tables not to be
protected. (This step is recommended but not required.)
b. Set audit compression (the AUDITCOMPRESS file attribute) on for all tables
and files to be protected by RDF. Note that audit compression on is the
creation default for NonStop SQL/MP tables and indexes. Although not
required by RDF, audit compression will enhance RDF performance.
Stopping the Software
After you stop all applications protected by TMF, stop TMF itself by issuing a STOP
TMF command through the TMFCOM interactive interface. (You only need to stop your
applications and TMF if you are going to use the TIMESTAMP parameter of the INIT
RDF command or if you are going to omit the timestamp parameter in all forms). For
information about issuing this and other TMFCOM commands, see the HP NonStop
TMF Reference Manual.
Preparing the Tables and Files
Now prepare your tables and files.
Separating NonStop SQL/MP or NonStop SQL/MX Tables
It is recommended that you avoid registering NonStop SQL/MP or NonStop SQL/MX
tables protected by RDF in the same catalogs as tables that are not protected by RDF.
Separating protected tables from unprotected ones simplifies the comparison of
primary system catalogs with backup system catalogs.
Compressing Audit Data for Tables and Files
Although not required by RDF, using the AUDITCOMPRESS file attribute will enhance
RDF performance. TMF compresses the audit data generated for NonStop SQL/MP
and NonStop SQL/MX tables and Enscribe files for which AUDITCOMPRESS is on.
For applications involving updates of only a few bytes to large existing rows or records,
this audit compression greatly reduces both the amount of audit information the
extractor must read and send to the receiver and the corresponding amount of RDF
traffic on the communications line.
For NonStop SQL/MP and NonStop SQL/MX tables and indexes, AUDITCOMPRESS
is the default. If the value has been changed to NO AUDITCOMPRESS for a table,
you can use an ALTER TABLE command, entered through the NonStop SQL/MP or
NonStop SQL/MX conversational interface, to reset the default value:
ALTER TABLE table-name AUDITCOMPRESS;