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-101
Command Overview
Where Issued
You can issue the STOP RDF, DRAIN and STOP RDF, REVERSE commands only at
the primary system.
Security Restrictions
You can issue the STOP RDF command if you are a member of the super-user group
that initialized RDF and have a remote password from the RDF primary system to the
backup.
RDF State Requirement
You can issue the STOP RDF, DRAIN and STOP RDF, REVERSE commands only
while RDF is running and update is on.
Usage Guidelines
The decision to stop RDF is a management decision that should be carefully planned
and performed. Operators should never issue the STOP RDF command strictly on
their own initiative.
To execute a planned RDF shutdown, you should generally use the STOP TMF
command rather than STOP RDF. Issue the STOP TMF command at the primary
system while the communications lines are up. In addition to stopping TMF, this action
stops all RDF processes and saves the context of each process in a file.
For information about when to use the STOP RDF command and how it affects the
primary and backup databases, see Restarting RDF in section 5. For more information
about stopping RDF, continue with this discussion.
There are three ways to stop RDF:
•
Issue a STOP TMF command at the primary system.
As noted earlier, this is the recommended method for terminating RDF processing.
When you issue the TMFCOM command STOP TMF, RDF also shuts down after
RDF encounters the TMF shutdown record in the MAT. This method ensures that
the primary and backup databases are logically identical with one another when
RDF stops. When you restart RDF, the context file directs RDF where to resume.
•
Issue a STOP RDF command at the primary system.
If the decision has been made to stop RDF without stopping TMF, issue a STOP
RDF command at the primary system. RDF stops immediately after all RDF
processes save context information in the context file.
•
Issue a STOP RDF command at the backup system.
You should use this method of stopping RDF only if either of the following is true:
•
The RDF monitor process is not running on the primary system.