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
Operating and Monitoring RDF
HP NonStop RDF System Management Manual—524388-003
4-6
Using RDFCOM From a Command File
Using RDFCOM From a Command File
RDFCOM can also read commands from a command file. The command file is a text
file that contains the RDFCOM commands you want to execute, which you prepare
using your standard text editor. You might, for example, create a command file named
RDFSET that contains the following commands:
SET RDF SOFTWARELOC $SYSTEM.RDF
SET RDF LOGFILE $0
SET RDF UPDATERDELAY 10
SET RDF UPDATERTXTIME 60
SET RDF UPDATERRTDWARNING 60
SET RDF UPDATEROPEN PROTECTED
SET RDF NETWORK ON
SET RDF NETWORKMASTER ON
SET RDF UPDATEREXCEPTION OFF
ADD RDF
To run RDFCOM and execute the commands in this file, supply the command file
name in the IN option of the command to start RDFCOM:
4> RDFCOM /IN RDFSET/ control-subvolume
When it uses a command file in this way, RDFCOM works in batch mode: RDFCOM
begins the session, reads and executes each command from the command file, and
displays the associated output at your terminal. When RDFCOM reaches the end of
the command file or encounters an EXIT command within that file, RDFCOM
terminates the session and returns control to TACL. If RDFCOM encounters an error
while reading the command file, RDFCOM displays an error message, terminates the
session, and returns control to TACL.
If you include both the IN and OUT options in the RDFCOM command, RDFCOM
reads commands from the command file specified by the IN option and directs all
output to the destination specified by the OUT option. For example, the following
command causes RDFCOM to read commands from the command file COMFILE1 and
list the output to the printer $LP:
5> RDFCOM/IN COMFILE1, OUT $LP/ control-subvolume
In addition, you can execute the contents of a command file within an interactive
RDFCOM session by using the OBEY command. If you regularly use a series of
sequential RDF operations in your interactive sessions, for instance, you might want to
specify these in a command file. Then each time you need these operations, you can
invoke them with a single OBEY command rather than with multiple individual
RDFCOM commands.
As an example, many users find that initializing RDF is much easier and more
consistent when done using command files. Suppose you have created a command
file named RDFINIT that contains the commands for initializing the subsystem. You
could execute all these commands by simply entering:
]OBEY RDFINIT