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
Zero Lost Transactions (ZLT)
HP NonStop RDF System Management Manual—524388-003
16-11
Old Audit Trail Files
Old Audit Trail Files
When a ZLT takeover operation completes, you should not purge the old audit-trail files
on the remote mirrors connected to the standby system if you believe you can recover
the primary system. The old audit-trail files are necessary for recovering the primary
system.
If you can’t recover the primary system, you may purge the files because they have no
further use.
Because the old audit-trail files are not managed by TMF on the standby system, if you
choose to purge them you must do so manually using Snoop.
Recovering the Primary System After an RDF
ZLT Takeover
If you had to execute the RDF takeover operation and you are able to bring your
former primary system back online, you must perform the following tasks to recover the
database on your former primary system.
1. Determine which disks (the local disk on the primary system or the remote mirror
on the standby system) for all audit trails in the RDF configuration received the
most audit records. The example that follows shows how to do so for the MAT. If
your RDF configuration includes one or more auxiliary audit trails, you must do the
same for each auxiliary audit trail.
On the ZLT standby system, use SNOOP READAUDIT to read the final file in the
MAT, positioning at EOF and reading in reverse order for one record. The
following is sample output from READAUDIT with the MAT position in bold.
* SEQNO = 8, RBA = 107628804, RBN = 26276 *
AC^RECORD^LENGTH=108, AC_VERSION=7, VERSION_FLAGS=000000 000000, PRIMARY^CPU=0
AUDITING^PROCESS=TMP , VSN=000000 000000 000004 077334
TRANSID=000000 000000 000000 000000, ACTTX=0, TYPE=1033 (DATAVOL STATE)
CREATING^SYSTEM=190, VOLNAME=$DATA13, STATE=8, STATE^TEXT=STARTED
On the former primary system, the last file in the MAT may have been left in the
crashopen state. You can determine that by issuing the following command:
$system system 3> fileinfo $*.ztmfat.*
$audit.ztmfat
CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
aa000001 134 125825024 01feb2005 10:15 255,255 gggg 3840 3840
aa000002 134 125829120 01feb2005 10:20 255,255 gggg 3840 3840
aa000003 134 125829120 01feb2005 10:24 255,255 gggg 3840 3840
aa000004 134 125808640 01feb2005 10:31 255,255 gggg 3840 3840
aa000005 134 125829120 01feb2005 10:38 255,255 gggg 3840 3840
aa000006 134 125829120 01feb2005 10:45 255,255 gggg 3840 3840
aa000007 134 125829120 01feb2005 10:54 255,255 gggg 3840 3840
aa000008 134 125829120 01feb2005 11:04 255,255 gggg 3840 3840
aa000009 134 125829120 01feb2005 11:14 255,255 gggg 3840 3840
aa000008 ? 134 107630592 01feb2005 11:04 255,255 gggg 3840 3840