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
NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-8
Online Database Synchronization With NonStop
SQL/MX Objects
For example, assume you have the objects on your primary system that have the
following fully qualified Guardian names:
\pnode.$DATA01.ZSDABCDEF.FILE100
\pnode.$DATA02.ZSDABCDEF.FILE100
\pnode.$DATA03.ZSDABCDEF.FILE100
For the RESTORE command, you must name the qualified Guardian filenames of
your source objects and also the qualified Guardian filenames of your target
objects in the LOCATION clause.
LOCATION
( \pnode.$DATA01.ZSDABCDEF.FILE100 TO \bnode.$DATA0A.ZSDABCDEF.FILE100,
\pnode.$DATA02.ZSDABCDEF.FILE100 TO \bnode.$DATA0B.ZSDABCDEF.FILE100,
\pnode.$DATA03.ZSDABCDEF.FILE100 TO \bnode.$DATA0C.ZSDABCDEF.FILE100
)
Note that the volume names can differ between the primary and backup systems.
Also, the subvolume and filenames on the backup system must be identical to
those on the primary system, and the the subvolume must correspond to the
subvolume you used when you created your schema.
The backup database is now ready for RDF replication activity.
Online Database Synchronization With
NonStop SQL/MX Objects
The principles of protocol for online database synchronization with NonStop SQL/MX
objects are the same as for Enscribe and NonStop SQL/MP objects. That is, you follow
the guidelines for the RDF online database-synchronization protocol. The only
difference is how the fuzzy copy is obtained. The following discussions focus on the
two options for getting the fuzzy copy: creating a fuzzy copy on the primary system or
creating the fuzzy copy on the backup system.
Creating the Fuzzy Copy on the Primary System
The advantage of this method is that in creating and populating the fuzzy copy on the
primary system you achieve better performance than by creating and populating the
fuzzy copy over the network. Once created and populated, you use
BACKUP/RESTORE to move the fuzzy copy to the backup system. The disadvantage
of this method is that it requires disk space on the primary system to store a second
copy of your NonStop SQL/MX database.
To create the fuzzy copy on the primary system, perform the following steps.
1. Create a temporary catalog on your primary system to correspond to your regular
catalog on your primary system whose objects you want RDF to replicate.
CREATE CATALOG <catalog_name> LOCATION <optional_guardian_location>;