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-7
Synchronizing the Primary and Backup Databases
7. Enter commands to specify the data to be inserted into the table on the primary
system:
INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME )
VALUES ( 826, "Evans", "Joan" );
INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME )
VALUES ( 3351, "MacArthur", "Bill" );
INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME )
VALUES ( 10809, "Gember", "Tom" );
Now direct your attention to the backup system (\BACK). As you perform the
necessary tasks on this system, note the following considerations:
•
DEFINEs cannot be used if you specify MAP NAMES parameter in the DUP
command.
•
The DUP operation moves the entire database, including all partitions and
indexes, by default.
•
The catalog \BACK.$DATA1.DBCAT is used for all partitions and all indexes.
8. Specify the catalog for the backup system:
CATALOG \BACK.$DATA1.DBCAT;
9. Use the SQLCI DUP command to copy the primary system’s database to the
backup system:
DUP ( *.*.* FROM CATALOG \PRIM.$TEST.DBCAT ),
MAP NAMES ( \PRIM.$DATA1.*.* TO \BACK.$DATA1.*.* ,
\PRIM.$DATA2.*.* TO \BACK.$DATA2.*.* )
SAVEALL ON;
10. After using the SQLCI DUP command, perform a TMF online dump on the primary
system to create a recovery point.
Synchronizing Databases With BACKUP and RESTORE
Utilities
You can use the BACKUP and RESTORE utilities to synchronize NonStop SQL/MP,
NonStop SQL/MX, or Enscribe databases by copying a database to tape on the
primary system and restoring the database from tape on the backup system. This
method is preferable when you want a backup tape of the primary system database, or
when the database is large.
The following example of BACKUP and RESTORE commands shows how to copy a
NonStop SQL/MP database from the primary system \PRIM to the magnetic tape
device named $TAPE and how to restore the database to volumes of the same name
on the backup system \BACK. Note that you must include the AUDITED parameter in
both the BACKUP and RESTORE commands.