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-5
Synchronizing the Primary and Backup Databases
Backing up partitioned files requires some extra planning, as explained in
Synchronizing Partitioned Files later in this section.
For a complete discussion of synchronized versus unsynchronized databases and their
ramifications, see Understanding Database States in section 6.
Re-Creating an Empty Database With an OBEY Command
If a database on the primary system does not contain any data yet, use either an
OBEY command file or a TACL macro to re-create the database on the backup
system.
To create logically identical database structures on the primary and backup systems,
first do the following at the primary system:
1. Place the database creation commands in either an EDIT (command) file or TACL
macro or routine. See the HP NonStop TACL Reference Manual for more
information.
2. Through the TACL command interpreter, issue an OBEY filename command or run
the macro to create the primary database.
3. Copy the command file or TACL macro to the backup system.
Now do the following on the backup system:
•
Change any system references in the command file or TACL macro from the
primary system name to the backup system name. If the volume names are
different or if you want a different database layout on the backup system, change
volume references as well.
•
Through the TACL command interpreter, issue an OBEY filename command or run
the macro to create the backup database.
Synchronizing Databases With SQLCI Commands
This topic only applies to NonStop SQL/MP databases. For instructions on how to
synchronize NonStop SQL/MX databases, see Section 15, NonStop SQL/MX and
RDF.
You can use SQLCI commands to synchronize NonStop SQL/MP databases online.
For NonStop SQL/MP databases, you create the catalog or catalogs on the backup
system and then duplicate the objects registered in each catalog.
For complete information about using SQLCI to copy databases, see the information
on moving databases in the HP NonStop SQL/MP Installation and Management Guide.
For the syntax of SQLCI commands, see the SQLCI online help or the HP NonStop
SQL/MP Reference Manual.
The following example shows how you can create a partitioned NonStop SQL/MP table
with an alternate index on the primary system with the SQLCI CREATE command, and