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-31
Performing Shared Access DDL Operations
Database administrators with a clear understanding of the underlying TMF auditing
issues might elect to skip some of these steps as long as the DDL operations and
other audited operations are performed in the correct sequence on the primary and
backup systems. For example, it is not absolutely necessary to stop TMF (and thus
RDF), but it is safest to do so. As long as application processing is stopped and the
display from a STATUS RDF command shows that the RTD time for every updater
process is zero, the DDL operations can be safely applied.
Performing Shared Access DDL Operations
DDL operations that include the WITH SHARED ACCESS option, and which are
performed on the primary system, generate a special Stop-RDF-Updater audit record
in the MAT. As each updater on the backup system encounters that record in its image
trail file, that updater logs an RDF message 733 and then shuts down. When all of the
updaters have done so, RDF logs a message 908 indicating that it is now safe to
perform the same DDL operations on the backup system. Do that, and then issue a
START UPDATE command.
If RDF aborts while the updaters are in the process of shutting down, check the RDF
log to see if RDF generated a message 908. If it did, then do as follows:
1. Issue a START RDF, UPDATE OFF command on the primary system.
2. Perform the DDL operation(s) on the backup system.
3. Issue a START UPDATE command on the primary system.
Whether or not RDF aborted while the updaters were shutting down, if one or more
updaters did not generate a message 733, RDF logs a message 905 indicating that
you must not perform the DDL operations on the backup system. If that happens, issue
a START RDF, UPDATE ON command (only those updaters that did not generate a
message 733 are started). Check the RDF log again to see if RDF generated another
message 905. If it did, issue another START RDF, UPDATE ON command, and so
forth, until RDF logs a message 908. When RDF logs the message 908, do the Steps 2
and 3 listed above.
RDF does not support shared access NonStop SQL/MP DDL operations where the
target file is located on a different node than the primary system. For example, if you
have two RDF subsystems, one going from system \A to system \B and the other going
from system \X to system \Y, you cannot move a partition boundary for a table on
Note. If you do not stop TMF on the primary system and wait for RDF to stop itself in response
to the TMFCOM STOP TMF command, make sure the RDF time delay (RTD) time for every
updater process is zero and that the updater processes have closed all database tables before
you start any DDL operation. To check the RTD times for the processes, issue a STATUS RDF
command. For this method to work, all applications protected by RDF must be shut down and
only the data base administrator manipulates the primary database.