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
Online Database Synchronization
HP NonStop RDF System Management Manual—524388-003
7-3
Synchronizing Entire Databases Online
6. When the load operations are done, issue the RDFCOM STOP SYNCH command
on the primary system. This command issues a message to the extractor. The
purpose of this command is to enable RDF to determine when the synchronization
operation has completed and the backup database is synchronized with the
primary database.
When the extractor completes its role in the online synchronization operation, it
generates the RDF Event 782 and then resumes normal operations. For more
detailed information, see “Phases of Online Database Synchronization” later in this
section.
7. If the duplicate tables and files were created on the primary system in step 4, use
BACKUP/RESTORE or FUP DUP operations to copy them to the backup system.
For ENSCRIBE files with alternate key files, after restoring the files to the backup
system, if the name of the alternate key file is in network form, then you must
manually alter the system name of the alternate key file in the file label, replacing
the name of the primary system with that of the backup.
For example, suppose that on the primary system (\PRIMARY) you have a file
named $DATA.TEST.PART0100 with an alternate key file named ALTF0100.
After restoring both files to the backup system (\BACKUP), you must then use a
FUP ALTER command to alter the file label of PART0100 to point to the alternate
key file on the backup system.
FUP ALTER $DATA.TEST.PART0100,
ALTFILE ( 0, \BACKUP.$DATA.TEST.ALTF0100 )
Note that the above command does not pertain to NonStop SQL/MP indexes
because their labels are automatically corrected by the MAP NAMES option of the
RESTORE utility.
The same issue pertains to Enscribe partitioned files. If the primary partition
references secondary partitions that include the primary system name, you must
alter the primary system name to that of the backup system.
If you have an RDF network for replicating network transactions, then you will need
to alter the partition names to reference the correct names of the backup systems
where the partitions are located.