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-21
Command Overview
RDF State Requirement
After RDF is initialized, you can issue a DELETE command only when RDF is stopped.
Usage Guidelines
For the DELETE command to have any effect, a configuration record must already
exist for the secondary image trail or updater process associated with the volume
name supplied (that is, someone must have previously issued an ADD IMAGETRAIL
or ADD VOLUME command for the volume).
When you issue a DELETE VOLUME command, RDF responds as follows:
•
The extractor process stops sending image data for the volume specified in the
DELETE VOLUME command.
•
The updater process associated with this volume will not be started.
Use the DELETE VOLUME command if an update volume on the backup system
becomes unusable and you want RDF to continue maintaining the other volumes. In
such a case, you must stop RDF at the primary system, issue the DELETE VOLUME
command, and then restart RDF.
When it is convenient to do so, you can resynchronize the affected volume, configure a
new updater process by issuing appropriate SET VOLUME commands, and then issue
an ADD VOLUME command to restart RDF protection for the affected primary volume.
Before you can remove an image trail with the DELETE IMAGETRAIL command, you
must delete all updater processes that are configured to that image trail. The DELETE
IMAGETRAIL command then deletes the configuration record for the image trail and all
image files currently belonging to that trail. Thus, the network connection to the
backup system must be available when you enter this command.
If you need to change an updater’s image trail volume, it is recommended that you
stop TMF; wait for RDF to stop; delete the volume; re-add the volume back into the
configuration, associating it to a different image trail volume; and then restart the TMF
and RDF subsystems. This is the only way to ensure that the backup database will
remain synchronized with the primary database.
Examples
Assume that RDF is protecting primary system data volumes $DATA01, $DATA02, and
$DATA03, and that all three volumes are configured to the MAT. Assume also that the
changes are being replicated to backup system volumes $DATA1, $DATA2, and
$DATA3, and that the updaters for those volumes are acquiring their audit data from
secondary image trail volumes $SECIT1, $SECIT2, and $SECIT3, respectively.
To delete the configuration records for the updater process and secondary image trail
associated with $DATA03, enter the following commands:
]DELETE VOLUME $DATA03
]DELETE IMAGETRAIL $SECIT3