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
Subvolume- and File-Level Replication
HP NonStop RDF System Management Manual—524388-003
11-3
INCLUDE and EXCLUDE Processing
INCLUDE and EXCLUDE Processing
You can specify a maximum of 100 INCLUDE and EXCLUDE parameters for each
volume, in any combination. When you specify both INCLUDE and EXCLUDE clauses
for a given volume, the clauses are processed hierarchically, with the INCLUDE
clauses processed first and EXCLUDE clauses processed second.
Error Checking
Extensive checking is done when the subvolume and file names are parsed, and
invalid names cause errors. The logic of a series of INCLUDE and EXCLUDE
clauses, however, is not checked. For example, the following is not regarded as an
error, even though it makes no sense because everything will be filtered out:
SET VOLUME INCLUDE MMTEST10.*
SET VOLUME EXCLUDE MMTEST10.*
Performance Ramifications
The extractor processes all INCLUDE and EXCLUDE clauses. If the extractor reads an
audit record associated with a file or table not specified in an INCLUDE clause, it
discards the record. Similarly, if the extractor reads an audit record associated with a
file or table specified in an EXCLUDE clause, it discards the record.
With volume-level replication, the extractor needs to test only the volume name to
determine if a record should be sent to the backup system. With subvolume- and file-
level replication, however, the extractor must also test the subvolume name and
filename. Hence there is more work to do with subvolume- and file-level replication.
Note that if you use large numbers of INCLUDE and EXCLUDE clauses for each
volume, the extractor may have to evaluate the subvolume name and filename against
multiple lists, which could lead to increased CPU usage by the extractor and lower
extractor performance than with simple volume-level replication. Therefore, you should
be careful about how many INCLUDE and EXCLUDE clauses you specify for each
volume. The use of wildcard characters in subvolume names and filenames can help
considerably. For example, to replicate all of the files within all subvolumes whose
names begin with the letters DB, you can do so with a single INCLUDE clause, as
follows:
INCLUDE DB*.*
Note. When you are adding multiple volumes using INCLUDE and EXCLUDE lists, you must
be sure to issue a RESET VOLUME command after each ADD VOLUME command or the
previous INCLUDE/EXCLUDE lists will carry forward to the next volume being added.