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-37
Enabling RDF Operations
If RDFCOM cannot determine the configuration file version, it prints the following
message to the home terminal and aborts the command:
If that happens, you should make sure you are using the correct RDFCOM. If you are
using the correct version and you get this message, then you must reinitialize RDF.
Enabling RDF Operations
After you have copied all pertinent database files from the primary system to the
backup system, installed the RDF software on both systems, initialized and configured
TMF on the primary and all backup systems, and initialized and configured RDF, you
can then start the TMF and RDF subsystems. You must start TMF on the primary and
all backup systems before you can start RDF.
Starting TMF
To start or restart TMF, issue the TMFCOM command START TMF. If you plan to start
the applications being protected by TMF before starting RDF, you can include the
DISABLE BEGINTRANS parameter in the START TMF command; this parameter
prevents the applications from starting any transactions until you issue the TMFCOM
command ENABLE BEGINTRANS. For details about these TMFCOM commands, see
the HP NonStop Transaction Management Facility (TMF) Reference Manual.
Starting RDF
There are two ways to start RDF: with updating enabled and with updating disabled. If
updating is enabled, the updaters begin updating the backup database immediately. If
updating is disabled, they do not (but the extractor and receiver continue to work
normally). The default is to start RDF with updating enabled.
To start RDF, issue the RDFCOM command START RDF, as follows:
]START RDF
Notice that to issue this command, you must have an RDFCOM session running on the
primary system and meet all of the following requirements:
•
You aree logged on as a member of the super-user group (or have execution
access for an RDFCOM object that has been PROGID'd by the customer).
•
You have the same super ID that was used to initialize RDF (or have execution
access an RDFCOM object that has been PROGID'd by the customer). Note that
you can have a different super ID if the RDF OWNER attribute has been set.
•
You have a remote password on the primary system (it is also recommended, but
not required, that you have a remote password on the backup system as well).
RDFCOM version (version) does not match the config file
version <unknown>