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-25
Configuring RDF
UPDATEREXCEPTION Parameter
The UPDATEREXCEPTION parameter specifies the manner in which exception files
are used.
When set to ON (the default value), the updaters log an exception record for each and
every audit record they must undo during a takeover.
When set to OFF, the updaters log exception records only for the first and last audit
records that must be undone (the minimum logging necessary to support Triple
Contingency operation).
LOCKSTEPVOL Parameter
The LOCKSTEPVOL parameter specifies the primary system disk volume on which the
RDF lockstep file (<control-subvolume>.ZRDFLKSP) is to be located. The specified
volume must be configured to the Master Audit Trail (MAT), and either the entire
volume or at least the lockstep file must be protected by the RDF subsystem. For
information about the RDF lockstep capability, see Section 14, Process-Lockstep
Operation.
REPLICATEPURGE Parameter
The REPLICATEPURGE parameter specifies whether Enscribe purge operations on
the primary system are to be replicated on the backup system.
When set to OFF (the default value), Enscribe purge operations are not replicated.
You should use the default (OFF) for all RDF configurations (unless you have a
specific need for replicating Enscribe purge operations).
If you configure the RDF subsystem to replicate network transactions, you should not
replicate Enscribe purge operations because doing so might result in unexpected
errors during the updater network undo processing.
When set to ON, Enscribe purge operations on the primary system are replicated on
the backup system.
REMOTE MIRROR Parameter
The REMOTE MIRROR parameter specifies whether ZLT is enabled or disabled. The
default is off. For information about the ZLT capability, see Section 16, Zero Lost
Transactions (ZLT).
REMOTE STANDBY Parameter
The REMOTE STANDBY parameter specifies the system name of the ZLT standby
system. node-name must be a valid name and must identify a system in your current
Expand network. The default is the name of the backup system. For information about
the ZLT capability, see Section 16, Zero Lost Transactions (ZLT).