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-2
Synchronizing Entire Databases Online
start updating. When the updaters are caught up, stop RDF and reinitialize RDF using
synchdbtime. Then do the same with the next subset of volumes).
Synchronizing Entire Databases Online
To synchronize an entire RDF backup database to the primary database online, do as
follows.
1. If RDF is currently running, issue a STOP RDF command on the primary system.
2. Purge the RDF control subvolume on both the primary and backup systems and
then issue an INITIALIZE RDF command of the following form on the primary
system:
INITIALIZE RDF, BACKUPSYSTEM \system, SYNCHDBTIME ddmmmyyyy hh:mm
where system is the name of the backup system, ddmmmyyyy is today’s date
(such as 17DEC2004), and hh:mm is an appropriate timestamp prior to the current
time (see the description of the INITIALIZE RDF command in Section 8).
3. Configure RDF and then issue a START RDF, UPDATE OFF command on the
primary system.
4. Make a copy of all tables and files in the database as follows:
Create an empty set of duplicate key-sequenced and relative tables and files
on either the primary or backup system. The duplicate tables and files must
not be audited.
You can create these files and tables on either the primary or backup system,
but you should only create them on the backup system if you have sufficient
Expand bandwidth between the two systems to handle both the audit sent by
the extractor and the data sent by the load operations.
5. Using load commands, populate the empty tables and files.
For NonStop SQL/MP tables, use SQLCI LOAD commands with the SHARE
option.
For Enscribe files, use FUP LOAD commands with the SHARE option.
Note. RDF does not replicate NonStop SQL/MP catalogs. Therefore, if you are
synchronizing NonStop SQL/MP tables, you may need to create NonStop SQL/MP
catalogs manually on the backup system.
Note. If you have multiple RDF environments, be sure to specify an appropriate SUFFIX
parameter in the above INITIALIZE RDF command to keep this RDF configuration
separate from the other RDF configurations on the primary system. Also, if this
configuration is to protect different data from the other RDF configurations, you might want
to consider using the INCLUDE and EXCLUDE options for your updaters.