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
Managing RDF
HP NonStop RDF System Management Manual—524388-003
5-20
Reciprocal Configurations
The steps for performing a planned switchover from \A to \B in such a configuration
are:
1. On system \B, stop RDF subsystem #2. Note the local system time; you’ll need it
later.
2. On system \A, stop the business applications that access the primary database
(Applications #1).
3. On system \A, stop TMF.
4. Wait for RDF subsystem #1 on \A to shut down.
5. On system \B, restart Applications #1.
At this point, the RDF subsystem is down on both systems, the business
applications from system \A are now running on system \B, the business
applications that were running on system \B are still running on system \B, and all
audit information is being queued in TMF audit trails on system \B.
6. When system \A is ready to resume its normal operations, restart TMF.
7. On system \B, restart RDF subsystem #2 (the RDF subsystem that replicates data
from \B to \A for the business applications that normally run on \B). The subsystem
resumes its processing exactly where it was when you stopped it in step 1.
8. On system \B, initialize RDF subsystem #1. In the INITIALIZE RDF command,
include the INITTIME option and specify the timestamp you noted in step 1.
Configure the subsystem to replicate data from \B to \A for Applications #1 (the
business applications that were moved from system \A to system \B).
When the RDF subsystem #1 extractor starts sending current audit information to \A
(and at a convenient time with respect to your processing environment), stop
Applications #1 and carry out a planned switchover from \B to \A as follows:
1. On system \B, create an audited Enscribe file on each data volume in the RDF
subsystem #1 configuration.
2. Wait until all of those files are created on system \A.
3. On system \B, stop RDF subsystem #1.
4. Purge the Enscribe files on both systems.
5. On system \A, initialize RDF subsystem #1 using the INITTIME option and
specifying the current (for \A) local time.
6. On system \A, restart Applications #1.