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-33
Making Online Dumps With Updaters Running
For a successful backup, follow these steps:
1. Execute a process that opens the image trail file with shared read access. This can
be a simple process that you supply to perform only this operation. When the
purger determines that all updaters are finished with this image trail file (named,
say, AA000007), and have moved on to the next image trail file (named, say,
AA000008), then it may try to purge AA000007. The purge operation will fail,
however, because your process still has AA000007 open. The purger will terminate
the purge attempt and try it again later. As long as your process keeps AA000007
open, the purger cannot purge it.
2. When the purger tries to purge AA000007 and fails, it writes a message denoting
this error to the EMS event log. This message implies that all updaters have
moved from AA000007 to AA000008 (or beyond), and will never need AA000007
again; it is your only way to know for certain that AA000007 will never be needed
again. When this message is written, you can start the backup process to dump
AA000007 to tape.
3. When the backup process opens AA000007 and the backup is in progress, you
can stop the file-opening process run in Step 1. The purger will continue its
attempts to purge AA000007, but these attempts also will fail as long as the
backup process has AA000007 open. Eventually, when the backup is complete
and AA000007 is successfully copied to tape, no processes will have this file open.
After this point, the purger will be able to purge AA000007 successfully.
Repeat the preceding steps for each image trail file you wish to back up.
Making Online Dumps With Updaters Running
RDF/IMP, IMPX, and ZLT allow you to take dumps of the backup database while the
updaters are running. To do this, you use the UPDATEROPEN parameter of a SET
RDF or ALTER RDF command to specify the access mode (protected or shared) that
all of the updaters use when opening database files.
The default is protected access.
Protected access is strongly recommended, except when you specifically wish to take
dumps of the backup database with the updaters running.
To take online dumps of the backup database while the updaters are running, do as
follows:
1. Stop the updaters (issue a STOP UPDATE command on the primary system).
2. Alter the UPDATEROPEN attribute of the RDF configuration to SHARED:
ALTER RDF UPDATEROPEN SHARED
3. Restart the updaters (issue a START UPDATE command on the primary system).
4. Initiate the online dump.