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
Zero Lost Transactions (ZLT)
HP NonStop RDF System Management Manual—524388-003
16-7
RDF Configuration Attributes
RDF Configuration Attributes
RDF Remote Mirror Configuration
When declaring the attributes of the RDF configuration record, you use the following
optional attribute to specify whether ZLT is enabled or disabled:
SET RDF REMOTE MIRROR [ ON | OFF ]
The default is off. If this attribute is off, normal RDF operations are unchanged, as is
execution of the RDF TAKEOVER command. If this attribute is on, then you must also
set other RDF and extractor attributes, and the TAKEOVER operation has an
additional step: connecting the remote mirrors to the standby system.
RDF Remote Standby Configuration
If you set the RDF REMOTE MIRROR attribute on, you must also set the system name
of a standby system. This standby system can be either a third system, apart from the
primary and backup systems, or it can be the backup system itself. The syntax for
specifying the standby system name is as follows.
SET RDF REMOTE STANDBY node-name
node-name must be a valid name and must identify a system in your current Expand
network. If you set the standby to a different node than your backup system, the
specified system must be accessible to the backup system.
RDF Configuration Record Validation
When you ADD the RDF configuration record, the following checks are performed:
•
If you set the RDF REMOTE MIRROR attribute on, but did not issue a SET RDF
REMOTE STANDBY command, the ADD command fails.
•
If you set the RDF REMOTE MIRROR attribute off and issued a SET RDF
REMOTE STANDBY command, the ADD command fails.
ZLT is only a feature of the RDF/ZLT product: you cannot add the RDF record with ZLT
attributes if you do not have the RDF/ZLT product installed.
Note. The hardware configuration for use of a remote mirror on the audit trail is not part of the
RDF configuration, nor is it part of any RDF validation. You must have placed the remote mirror
in a location where you can connect it to the standby system at the time of a takeover. If you fail
to do this, the RDF takeover operation fails until you have connected the remote mirror to the
standby system or turned off remote mirroring (see ALTER RDF Remote Mirror Configuration
).