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-28
Configuring RDF
WAIT causes RDF to wait for the trigger process to terminate before shutting down.
NOWAIT specifies that once the trigger process is launched, RDF can immediately
proceed to shut down.
Setting Network Configuration Record Parameters
Use SET NETWORK and ADD NETWORK commands to configure the following
network configuration record parameters:
•
PRIMARYSYSTEM system-name
•
BACKUPSYSTEM system-name
•
REMOTECONTROLSUBVOL subvolume-name
•
PNETTXVOLUME volume-name
If you are configuring the network master RDF subsystem, you must include a network
configuration record for every RDF subsystem in the RDF network (including the
network master itself). Each of those records must include the following parameters:
If you are configuring a non network master RDF subsystem, you must include a single
network configuration record containing the following attributes:
Thus, within its configuration file, the network master has all necessary information
about every system in the RDF network (whereas the other systems have only a
pointer enabling them to obtain information about other systems in the network).
PRIMARYSYSTEM Parameter
The PRIMARYSYSTEM parameter specifies the name of a primary system. There is
no default value. Each primary system within an RDF network must be unique within
the network. An RDF network cannot contain two or more RDF subsystems with the
same primary system (that is, it cannot contain RDF subsystems for \A to \B and \A to
\C).
PRIMARYSYSTEM system-name Name of the primary system.
BACKUPSYSTEM system-name Name of the associated backup system.
REMOTECONTROLSUBVOL
subvolume-name
Name of the primary system’s remote control
subvolume.
PNETTXVOLUME volume-name Name of the primary system volume on which
the RDF subsystem stores an audited network
synchronization file.
PRIMARYSYSTEM system-name Name of the network master’s primary system.
BACKUPSYSTEM system-name Name of the network master’s backup system.
REMOTECONTROLSUBVOL
subvolume-name
Name of the network master’s remote control
subvolume.