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
HP NonStop RDF System Management Manual—524388-003
15-1
15
NonStop SQL/MX and RDF
RDF supports replication of NonStop SQL/MX user tables (file code 550) and indexes
(file code 552). These operations are supported in much the same way as they are
with NonStop SQL/MP, and the same types of data and DDL operations are replicated.
This section describes the following operations:
•
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
•
Synchronizing a NonStop SQL/MX database online
•
Synchronizing a single NonStop SQL/MX partition offline
•
Synchronizing a single NonStop SQL/MX partition online
•
Correcting incorrect NonStop SQL/MX name mapping
•
Querying metadata
•
Restoring to a specific location
•
Comparing NonStop SQL/MX tables
Given the way the name mapping works between NonStop SQL/MX objects and their
underlying Guardian file names, there are special considerations when setting up
NonStop SQL/MX objects to be replicated by RDF. This section describes those
issues.
The command interface for NonStop SQL/MX is MXCI.
Including and Excluding SQL/MX Objects
By default, RDF provides volume-level protection, wherein changes to all audited files
and tables on each protected primary system data volume are replicated to an
associated backup system data volume.
RDF also supports subvolume- and file-level replication. To use this capability, you use
INCLUDE and EXCLUDE clauses when configuring updaters to identify specific
database objects you want replicated or not replicated. INCLUDE and EXCLUDE
clauses require the use of Guardian names. If you have an ANSI-named NonStop
SQL/MX object that you want to include or exclude, you first must get the underlying
Guardian name by using the MXGNAMES utility or the MXCI SHOWDLL command.
The use of INCLUDE and EXCLUDE clauses is described in Section 11, Subvolume-
and File-Level Replication.