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
NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-18
Example
6. Table and Index information:
The RESTORE command would be as follows:
RESTORE $tape,
( MX
( ( TBL PCAT.MYSCHEMA.MYTABLE1, TGT CATALOG BCAT ),
( TBL PCAT.MYSCHEMA.MYTABLE2, TGT CATALOG BCAT ),
( TBL PCAT.MYSCHEMX.MYTABLE1, TGT CATALOG BCAT ),
( TBL PCAT.MYSCHEMX.MYTABLE2, TGT CATALOG BCAT )
),
LOCATION
(
\P.$data01.ZSDAAAAA.HEBFRW00 TO \B.$data01.ZSDAAAAA.HEBFRW00,
\P.$data02.ZSDAAAAA.HEBFRX00 TO \B.$data02.ZSDAAAAA.HEBFRX00,
\P.$data03.ZSDAAAAA.HEBFRY00 TO \B.$data03.ZSDAAAAA.HEBFRY00,
\P.$data02.ZSDAAAAA.YREWPO00 TO \B.$data02.ZSDAAAAA.YREWPO00,
\P.$data01.ZSDAAAAA.GABCDE00 TO \B.$data01.ZSDAAAAA.GABCDE00,
\P.$data02.ZSDAAAAA.GABCRF00 TO \B.$data02.ZSDAAAAA.GABCRF00,
\P.$data03.ZSDAAAAA.GABCRG00 TO \B.$data03.ZSDAAAAA.GABCRG00,
\P.$data02.ZSDAAAAA.YZZWPO00 TO \B.$data02.ZSDAAAAA.YZZWPO00,
\P.$data01.ZSDBBBBB.FGABCD00 TO \B.$data01.ZSDBBBBB.FGABCD00,
\P.$data02.ZSDBBBBB.FGABCE00 TO \B.$data02.ZSDBBBBB.FGABCE00,
\P.$data03.ZSDBBBBB.FGABCF00 TO \B.$data03.ZSDBBBBB.FGABCF00,
\P.$data03.ZSDBBBBB.IGABCD00 TO \B.$data03.ZSDBBBBB.IGABCD00,
\P.$data04.ZSDBBBBB.EFGHIJ00 TO \B.$data04.ZSDBBBBB.EFGHIJ00,
\P.$data03.ZSDBBBBB.DEFGHI00 TO \B.$data03.ZSDBBBBB.DEFGHI00
), INDEXES INCLUDED
);
Table or Index Name Guardian Names for partitions and indexes
PCAT.MYSCHEMA.MYTABLE1
PCAT.MYSCHEMA.MYINDEX1
\P.$data01.ZSDAAAAA.HEBFRW00
\P.$data02.ZSDAAAAA.HEBFRX00
\P.$data03.ZSDAAAAA.HEBFRY00
\P.$data02.ZSDAAAAA.YREWPO00
PCAT.MYSCHEMA.MYTABLE2
PCAT.MYSCHEMA.MYINDEX2
\P.$data01.ZSDAAAAA.GABCDE00
\P.$data02.ZSDAAAAA.GABCDF00
\P.$data03.ZSDAAAAA.GABCDG00
\P.$data02.ZSDAAAAA.YZZWPO00
PCAT.MYSCHEMAX.MYTABLE1
PCAT.MYSCHEMAX.MYINDEX1
\P.$data01.ZSDBBBBB.FGABCD00
\P.$data02.ZSDBBBBB.FGABCE00
\P.$data03.ZSDBBBBB.FGABCF00
\P.$data03.ZSDBBBBB.IGABCD00
PCAT.MYSCHEMAX.MYTABLE2
PCAT.MYSCHEMAX.MYINDEX2
\P.$data04.ZSDBBBBB.EFGHIJ00
\P.$data03.ZSDBBBBB.DEFGHI00