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
Messages
HP NonStop RDF System Management Manual—524388-003
C-82
RDFCOM Messages
Cause. You tried to add an auxiliary extractor or receiver to an RDF environment that
had previously been configured for lockstep operations.
Effect. The ADD EXTRACTOR or ADD RECEIVER command fails.
Recovery. You cannot have both lockstep operation and protection for data configured
to an auxiliary audit trail in the same RDF subsystem. If you want lockstep protection,
then your data must be placed on TMF data volumes configured to the Master Audit
Trail. If your data must remain on TMF data volumes configured to auxiliary audit
trails, then you must reconfigure your RDF subsystem without lockstep protection.
You must rethink what data you want protected and whether or not it needs lockstep
protection. You may have to configure two separate RDF subsystems, protecting
lockstep data with one subsystem, and protecting the data associated with auxiliary
audit trails with the other RDF syubsystem. You cannot have lockstep protection for
data configured to auxiliary audit trails.
Cause. You tried to add a volume to the RDF configuration and use the online
database synchronization feature, but RDF/IMP or IMPX is not installed.
Effect. The ADD command fails.
Recovery. If you want to perform online database synchronization, RDF/IMP or IMPX
must be installed on both the primary and backup systems.
Cause. In response to your INITIALIZE RDF command and your confirmation to
proceed with that command’s execution, RDFCOM has found the record with the
specified TMF shutdown timestamp in the MAT and RDF is ready to be initialized at
that shutdown point. This message requests your confirmation to proceed further.
Effect. If you respond YES or Y, RDF will be initialized at the shutdown point you
specified; when RDF starts, the extractor will begin reading audit at that point in the
audit trail. If you respond NO or N, however, the subsystem will not be initialized.
Recovery. This is an informational message; no recovery is required.
Data from auxiliary audit trails is not allowed with lockstep
Database synchronization is only available with the
NonStop(TM) RDF/IMP(X) product
Do you still wish to start at this point? [Y/N]