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
Process-Lockstep Operation
HP NonStop RDF System Management Manual—524388-003
14-6
The Lockstep Gateway Process
The Lockstep Gateway Process
The RDF lockstep gateway process is managed by the Subsystem Control Facility
(SCF). To start a lockstep gateway process, you must create and execute an SCF
script file. The recommended script settings are:
ASSUME PROCESS $ZZKRN
ADD #LSGO, &
NAME $ZLSGW, &
CPU FIRSTOF (1,2,3), &
PROGRAM volume.subvolume.LSGO, &
STARTMODE APPLICATION, &
STARTUPMSG "ENABLE <extractor-process-name>", &
AUTORESTART 10
START #LSGO
For detailed information about these attributes, see Configuring and Managing Generic
Processes in the SCF Reference Manual. For some attributes, however, restrictions
apply when the attributes are used with a lockstep gateway process.
NAME
This attribute must be $ZLSGW. If you specify anything else, the lockstep gateway
stops and you cannot perform lockstep operations. Note that this means you can only
have a single lockstep gateway process running on your primary system.
PROGRAM
This attribute specifies where the RDF gateway object code resides. Typically, that
location is the same volume and subvolume where all of the other RDF software
resides. Note that the object name is LSGO, and that you must fully qualify the name.
For example, you might specify the PROGRAM attribute as $SYSTEM.RDF.LSGO.
STARTUPMSG
This attribute must include the process name of your RDF extractor (for example,
STARTUPMSG "ENABLE $MEXT"). The startup message must also include either
ENABLE or DISABLE as the first parameter. Failure to include either of these
parameters will cause the gateway to stop. Note that the gateway can only
communicate with one extractor. If you have multiple RDF subsystems using the same
node as their primary system, only one of them can execute lockstep operations.
AUTORESTART
This attribute specifies the number of times SCF attempts to restart the gateway
process if it should stop unexpectedly. You should set this attribute to 10.