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-5
Using RDFCOM Noninteractively
•
If you press BREAK when an RDFCOM command that displays information (such
as STATUS RDF) is in progress, RDFCOM terminates execution of this command
and prompts you for another one.
•
If you press BREAK when an RDFCOM command that changes the RDF
configuration or status (such as ALTER RDF) is in progress, RDFCOM continues
to execute this command while immediately prompting you for another one.
Using RDFCOM Noninteractively
When you use RDFCOM noninteractively, you enter one or more commands to
RDFCOM at the same time you start your session. RDFCOM executes all of these
commands, and then terminates the session and returns control of your terminal to
TACL.
To run RDFCOM noninteractively, you enter the RDFCOM keyword, the control
subvolume name, and one or more RDFCOM commands on the same line. The
following example includes a command that displays current configuration information
for the RDF monitor (the example assumes that \LONDON is the primary system, the
suffix character “A” was specified in the INITIALIZE RDF command, and the user did
not explicitly name the monitor process):
1> RDFCOM LONDONA; INFO MONITOR
RDFCOM - T0346A07 - 05JUL05
(C)2005 Hewlett-Packard Development Company, L.P.
MONITOR CPUS 0:1
MONITOR PRIORITY 170
MONITOR PROCESS $MON
2>
As this example illustrates, after the command is executed, the RDFCOM session
automatically terminates and the TACL prompt again appears.
To specify multiple RDFCOM commands on a single line, you must enter a semicolon
(;) to separate each command from the preceding one. For example:
3> RDFCOM LONDONA; INFO MONITOR; INFO EXTRACTOR
If any command on the line fails, RDFCOM reports the error and terminates without
executing any of the subsequent commands.
Note. On your terminal, the BREAK key might not actually be labeled “BREAK.” All terminals,
however, have some key or combination of keys that perform the BREAK operation. Before
using RDFCOM, determine how this operation is selected on your terminal.