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
Online Database Synchronization
HP NonStop RDF System Management Manual—524388-003
7-16
Partial Database Synchronization Issues
You must load all the partitions of a relative file. Therefore, only one command is
possible.
FUP LOAD $DATA1.TEST.PART0100, $DATA1.TEMP.PART0100,
SHARE
You can then use BACKUP and RESTORE (or FUP DUP) with the PARTONLY option
to copy the loaded partition you need to the backup system.
Entry-sequenced and Unstructured Files
Currently there is no reliable mechanism to synchronize these file types online. Entry-
sequenced and unstructured files should be synchronized offline.
NonStop SQL/MP Tables Without Partitions
Key-sequenced Tables with SYSKEY
Because the SQLCI LOAD operation generates new SYSKEY values in the backup
table, key-sequenced tables containing SYSKEYs cannot be synchronized online.
Key-sequenced Tables without SYSKEY and Relative Tables
First create a non-audited duplicate table on the primary system and then load it. Use
BACKUP and RESTORE (or SQLCI DUP) to move the duplicate table to the backup
system.
Alternatively, you can use the create and load method to put the duplicate tables
directly onto the backup system, provided you have enough Expand capacity to handle
both the data being loaded and the audit being shipped to the backup system by the
extractor.
There are no special considerations for key-sequenced tables with indexes, but see
below for issues regarding the synchronization of indexes.
NonStop SQL/MP Tables With Partitions
The utilities associated with and related to the NonStop SQL/MP product have
limitations that make synchronization of individual partitions complicated and difficult.
The following represent methods that enable you to circumvent these limitations.
1. SQLCI DUP does not have a PARTONLY option. Therefore, you cannot
duplicate only an individual partition.
2. While BACKUP and RESTORE have the PARTONLY option, if you have backed
up tables from the primary system, you must use the MAP NAMES option when
restoring them on the backup system in order to specify the correct system name.
You cannot, however, include both the MAP NAMES and PARTONLY options in
the RESTORE operation. Therefore, because you must use MAP NAMES, you
cannot restore only a single partition.