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-13
Overview
Overview
To synchronize selected portions of your database, you follow the same steps as those
for synchronizing an entire database.
Example #1 – Staged Synchronization of an Entire Database
Suppose you are synchronizing your entire database by synchronizing selected
portions first. Suppose your database is on ten volumes and you want to synchronize
two volumes at a time. You would start by synchronizing your first two volumes,
following the guidelines for synchronizing an entire database.
When this operation has completed and the RDF updaters are fully caught up, you
stop the NonStop RDF product. You then delete your current RDF configuration and
initialize a new RDF subsystem, using the SYNCHDBTIME option. For the timestamp
to be used with the SYNCHDBTIME parameter, you specify a timestamp following the
guidelines for the INITTIME option.
When you create your new RDF configuration, include the first two volumes you have
just synchronized and include two new volumes. Regarding the first two volumes that
are already synchronized, you do not need to create and load copies of the files and
tables on those volumes because they are already synchronized. For the two new
volumes, you need to synchronize these following the steps for an entire database
synchronization.
When these two new volumes have been synchronized, you follow the same
procedure discussed above, and adding two new volumes to your new RDF
configuration file.
Example #2 – Synchronization of an Individual Volume
Suppose you just need either to synchronize a new volume to an existing RDF
configuration, or you need to re-synchronize an existing volume in your configuration.
You would first stop your current RDF subsystem. You then delete your current RDF
control subvolume and initialize a new RDF subsystem, using the SYNCHDBTIME
option. For the timestamp to be used with the SYNCHDBTIME parameter, you specify
a timestamp following the guidelines for the INITTIME option.
When you create your new RDF configuration:
•
If you are synchronizing a new volume, add it to your new configuration.
•
If you are resynchronizing an existing volume, then just use your existing RDF
configuration.
You then follow the guideline for an entire database synchronization operation, except
that you only need to create and load copies of the files and tables on the one volume.