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
Preparing the RDF Environment
HP NonStop RDF System Management Manual—524388-003
2-11
Designing Transactions for RDF Protection
The only file-label modifications that RDF replicates are the following:
Purge Operations
The two kinds of purge operations are PURGEDATA and PURGE. RDF replicates
PURGEDATA operations for NonStop SQL/MP tables, NonStop SQL/MX tables, and
Enscribe files. RDF replicates PURGE operations for Enscribe files if
REPLICATEPURGE is set on.
Partitioned Files
All partitions of a partitioned Enscribe file or NonStop SQL/MP or NonStop SQL/MX
table must reside on volumes protected by RDF, or none should. Corresponding
partitions on each system must have the same key values.
If you are using RDF to replicate the creation of partitioned files and an RDF takeover
operation occurs in the midst of a set of creations, some partitions might have been
created while others were not, because each partition of a partitioned file is created
independently.
Temporary Disk Files
File creation, modification, and updates are not replicated for audited temporary disk
files. All audit data is filtered out by the extractor on the primary system for file names
of the form $volume.#nnnnnnn.
A file name that begins with # (pound sign) indicates a temporary disk file; this type of
file name is returned when only the volume name is specified in a call to the file system
CREATE procedure or FILE_CREATE_ procedure.
CREATE To create an audited Enscribe file
ALTER MAXEXTENTS To increase the number of extents for an audited
Enscribe file
PURGEDATA To purge data from an audited Enscribe file
PURGE To purge an Enscribe file (if REPLICATEPURGE is
enabled)
Caution. For partitioned files, it is essential that the partial key value for Enscribe files, or first
key value for NonStop SQL/MP and NonStop SQL/MX tables, on the backup system exactly
match those on the primary system. This is the RDF database administrator’s responsibility.
If the partitions are not mapped correctly on the backup system, then some updates might be
applied to the wrong partition, producing a corrupt database.