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-7
Considerations When Synchronizing Entire
Databases
Special Consideration for Enscribe Files
If you create empty Enscribe files on your primary system, you should create them with
the audit attribute set off. This is particularly important if you create them on volumes
protected by RDF. If you create them as audited files on database volumes that are
being protected by RDF, the updaters also create them on the backup system. You
then must purge the files on your backup system before copying the loaded files from
the primary system.
General Considerations for NonStop SQL/MP Tables
•
Key-sequenced Tables without SYSKEY. To improve the performance of the
load operations significantly, specify the SORTED option.
•
Key-sequenced Tables with SYSKEY. Because the SQLCI LOAD operation
generates new SYSKEY values, key-sequenced tables containing SYSKEYs
cannot be synchronized online.
•
Relative Tables. To ensure complete consistency with the source files, specify
the NO COMPACT option.
•
Entry-sequenced Tables. Currently there is no reliable mechanism to
synchronize entry-sequenced tables online. These tables should be synchronized
offline.
•
Partitioned Tables. You can initiate the load operation with a single command by
executing the LOAD command against the primary partition.
•
Index Tables. With regard to index tables, there are several considerations for
relative and key-sequenced tables. Regardless of base table type, you cannot
load an index table by itself. Index tables can only be loaded when the associated
relative or key-sequenced table is loaded.
If you want the associated index tables loaded when you load a relative or key-
sequenced table, you must create empty index tables first, before issuing the
LOAD command. When you load the base table, the index tables are loaded
automatically.
Alternatively, you can load your base tables without index tables. Then you can
create and populate your index tables with the NonStop SQL/MP product before
you start the RDF updaters.
If you fail to create the index tables before issuing the START UPDATE command,
the affected updater reports a file system error 11 (File not found) when trying to
apply an update to an index table, and it continues to retry the update. In this
situation, the updater does not make forward progress until you create the index on
your backup system.