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
Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-83
Command Overview
Usage Guidelines
The SET VOLUME command enters the parameter values specified for the updater in
this command into the RDF configuration table in memory. This table serves as an
input buffer only, and so these values do not affect the subsystem until they are applied
to the RDF configuration file with the ADD command.
For ATINDEX values greater than 0, the specified value must match the audit trail
number of a configured auxiliary audit trail. If you specify SET VOLUME ATINDEX 2,
for example, there must be a configured auxiliary audit trail AUX02.
Furthermore, RDF objects with a particular ATINDEX value greater than 0 must
together constitute a complete set, as follows:
•
If there is an extractor with an ATINDEX value of 1, there must also be a receiver
with an ATINDEX value of 1.
•
If there is a receiver with an ATINDEX value of 1, there must also be a secondary
image trail with an ATINDEX of 1.
•
An updater with an ATINDEX value of 1 must be protecting a primary system data
volume configured to auxiliary audit trail AUX01, and its secondary image trail must
also have an ATINDEX value of 1.
Once an updater process has been added to the RDF configuration, you cannot alter
its INCLUDE or EXCLUDE parameters. If you must do so, you have to delete the
updater and then add it back to the configuration as described in Section 11,
Subvolume- and File-Level Replication.
You can specify a maximum of 100 INCLUDE and EXCLUDE parameters for each
volume, in any combination.
Unlike the behavior of other SET parameters, successive INCLUDE or EXCLUDE
parameters do not supersede preceding ones in the RDF configuration memory table
(they merely extend the include and exclude lists for the particular data volume).
As with SET parameters for all RDF object types, specified INCLUDE and EXCLUDE
parameters remain in the RDF configuration memory table even after you add the
updater to the configuration. This can be useful, for example, if the same INCLUDE
and EXCLUDE parameters apply to multiple volumes. If the parameters vary from one
volume to the next, however, you must remember to issue a RESET VOLUME
command after adding each updater (otherwise the INCLUDE and EXCLUDE
parameters for each added updater are applied to the next added updater as well).
To view the current INCLUDE and EXCLUDE parameters in the RDF configuration
memory table, issue a SHOW VOLUME command.
To view the INCLUDE and EXCLUDE parameters for an updater that has already been
added, issue an INFO VOLUME or INFO $volume command.