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
Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-19
Online Installation and Initialization Without Stopping
RDF
Online Installation and Initialization Without Stopping RDF
For the procedure described under Initializating RDF Without Stopping TMF, you are
required to stop RDF, delete the control subvolumes, reinitialize RDF, and then restart
RDF. Although unlikely, stopping RDF does leave you briefly vulnerable to inconsistent
data on the backup system if your primary system should fail after you stop RDF and
delete the previous RDF control files, but before you restart RDF.
By using the procedure that follows, you can install and initialize the RDF product
without stopping RDF, TMF, or your applications.
The procedure is best described by example. Assume that you are running RDF from
\RDF04 to \RDF06, and that your control subvolume is RDF04.
1. For your current RDF subsystem (RDF04->RDF06), issue an RDFCOM STATUS
RDF command on the primary system.
2. Note the general timestamp and the RTD times (11JUN2004 13:30).
Status of \RDF04 -> \RDF06 RDF 2004/06/11 13:30:42.047
Control Subvol: $SYSTEM.RDF04
Current State : Normal
RDF Process Name RTD Time Pri Volume Seqnce Rel Byte Addr Cpus Error
------------------ ----- --------- --- ------- ------ ------------- ----- -----
Monitor $MN00 185 $AUDIT 4047 1: 2
Extractor (0) $EX00 00:00 185 $AUDIT 3971 49144448 1: 2
Receiver (0) $RC00 00:00 185 $DATA05 108 1: 2
Imagetrail (0) $DATA01 8910
Imagetrail (0) $DATA02 8166
Imagetrail (0) $DATA03 8164
Imagetrail (0) $DATA04 5130
Purger $PR00 185 1: 2
$DATA01 -> $DATA01 $UP01 1:26 185 $DATA01 8890 2702560 0: 1
$DATA02 -> $DATA02 $UP02 0:02 185 $DATA02 8147 2414040 1: 2
$DATA03 -> $DATA03 $UP03 0:05 185 $DATA03 8146 5735088 2: 3
$DATA04 -> $DATA04 $UP04 0:10 185 $DATA04 5124 3421980 3: 0
]
3. If the extractor RTD is greater than 0:00, wait until the extractor reports this value.
If the value is 0:00, take the highest updater RTD and round up to the next minute.
In this example, the highest updater RTD rounded up to the next minute is 2:00.
4. Subtract this value from the general timstamp (11JUN2004 13:28).
5. Issue the STOP UPDATE command. Note, this command stops the updaters but
allows the extractor and receiver to continue to shipping and storing audit,
respectively.