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
Installing and Configuring RDF
HP NonStop RDF System Management Manual—524388-003
3-16
Initializing RDF
To a TMF Shutdown Timestamp
If TMF was running previously on the primary system and did not need to be initialized
and configured, you can initialize RDF to a timestamp that reflects the time of the last
TMF shutdown.
To issue the INITIALIZE RDF command without first initiating an RDFCOM session,
enter the command in the following format in response to the TACL prompt. In the
TIMESTAMP parameter, be certain to specify the exact time (to the minute) that TMF
was last shut down. You determine the appropriate timestamp by examining previous
TMF messages in the EMS log. In this example, the TIMESTAMP parameter specifies
1:32 p.m., January 7, 1999:
>RDFCOM;INITIALIZE RDF, BACKUPSYSTEM \CHICAGO,
SUFFIX A, TIMESTAMP 7JAN1999 13:32
To issue the INITIALIZE RDF command from within an RDFCOM session, enter the
following in response to the RDFCOM prompt:
]INITIALIZE RDF, BACKUPSYSTEM \CHICAGO, SUFFIX A,
TIMESTAMP 7JAN1999 13:32
If the INITIALIZE RDF commands in this discussion were issued from the primary
system \DALLAS, RDF would respond by creating a configuration file in the control
subvolume named $SYSTEM.DALLASA.CONFIG.
Without a TMF Shutdown Timestamp
If you have just installed (or deleted and reinstalled) TMF so that it starts at relative
byte address (rba) 0 in audit trail file sequence number 1, you should now issue an
INITIALIZE RDF command without the TIMESTAMP parameter at the TACL prompt on
the primary system:
>RDFCOM; INITIALIZE RDF, BACKUPSYSTEM \BOSTON, SUFFIX A
Note that when you begin an RDFCOM session on a system in which RDF has never
been previously initialized (such as \PRIMSYS, for example), RDFCOM responds with
the following prompt:
***Warning*** The control subvolume PRIMSYS is not presently
***Warning*** configured for an RDF primary system.
You must use the OPEN command to open an RDF CONFIG file in
an existing RDF control subvolume, or you must initialize a
new RDF configuration with the INITIALIZE RDF command.
To continue with the session, you must either enter an INITIALIZE RDF command, or
use the OPEN command as directed in Section 8, Entering RDFCOM Commands.