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-8
Synchronizing the Primary and Backup Databases
1. Back up the database from \PRIM onto tape:
BACKUP $TAPE, (*.*.* FROM CATALOG \PRIM.$TEST.DBCAT),
AUDITED, INDEXES IMPLICIT, LISTALL
2. Restore the database from tape onto \BACK (assuming the catalog was already
created):
RESTORE $TAPE, *.*.*, AUDITED,
MAP NAMES ( \PRIM.$DATA1.*.* TO \BACK.$DATA1.*.* ,
\PRIM.$DATA2.*.* TO \BACK.$DATA2.*.* ),
CATALOG \BACK.$DATA1.DBCAT, INDEXES IMPLICIT,
SQLCOMPILE OFF, LISTALL
The next examples of BACKUP and RESTORE commands show how to copy all files
from the primary system volumes $DATA01, $DATA02, $DATA03, and $DATA04 to the
magnetic tape device named $TAPE and how to restore these files to volumes of the
same name on the backup system. Note that you must include the AUDITED
parameter in both the BACKUP and RESTORE commands.
BACKUP $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*,
$DATA04.*.*), AUDITED
RESTORE $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*,
$DATA04.*.*), AUDITED
Synchronizing Databases With FUP
You can use the FUP DUP command to copy Enscribe database files from the primary
system to the backup system. If you use FUP DUP, the “FUP ALTER filename , NO
AUDIT” command is performed implicitly for each backup file that corresponds to a
primary file protected by RDF. You will therefore need to turn the audit flags back on for
all the data volumes on the backup system after the FUP DUP operation is complete.
Synchronizing Partitioned Files
When synchronizing partitioned files, you must consider one major difference between
NonStop SQL/MP tables and Enscribe files: a NonStop SQL/MP catalog has a
description of all indexes of a table and partitions of a partitioned table, but a
partitioned Enscribe file has no associated catalog.
To ensure the consistency of a NonStop SQL/MP catalog, you must copy all partitions
of a NonStop SQL/MP table and its dependent indexes at one time rather than on a
partition basis. You can use either the SQLCI DUP command or the BACKUP and
RESTORE utilities to copy the partitions.
Note. For this copy operation to work correctly, do not specify the SAVEALL parameter in the
FUP DUP command.