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-20
Online Installation and Initialization Without Stopping
RDF
6. Install the new RDF software in a different volume.subvolume from that housing
the current version of RDF that is running. For example, if you are upgrading to
T0346AAV, you might specify $system.rdfaav.
7. Run $system.rdfaav.RDFCOM and initialize a new RDF configuration, using
•
the suffix parameter (such as suffix "a")
•
the INITTIME parameter, using the timestamp calculated in Step 4 above
(11JUN2004 13:28).
Initialize RDF, backupsystem \RDF06, suffix a, inittime 11JUN2004 13:28
8. If you do not already have a copy of the configuration script used for the current
version of RDF, you can get it by starting the RDFCOM for that RDF subsystem
and using the INFO *, OBEYFORM command.
9. Use the same script to configure your new RDF subsystem, but you will need to
change the following:
a. Set SOFTWARELOC to $system.rdfaav
b. Set the extractor name(s) to a different name(s)
c. Set the monitor name to a different name
d. Set the receiver name(s) to different name(s)
10. Now start your new RDF subsystem:
] run $system.rdfaav.rdfcom rdf04a
] start RDF, update off
Note that you now have parallel sets of extractors shipping audit to parallel sets of
receivers for the two operating RDF subsystems, although each subsystem has its
own control subvolumes and its own imagetrail subvolumes.
11. When the extractor(s) for RDF04A have caught up, do the following:
a. Issue a STOP RDF command for the previous RDF subsystem.
b. Issue an UNPINAUDIT command for the previous subsystem.
c. Issue a START UPDATE command for the RDF04A subsystem. Wait until all
updaters have caught up.
d. Purge the previous control subvolumes on the primary and backup, as well as
the imagetrails for the previous subsystem.
You have now installed and started new RDF software without jeopardizing disaster-
recovery protection by having to stop RDF.
What About Disaster Points?
If the primary system fails between steps 1 and 10, you perform the takeover operation
using your previous RDF subsystem. If the primary system fails at or after step 11, you
perform the takeover operation using the new subsystem (RDF04A).