HP NonStop RDF System Management Manual Abstract This manual describes how to install, configure, operate, and manage the HP NonStop™ RDF/IMPX and ZLT Remote Database Facility (RDF) products for HP Integrity NonStop servers. It is intended mainly for system managers and operators, but also contains information for database administrators, system analysts, application designers, and programmers. Product Version NonStop RDF/IMPX 1.7 (T0346 and T0347) NonStop RDF/ZLT 1.
Document History Part Number Product Version Published 529826-002 NonStop RDF/IMPX 1.6 (T0346 and T0347) NonStop RDF/ZLT 1.6 (T0618) July 2005 529826-003 NonStop RDF/IMPX 1.7 (T0346 and T0347) NonStop RDF/ZLT 1.
HP NonStop RDF System Management Manual Index Figures What’s New in This Manual xiii Manual Information xiii New and Changed Information Tables xiv About This Manual xvii Who Should Read This Manual xvii Where to Find Information You Need xviii Related Reading xix Notation Conventions xxi 1.
2.
4.
5. Managing RDF Contents Performing Routine Operational Tasks 4-18 Displaying Current Configuration Parameters and Operating Statistics Changing Configuration Parameters 4-23 Reading Log Messages 4-24 5.
6. Maintaining the Databases Contents RDF and NonStop SQL/MP DDL Operations 5-30 Performing Non-Shared Access DDL Operations 5-30 Performing Shared Access DDL Operations 5-31 RDF and NonStop SQL/MX Operations 5-32 Backing Up Image Trail Files 5-32 Making Online Dumps With Updaters Running 5-33 Doing FUP RELOAD Operations With Updaters Running 5-34 Exception File Optimization 5-35 Switching Disks on Updater UPDATEVOLUMES 5-36 6.
. Entering RDFCOM Commands Contents 8. Entering RDFCOM Commands Command Description Elements 8-1 Purpose, Syntax, and Parameters 8-1 Where Issued 8-2 Security Restrictions 8-2 RDF State Requirement 8-2 Usage Guidelines 8-2 Output Displayed 8-5 Examples 8-5 File Names and Process Identifiers 8-5 Reserved File Names 8-5 Disk File Names 8-6 Nondisk Device Names 8-7 Process File Names 8-8 Command Overview 8-8 9.
11. Subvolume- and File-Level Replication Contents Using ZLT to Achieve Triple Contingency Protection for Auxiliary Audit Trails Triple Contingency Without ZLT 10-7 Using ZLT to Achieve the Same Protection 10-8 Summary 10-8 11. Subvolume- and File-Level Replication INCLUDE Clauses 11-1 EXCLUDE Clauses 11-2 Wildcard Character (*) 11-2 Within Subvolume Names 11-2 Within Filenames 11-2 INCLUDE and EXCLUDE Processing Error Checking 11-3 Performance Ramifications 11-3 Summary Examples 11-4 11-3 12.
14.
15. NonStop SQL/MX and RDF Contents Reenabling Lockstep 14-7 Lockstep Performance Ramifications 14-8 Lockstep and Auxiliary Audit Trails 14-8 Lockstep and Network Transactions 14-8 Lockstep Operation Event Messages 14-8 15.
A.
D. Operational Limits Contents D. Operational Limits E. Using ASAP Architectural Overview E-1 Installation E-2 Auto Discovery E-2 Monitoring Specific RDF Environments E-3 Adding and Removing RDF Environments E-3 Version Compatibility E-3 RDF Metrics Reported by ASAP E-4 Index Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 1-6. Figure 1-7. Figure 1-8. Figure 6-1. Figure 6-2. Figure 6-3. Figure 6-4. Figure 6-5. Figure 16-1. Figure 16-2. Figure 16-3. Figure E-1.
Tables Contents Tables Table 1-1. Table 2-1. Table 2-2. Table 3-1. Table 4-1. Table 4-2. Table 4-3. Table 4-4. Table 5-1. Table 5-2. Table 5-3. Table 8-1. Table 8-2. Table 9-1. Table D-1. Table E-1.
What’s New in This Manual Manual Information HP NonStop RDF System Management Manual Abstract This manual describes how to install, configure, operate, and manage the HP NonStop™ RDF/IMPX and ZLT Remote Database Facility (RDF) products for HP Integrity NonStop servers. It is intended mainly for system managers and operators, but also contains information for database administrators, system analysts, application designers, and programmers. Product Version NonStop RDF/IMPX 1.
What’s New in This Manual New and Changed Information New and Changed Information This manual replaces the HP NonStop RDF System Management Manual (part number 529826-002), making that manual obsolete. Change bars in the margin identify all differences between this manual and the one it replaces.
What’s New in This Manual • • • • • • • Added File Recovery on the Primary System and File Recovery on the Backup System. Added STOP RDF, DRAIN Operations to “Stopping RDF From the Primary System.” Added Switching Disks on Updater UPDATEVOLUMES. Section 7, Online Database Synchronization: Updated Enscribe Queue File Issues. Section 8, Entering RDFCOM Commands: • • • • • • • • • • • • New and Changed Information • Added the TRIGGER parameter to the ADD command (page 8-9).
What’s New in This Manual • Appendix A, RDF Command Summary: • • • • • • • • • • • New and Changed Information • Added the TRIGGER parameter to the ADD command (page A-2). Added the TRIGGER parameter to the ALTER command (page A-2). Added the TRIGGER parameter to the DELETE command (page A-3). Added the TRIGGER parameter to the INFO command (page A-5). Added the NOW clause to the INITTIME parameter of the INITIALIZE RDF command (page A-5). Added the TRIGGER parameter to the RESET command (page A-6).
About This Manual Note that the content of this manual is identical to the content of the manual that supports the RDF 1.7 independent product (manual part number 524388-003). The Remote Database Facility (RDF) subsystem enables HP NonStop Series users at a local (primary) system to maintain a current, online copy of their database on one or more remote (backup) systems, protecting stored information from damage that might occur at the primary system.
Where to Find Information You Need About This Manual Where to Find Information You Need This manual presents three levels of information: introductory and conceptual information (Section 1), task-oriented guidelines (Sections 2 through 7, and 10 through 14), and reference information (Sections 8 and 9 and Appendixes A, B, and C).
Related Reading About This Manual • • • • • • • • • • Section 12 describes support for auxiliary audit trails. Section 13 describes support for network transactions. Section 14 describes lockstep operation. Section 15 describes SQL/MX database setup for RDF. Section 16 describes the Zero Lost Transactions (ZLT) functional capability. Appendix A summarizes the syntax of all RDFCOM and RDFSCAN commands.
Related Reading About This Manual Manuals for other software products that contain information helpful to RDF users include: • • • • • • • HP NonStop SQL Installation and Management Guide, which explains how to install the NonStop SQL relational database management system; and how to plan, create, and manage NonStop SQL databases and applications using the NonStop SQL product for database protection.
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
General Syntax Notation About This Manual … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
Notation for Messages About This Manual Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets.
Notation for Messages About This Manual HP NonStop RDF System Management Manual—529826-003 xxiv
1 Introducing RDF This manual describes the Remote Database Facility (RDF) subsystem as implemented in version 1, update 7 of the HP NonStop RDF/IMP, IMPX, and ZLT independent products. Customers who install RDF 1.7 can use existing RDF configuration scripts provided the scripts are not making use of new functionality.
RDF Subsystem Overview Introducing RDF There are three versions of the RDF product: 1. RDF/IMP (product number T0346) provides online product initialization, online database synchronization, triple contingency support, subvolume- and file-level replication, stop-update-to-time (for quiescing the backup database to a stable state), NonStop SQL/MP big files support, and many other features. 2.
RDF Subsystem Overview Introducing RDF Each volume protected by RDF on the primary system has its own updater process on the backup system responsible for applying audit information to the corresponding volume on the backup system. Figure 1-1 illustrates a basic RDF configuration that protects data volumes configured to a Master Audit Trail (MAT) and an auxiliary audit trail. Figure 1-1.
Unplanned Outages With ZLT Introducing RDF information associated with volumes $D11 through $D15 to the RDF auxiliary receiver process on the backup system. The master receiver writes transaction status information to the master image trail. Note that in this example each receiver process writes all audit information to a single secondary image trail. As will be discussed later, however, either could write to multiple sorted image trails.
Unplanned Outages Without ZLT Introducing RDF Unplanned Outages Without ZLT Without ZLT functionality, it is possible for some committed transactions to be lost during an unplanned outage. When the RDF TAKEOVER command is issued, any transaction whose final outcome is unknown on the backup system is backed out of the backup database.
Introducing RDF Tips for Executing Fast Business Takeover Operations Tips for Executing Fast Business Takeover Operations Take online dumps of your backup database as frequently as you take them on your primary system. In this way, when you need to takeover on your backup system, you will already have dumps available. Remember, if the RDF UPDATEROPEN attribute is set to PROTECTED, you must stop the updaters and set it to SHARED before taking online dumps of your backup database.
Planned Outages Introducing RDF When the program detects a successful RDF Takeover, it can then route requestor work to the servers on the backup system, and those servers are then ready to resume business on the backup system. An alternative, and preferred, approach is to configure a takeover trigger to send a message to the requester routing program. Of course, what makes this method work is ensuring that no work is ever routed to the backup system until the takeover has completed.
Features Introducing RDF • Flexibility in protection You can run RDF with updating on the backup system either enabled or disabled. RDF is also very flexible with regard to system interrelationships and to disk usage requirements on backup systems. Besides the most basic configuration of a single primary system protected by a single backup system, you can have configurations such as the following (see Figure 1-2, RDF Topologies): • • • • • Multiple primary systems protected by one backup system.
Features Introducing RDF Figure 1-2.
Features Introducing RDF • Master and auxiliary audit trail protection RDF can protect all tables and files that are being audited by TMF, whether they are associated with the master audit trail (MAT) or an auxiliary audit trail. • Subvolume and file replication In addition to volume replication, the RDF/IMP and IMPX products support replication of selected subvolumes and files. • Economical processing RDF conserves resources at both sites.
User Interfaces Introducing RDF User Interfaces To use RDF, you run two online utilities: RDFCOM and RDFSCAN. Both are interactive command interpreters through which you begin a session and enter requests to the subsystem. RDFCOM for Subsystem Management and Operations To manage, operate, and control RDF, use the RDFCOM utility.
Tasks Introducing RDF Using RDFSCAN commands, you can specify: • • • A starting point for scanning the intermediate RDF message file How many records to scan Text to search for in the file Tasks and examples for using RDFSCAN commands appear throughout the manual. Reference information for all commands appears in Section 9, Entering RDFSCAN Commands.
Tasks Introducing RDF Figure 1-3. RDF Tasks to Maintain a Copy of a Database Captures audit trail records. Extractor Filters and transmits audit trail data to backup system. Receives and writes audit trail data to image file. Receiver Reads image file and issues REDO request to disk process, supplying image records for REDO operation. Updater Disk process performs requested REDO operation, updating the backup database.
Introducing RDF RDF Processes RDF Processes To accomplish its four major tasks, RDF runs different processes on the primary system and the backup system. These processes (the monitor and extractor on the primary system and the receiver, updaters, and purger on the backup system) divide these tasks as summarized in the following pages. The relationship of these processes to one another is illustrated in Figure 1-4. More details about their operation appear under RDF Operations. Figure 1-4.
Introducing RDF Primary System Processes Primary System Processes On the primary system: • • The monitor process coordinates subsystem starts and stops, some messages, and NonStop SQL/MP and NonStop SQL/MX DDL operations using the WITH SHARED ACCESS option on protected volumes, and monitors the other RDF processes.
Introducing RDF Monitor Process Updating can be explicitly enabled or disabled through RDFCOM commands, as described later in this manual. If takeover performance is critical, you should run RDF with updating enabled. If updating is disabled, it is possible for the image trails to fill up; also, it may take significant time for the updaters to apply all audit information when a takeover operation is started. The monitor, extractor, receiver, RDFNET, updater, and purger processes run as process pairs.
Introducing RDF Extractor Process Figure 1-5. Extractor Process Operation Master Audit Trail (MAT) Primary Disk Mirror Disk Audit File Audit File 56 KB Read 56 KB Read Extractor (incl.
Introducing RDF Extractor Process physical audit records generated either for block splits or during FUP RELOAD operations. The extractor always tries to fill the buffer to be sent to the receiver. The buffer never contains partial records; if the buffer is nearly full and the next record to be transmitted does not fit in its entirety, the extractor transmits the current buffer and puts the record at the beginning of the next buffer.
Introducing RDF Receiver Process by the extractor, you will have to reinitialize RDF and resynchronize the primary and backup databases. In response to the UNPINAUDIT command, RDFCOM issues a prompt asking you to confirm your request. If the files are unpinned successfully, RDFCOM issues an informational message to that effect. If an error occurs while attempting to unpin the audit trail files, the command is ignored, and RDFCOM issues a message indicating the error.
Introducing RDF Receiver Process Figure 1-6.
Introducing RDF RDFNET Process With sorted image trails, the activity of any one image file typically remains so low that it can be stored on the same disk volumes as the main database with no significant I/O impact. This approach is not recommended, however, if you require very high RDF performance or if RDF is running with the UPDATE option turned off; in this case, the image trails could eventually fill the volume; in such cases, it is best to have volumes exclusively dedicated to the image trails.
Introducing RDF • • Updater Processes Bundles the REDO and UNDO requests into batch TMF transactions, the duration of which is specified by the UPDATERTXTIME configuration parameter.
Introducing RDF Updater Processes Audited Database Files All database files on the backup system are audited files. Each updater maintains a file status table to keep track of the files it has open. An updater closes any database file that has not been updated recently. Updaters also close database files when a STOP RDF or STOP UPDATE command is issued, or when the updater restarts because of error conditions. An updater process can have up to 500 files open simultaneously.
Introducing RDF Updater Processes NonStop SQL/MP and NonStop SQL/MX indexes are updated independently as a consequence of the individual audit records generated on the primary system by TMF software. Note. You must be sure that volumes on the primary system containing alternate key files and indexes are protected by RDF. It is not sufficient to protect just the associated data file or table (particularly in the case of alternate keys).
Introducing RDF Purger Process Purger Process The updaters apply all audit records to their data volumes regardless of whether the associated transaction has committed, has aborted, or is still in progress. The purging of redundant image trail files is based on transaction information. Specifically, the receiver process maintains general information on what transactions might be in each image file. This information is system-wide, not specific to any particular image trail.
Introducing RDF Reciprocal and Chain Replication Although all the updater restart locations are in AA000015, none of the image files from AA000002 through AA000014 can be purged while T1000 is active or aborting because they will be required if T1000 needs to be backed out during an RDF takeover or stop-update-to-timestamp operation. Note that this is true for both trails, even though none of the updaters on one trail have ever been involved with T1000.
Introducing RDF Reciprocal and Chain Replication Consider the following example. Assume that Primary DB 1 and Backup DB 2 are both located on $DATA on \A, and assume that Primary DB 2 and Backup DB 1 are also located on $DATA on \B. Using the reciprocal example, suppose your application does an update on \A to Primary DB 1. The extractor of RDF Subsystem 1 sees that the update was for $DATA and sends that update to \B where the updater applies that update to Backup DB 1.
Introducing RDF Available Types of Replication to Multiple Backup Systems Alternatively, if your two databases must share the same disks, then you must explicitly specify which files and tables you want replicated by each RDF subsystem. For erxample, RDF Subsystem 1 would INCLUDE only Primary DB 1, and RDF Subsystem 2 would INCLUDE only Primary DB 2.
Introducing RDF RDF Control Subvolume RDF Control Subvolume The INITIALIZE RDF command includes a control subvolume suffix parameter (SUFFIX char ), where char is an alphanumeric character. If you include this parameter, the RDF control subvolume on $SYSTEM will be the local (primary) system name without the backslash and with the specified character appended to it. If you omit this parameter, the RDF control subvolume on $SYSTEM will merely be the local system name without the backslash.
Introducing RDF Triple Contingency The following discussion assumes you do not have ZLT functionality. For triple contingency with ZLT, see Section 10, Triple Contingency. The triple contingency feature builds upon the ability to replicate to multiple backup systems.
Introducing RDF Loopback Configuration (Single System) systems are likely to be, depending on the image file rollover rate expected at your site. (RETAINCOUNT should always be the same value on both backup systems.) To achieve this type of protection, it is imperative that you carefully follow the instructions presented in Section 10, Triple Contingency. Loopback Configuration (Single System) A loopback configuration is one where the primary and backup systems are the same system.
Introducing RDF Subvolume- and File-Level Replication Subvolume- and File-Level Replication By default, RDF provides volume-level protection, wherein changes to all audited files and tables on each protected primary-system data volume are replicated to an associated backup-system data volume. RDF/IMP, IMPX, and ZLT also support subvolume-level and file-level replication.
Introducing RDF RTD Warning Thresholds RTD Warning Thresholds RDF/IMP, IMPX, and ZLT allow you to designate a pair of RTD warning thresholds: one for the extractor, and another for all of the updaters. Having set those thresholds, you then can issue a STATUS RTDWARNING command with a designated repeat interval to display information and statistics for only those processes (the extractor or any updater) that have fallen behind the configured RTD threshold.
Introducing RDF Zero Lost Transactions (ZLT) Zero Lost Transactions (ZLT) Zero Lost Transactions (ZLT), which is available only with the RDF/ZLT product, is a functional capability that uses mirrored disks to guarantee that no committed transactions on the primary system will be lost in the event of an RDF takeover by the backup system. For information about this capability, see Section 16, Zero Lost Transactions (ZLT).
2 Preparing the RDF Environment Before RDF can be run on an HP NonStop system, the system configurations and user applications must meet certain RDF requirements. This section explains how to prepare each system for RDF installation and operation, ensuring that all these requirements are met and that you understand the RDF product’s restrictions.
Preparing the RDF Environment Disk Volume Limit is identical to that of the primary system, your system personnel can adjust more quickly to the backup environment during disaster recovery. If you cannot configure the backup system as an identical copy of the primary system, plan the configuration of the backup system with enough processing power and disk drives to enable RDF to keep the backup database current with the primary database.
Preparing the RDF Environment Data Communication (Expand) Resources Data Communication (Expand) Resources RDF sends filtered audit data from the primary system over the network to the backup system. A communications path between the systems can be any form of Expand linkage.
Preparing the RDF Environment Data Communication (Expand) Resources 3. If all the TMF audit data is generated on volumes protected by RDF, subtract the first EOF value from the second EOF value to obtain the number of bytes generated during the 5-minute period.
Preparing the RDF Environment Preparing Software and Database Files for RDF Operations Preparing Software and Database Files for RDF Operations The software requirements for the RDF/IMP, IMPX, and ZLT products appear in Table 2-2. Table 2-2. Software Requirements Software Requirement Files The RDF/IMP, IMPX, and ZLT products protect only files on the primary system that are audited by the TMF subsystem.
Preparing the RDF Environment Configuring TMF for RDF Operations Configuring TMF for RDF Operations TMF attempts to purge old audit trail files each time it rolls over to a new one. The purge is performed only if the audit trail file is not pinned on behalf of RDF. RDF automatically pins audit trail files. The only ways TMF can purge an old audit trail file that is still required by RDF are as follows: 1. If you issue an UNPINAUDIT command while RDF is not running. 2.
Preparing the RDF Environment Preparing Databases for RDF Protection TMF Configuration Without Dump Process Long ago, the RDF product required that you configure TMF with a dump process that dumps to tape. RDF no longer imposes this requirement on either the primary or backup systems for the following reasons: 1. On the primary system, the RDF extractor explicitly pins the audit trail it is currently processing, thereby preventing TMF from purging it.
Preparing the RDF Environment Preparing Databases for RDF Protection system corresponds to volume $A on the primary system, then all files protected by RDF on volume $A must be present (and in the same subvolumes) on $B. Section 3 explains how to copy NonStop SQL/MP databases and Enscribe files to the backup system after stopping both the TMF product and the applications that use that product on the primary system.
Preparing the RDF Environment Specifying System Generation Parameters for an RDF Environment Views on the Backup System If an application uses any NonStop SQL/MP or NonStop SQL/MX shorthand or protection views on a volume protected by RDF, audit data for transactions on the views refers only to the underlying tables and not to the views. Views and their underlying base tables must be present on the backup system after a takeover operation so that applications can continue without interruption.
Preparing the RDF Environment Designing Transactions for RDF Protection Replicating Database Operations Database administrators preparing to work with RDF should be aware of considerations concerning: • • • • • • NonStop SQL/MP and NonStop SQL/MX Data Definition Language (DDL) operations NonStop SQL/MP and NonStop SQL/MX DDL operations with Shared Access Enscribe file-label modifications Purge operations Partitioned files Temporary disk files NonStop SQL/MP and NonStop SQL/MX DDL Operations Although RD
Preparing the RDF Environment Designing Transactions for RDF Protection The only file-label modifications that RDF replicates are the following: CREATE To create an audited Enscribe file ALTER MAXEXTENTS To increase the number of extents for an audited Enscribe file PURGEDATA To purge data from an audited Enscribe file PURGE To purge an Enscribe file (if REPLICATEPURGE is enabled) Purge Operations The two kinds of purge operations are PURGEDATA and PURGE.
Preparing the RDF Environment Using SMF With RDF Using SMF With RDF RDF supports the full use of SMF on both the primary and backup nodes. There are two basic ways to configure SMF logical volumes: • Map many physical disks to a single virtual disk Create SMF pools where each is comprised of many physical volumes and create SMF virtual disks from these pools.
Preparing the RDF Environment • Configuring an SMF Environment on the Backup RDF System Place the SMF catalog in the default SMF catalog subvolume on a volume that is protected by RDF. The extractor automatically filters out changes to the SMF catalog if the catalog is in the default SMF catalog subvolume.
Preparing the RDF Environment Configuring an SMF Environment on the Backup RDF System You can change the physical volume on which files reside in the SMF pool using the FUP RELOCATE command. This command only works on closed files, so the updaters must be stopped before relocating any files. SMF allows physical disks to be added and removed from pools. The RDF updaters must be stopped prior to the addition or deletion of any physical disks from SMF pools on the backup system.
3 Installing and Configuring RDF After preparing your system configurations and user applications to meet RDF requirements, you are ready to install and configure RDF. This section, which is intended for system managers, system analysts, and database administrators, describes how to do these tasks.
Installing and Configuring RDF Stopping the Software 2. Prepare your NonStop SQL/MP tables and Enscribe files for RDF protection as follows: a. Separate the tables to be protected by RDF from the tables not to be protected. (This step is recommended but not required.) b. Set audit compression (the AUDITCOMPRESS file attribute) on for all tables and files to be protected by RDF. Note that audit compression on is the creation default for NonStop SQL/MP tables and indexes.
Installing and Configuring RDF Preparing the Backup System To set the AUDITCOMPRESS attribute for an Enscribe file, use the File Utility Program (FUP) to enter an ALTER command: FUP ALTER filename, AUDITCOMPRESS Preparing the Backup System Before starting RDF, you need to copy every database, program, and file that the primary system applications use to the backup system so that the backup system can take over in the event of a primary system failure.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases The backup system should also have copies of the following files in case an RDF takeover operation is necessary: • • OBEY command files and TACL scripts containing NonStop SQL/MP or NonStop SQL/MX DDL commands that define the database SQLCI or MXCI report definitions To make it easy to compare catalogs on the primary and backup systems, it is strongly recommended that you register objects protected by RDF in separate catalogs
Installing and Configuring RDF Synchronizing the Primary and Backup Databases Backing up partitioned files requires some extra planning, as explained in Synchronizing Partitioned Files later in this section. For a complete discussion of synchronized versus unsynchronized databases and their ramifications, see Understanding Database States in section 6.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases then duplicate this table on the backup system by using the SQLCI DUP command. In this example, \PRIM is the primary system and \BACK is the backup system. Notice that the catalog for this NonStop SQL/MP table is created on the backup system before starting RDF on the primary system so that RDF will recognize the backup catalog and not report errors when attempting to process audit data for this catalog. 1.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases 7. Enter commands to specify the data to be inserted into the table on the primary system: INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME ) VALUES ( 826, "Evans", "Joan" ); INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME ) VALUES ( 3351, "MacArthur", "Bill" ); INSERT INTO =EMPLOYEE ( EMPNUM, FIRST_NAME, LAST_NAME ) VALUES ( 10809, "Gember", "Tom" ); Now direct your attention to the backup system (\BACK).
Installing and Configuring RDF Synchronizing the Primary and Backup Databases 1. Back up the database from \PRIM onto tape: BACKUP $TAPE, (*.*.* FROM CATALOG \PRIM.$TEST.DBCAT), AUDITED, INDEXES IMPLICIT, LISTALL 2. Restore the database from tape onto \BACK (assuming the catalog was already created): RESTORE $TAPE, *.*.*, AUDITED, MAP NAMES ( \PRIM.$DATA1.*.* TO \BACK.$DATA1.*.* , \PRIM.$DATA2.*.* TO \BACK.$DATA2.*.* ), CATALOG \BACK.$DATA1.
Installing and Configuring RDF Backing Up Application Programs and Files For an Enscribe file, you can use the FUP DUP command or the BACKUP and RESTORE utilities to copy the individual indexes and partitions. Then use FUP ALTER to incorporate the other partitions and any alternate indexes into the primary partition. If the volume names for partitions on the backup system are different from the volume names on the primary system, you need to change the volume references for those partitions.
Installing and Configuring RDF RDF/IMPX (T0347) Product Components RDFCOM The RDF command interface object code file RDFHELP The RDFCOM HELP file (an EDIT file) RDFEXTO The RDF extractor object code file RDFINST The RDFINST TACL macro (an EDIT file) RDFMONO The RDF monitor object code file RDFNETO The RDFNET object code file RDFRCVO The RDF receiver object code file RDFPRGO The RDF purger object code file RDFSCAN The RDFSCAN object code file RDFSCANH The RDFSCAN HELP file (an EDIT file)
Installing and Configuring RDF Process-Lockstep Gateway (T1226) Product Components Process-Lockstep Gateway (T1226) Product Components The release CD includes the following files associated with the process-lockstep capability: SLOCKCOB Sample code for invoking the DoLockstep procedure from a COBOL 85 program. LSGO RDF lockstep gateway object code. LSLIBTO DoLockstep procedure object code. FDOLOCK Forward declarations of the DoLockstep procedure call.
Installing and Configuring RDF Security Guidelines Table 3-1.
Installing and Configuring RDF • • • • • • • • Using the OWNER Attribute to Allow Super Group Users to Start, Stop, and Manage RDF RDFMONO. The RDF monitor program communicates with the TMP in privileged mode and must be licensed with FUP or by running the RDFINST macro. RDFMONO can be owned by any user ID. RDFNETO. The RDFNETO program opens and writes to the network synchronization file on each of the primary systems participating in the RDF network. RDFNETO can be owned by any user ID. RDFPRGO.
Installing and Configuring RDF Initializing and Configuring TMF Initializing and Configuring TMF After copying the appropriate files from the primary system to the backup system, you must ensure that TMF is configured on both systems to support RDF operations. The actions you take to do this depend on whether or not TMF was running previously on this system.
Installing and Configuring RDF Initializing and Configuring RDF Initializing and Configuring RDF After initializing and configuring TMF, you are ready to initialize and configure RDF. Initializing RDF To initialize RDF, you issue an INITIALIZE RDF command at the primary system.
Installing and Configuring RDF 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.
Installing and Configuring RDF Initializing RDF Without Stopping TMF Initializing RDF Without Stopping TMF The INITIALIZE RDF command includes a parameter, INITTIME inittime , that you can use to initialize the RDF product without stopping TMF or your applications. There are two cases where you would use this capability: 1. If you want to install a new version of the RDF product and you cannot afford to stop TMF even momentarily to get a TMF shutdown timestamp. 2.
Installing and Configuring RDF Initializing RDF Without Stopping TMF Enscribe Create Records If the previous version of RDF performed an Enscribe create operation on the backup system prior to execution of the INITIALIZE RDF command and the extractor’s restart position in the MAT precedes the associated Enscribe create record in the MAT, the updater processing that record will report a File System error 10 (File Already Exists) and you must purge the existing file.
Installing and Configuring RDF Online Installation and Initialization Without Stopping RDF Online Installation and Initialization Without Stopping RDF For the procedure described under Initializing RDF Without Stopping TMF, you are required to stop RDF, delete the control subvolumes, reinitialize RDF, and then restart RDF.
Installing and Configuring RDF Online Installation and Initialization Without Stopping RDF 6. Install the new RDF software in a different volume.subvolume from that housing the current version of RDF that is running. For example, if you are upgrading to T0346AAV, you might specify $system.rdfaav. 7. Run $system.rdfaav.RDFCOM and initialize a new RDF configuration, using • • the suffix parameter (such as suffix "a") the INITTIME parameter, using the timestamp calculated in Step 4 above (11JUN2004 13:28).
Installing and Configuring RDF Configuring RDF Considerations This method does not work with long-running transactions. You must not have any long-running transactions in the system when you start step 1, above. If you have long-running transactions, you must stop them and wait until they clear the TMF subsystem before you start Step 1. If you are running with RDF process lockstep, you should change the RDF gateway startup script to reference the new extractor name before executing Step 11.
Installing and Configuring RDF Configuring RDF After issuing the ADD commands (but before starting RDF), you can change some parameter values in the configuration file by issuing ALTER commands. Note. Instead of issuing SET and ADD commands interactively within an RDFCOM session, you can create and execute an RDF configuration command file. The first time you configure RDF, you can either configure it interactively or use the text editor to create a command file.
Installing and Configuring RDF Configuring RDF LOGFILE Parameter The LOGFILE parameter specifies the name of the EMS collector to which all RDF command, event, error, and warning messages are to be directed. The following commands specify the EMS collector $CTD25 as the RDF log file on both the primary and backup systems: ]SET RDF LOGFILE $CTD25 ]ADD RDF The collector on the primary system receives log messages from the extractor and monitor processes (plus RDFCOM messages that are logged in message 835).
Installing and Configuring RDF Configuring RDF UPDATERRTDWARNING Parameter The UPDATERRTDWARNING parameter specifies the RTD warning threshold (in seconds, 0 or greater) for all configured updaters. The default is 60 seconds. This threshold is used by the STATUS RTDWARNING command to determine which updaters, if any, are to be included in its display. The display includes the monitor process and only those RDF processes (extractor or updaters) whose RTD exceeds their configured RTD warning threshold.
Installing and Configuring RDF Configuring RDF UPDATEREXCEPTION Parameter The UPDATEREXCEPTION parameter specifies the manner in which exception files are used. When set to ON (the default value), the updaters log an exception record for each and every audit record they must undo during a takeover. When set to OFF, the updaters log exception records only for the first and last audit records that must be undone (the minimum logging necessary to support Triple Contingency operation).
Installing and Configuring RDF Configuring RDF OWNER Parameter The OWNER parameter specifies a userid under which all RDF processes will always run. This global configuration parameter provides functionality whereby any superuser group userid can start and stop RDF. To illustrate this functionality, imagine ten users are responsible for managing a particular RDF configuration and that SUPER.RDF is configured as the OWNER. Instead of providing all ten users access to the SUPER.
Installing and Configuring RDF Configuring RDF Each secondary image trail contains the audit records needed by the associated updater processes. Image trail files in secondary image trails have the same extent sizes as image trail files on the volume specified by RDFVOLUME. Note. To have secondary image trails, you must add them after initialization and before RDF has been started for the first time.
Installing and Configuring RDF Configuring RDF WAIT causes RDF to wait for the trigger process to terminate before shutting down. NOWAIT specifies that once the trigger process is launched, RDF can immediately proceed to shut down.
Installing and Configuring RDF Configuring RDF BACKUPSYSTEM Parameter The BACKUPSYSTEM parameter specifies the name of the backup system associated with the specified primary system. There is no default value. REMOTECONTROLSUBVOL Parameter The REMOTECONTROLSUBVOL parameter specifies the name of the control subvolume used by the RDF subsystem configured for the specified primary and backup systems. There is no default value.
Installing and Configuring RDF Configuring RDF Monitor Process Use SET MONITOR and ADD MONITOR commands to configure the following monitor parameters: • • • CPUS primary-CPU : backup-CPU PRIORITY PROCESS The CPUS parameter in the following form specifies the primary and backup processors in which the monitor will run: CPUS primary-CPU:backup-CPU If the primary processor is not available when RDF is started, the monitor executes in the specified backup processor without benefit of a backup process.
Installing and Configuring RDF • • Configuring RDF RTDWARNING VOLUME The ATINDEX parameter specifies an integer value from 0 through 15 specifying the TMF audit trail on the primary system with which the extractor is associated. 0 specifies the MAT. 1 through 15 specify auxiliary audit trails AUX01 through AUX15. The default is 0. If you omit this parameter, RDFCOM assumes the extractor is associated with the MAT.
Installing and Configuring RDF Configuring RDF Receiver Process Use SET RECEIVER and ADD RECEIVER commands to configure the following receiver parameters: • • • • • • • ATINDEX CPUS primary-CPU : backup-CPU EXTENTS PRIORITY PROCESS RDFVOLUME SLOWMODE The ATINDEX parameter specifies an integer value identifying a configured TMF audit trail on the primary system. 0 specifies the MAT. 1 through 15 specify auxiliary audit trails AUX01 through AUX15. The default is 0.
Installing and Configuring RDF Configuring RDF The default is SLOWMODE off. For a complete discussion of SLOWMODE, see the description of the SET RECEIVER command in section 8.
Installing and Configuring RDF Configuring RDF The PURGETIME parameter specifies the number of minutes the purger process waits between attempts to purge redundant image trail files. The default value is 60.
Installing and Configuring RDF Configuring RDF trail with the ADD IMAGETRAIL command. Also, the ATINDEX of this updater must match the ATINDEX of the associated image trail. The PRIORITY parameter specifies the priority at which the updater will run. You should set the updater’s priority higher than that of any application’s process but less than the priority of the RDF receiver process. The PROCESS parameter supplies a name for the updater process. You should specify a meaningful mnemonic such as $UP01.
Installing and Configuring RDF Creating a Configuration Command File You can issue ADD VOLUME commands only when RDF is stopped. You must configure all updaters to use secondary image trails, thereby leaving the RDFVOLUME (master image trail) exclusively for use by the master receiver (at index 0). Creating a Configuration Command File You can use the INFO * command with the OBEYFORM parameter to create a configuration command file quickly and easily from an existing RDF configuration: 1.
Installing and Configuring RDF Enabling RDF Operations If RDFCOM cannot determine the configuration file version, it prints the following message to the home terminal and aborts the command: RDFCOM version (version) does not match the config file version If that happens, you should make sure you are using the correct RDFCOM. If you are using the correct version and you get this message, then you must reinitialize RDF.
Installing and Configuring RDF • • Restarting the Applications The RDF configuration file contains all necessary parameters. All updater volumes on the backup system are enabled for transaction processing. When RDF starts execution, it automatically performs a validation check on the configuration file; if the check succeeds, RDF copies the configuration file $SYSTEM.control-subvolume.CONFIG to the backup system.
4 Operating and Monitoring RDF To operate and monitor RDF, you enter commands through two online utilities: the RDFCOM and RDFSCAN interactive command interpreters. Through these utilities, you initiate communication with RDF, request various RDF operations or information displays, and terminate communication with the subsystem.
Operating and Monitoring RDF Command Syntax for Starting an RDFCOM Session Command Syntax for Starting an RDFCOM Session To enter an RDFCOM session, use the following general command syntax. The specific parameters you enter depend, of course, on the options you desire. RDFCOM [/[IN command-file ] [,OUT output-file ]/ ] [control-subvolume] ; [command [; command ]... ] RDFCOM is an implicit RUN command, instructing the TACL command interpreter to run the RDFCOM utility program.
Operating and Monitoring RDF Using RDFCOM Interactively If you omit control-subvolume, RDFCOM assumes that the control subvolume name is the same as the name of the local system on which RDFCOM is running (without the backslash and with no suffix character appended to it). command is one or more RDFCOM commands; multiple commands are separated by semicolons (;). If commands are present, RDFCOM executes them and then terminates without reading the file specified in the IN option.
Operating and Monitoring RDF Using RDFCOM Interactively When it begins your interactive session, RDFCOM displays its product banner followed by the RDFCOM prompt: RDFCOM - T0346A07 - 05JUL05 (C)2005 Hewlett-Packard Development Company, L.P. ] The right-bracket (]) prompt indicates that RDFCOM is ready to accept your first command. When you enter this command, RDFCOM processes it and then displays another right-bracket prompt for your next command.
Operating and Monitoring RDF • • Using RDFCOM Noninteractively If you press BREAK when an RDFCOM command that displays information (such as STATUS RDF) is in progress, RDFCOM terminates execution of this command and prompts you for another one. If you press BREAK when an RDFCOM command that changes the RDF configuration or status (such as ALTER RDF) is in progress, RDFCOM continues to execute this command while immediately prompting you for another one. Note.
Operating and Monitoring RDF Using RDFCOM From a Command File Using RDFCOM From a Command File RDFCOM can also read commands from a command file. The command file is a text file that contains the RDFCOM commands you want to execute, which you prepare using your standard text editor. You might, for example, create a command file named RDFSET that contains the following commands: SET SET SET SET SET SET SET SET SET ADD RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF SOFTWARELOC $SYSTEM.
Operating and Monitoring RDF Using RDFCOM Commands If you decide later that you want to use different installation parameters, you can change the command file and then enter the OBEY command again. Using command files makes performing repeated tasks very convenient. During processing of an OBEY command, when RDFCOM reaches the end of the command file, RDFCOM prompts you for another RDFCOM command.
Operating and Monitoring RDF Using RDFCOM Commands Table 4-1. RDFCOM Configuration Commands Command Object ADD { { { { { { { { { { RDF MONITOR EXTRACTOR RECEIVER IMAGETRAIL PURGER RDFNET NETWORK TRIGGER VOLUME } } } } } } } } } } Applies option values from the configuration memory table to the RDF configuration file for the specified process, or adds RDF and image trail configuration records to the RDF configuration file.
Operating and Monitoring RDF Using RDFCOM Commands Table 4-1. RDFCOM Configuration Commands Command Object Function RESET { { { { { { { { { { RDF MONITOR EXTRACTOR RECEIVER VOLUME IMAGETRAIL PURGER RDFNET NETWORK TRIGGER } } } } } } } } } } Resets all option values in the configuration memory table to their default values for the specified process.
Operating and Monitoring RDF Using RDFCOM Commands Operational Commands RDFCOM operational commands and their functions are listed in Table 4-2. All of these commands except STATUS can be issued only by members of the super-user group; STATUS can be issued by anyone. Table 4-2.
Operating and Monitoring RDF Using RDFCOM Commands Utility Commands RDFCOM utility commands and their functions are listed in Table 4-3. All of these commands can be issued by anyone. Table 4-3. RDFCOM Utility Commands Command Object Function EXIT - - Terminates an RDFCOM session. FC - - Enables you to edit (fix) a previously issued command. HELP HISTORY {ABBREVIATIONS } {ALL } {command } {message-number} - - Displays help text for commands and messages.
Operating and Monitoring RDF Requesting Online Help Requesting Online Help Through the RDFCOM HELP command, you can display brief descriptions of: • • RDFCOM command syntax (including syntax for the HELP command itself) Numbered RDF messages (such as 700, 705, and so forth) The HELP texts are intended as reminders, not as substitutes for this manual. Help for Command Syntax To obtain syntax information for an individual command, enter HELP followed by the command name.
Operating and Monitoring RDF Requesting Online Help Operational Commands: COPYAUDIT START STATUS STOP TAKEOVER UNPINAUDIT VALIDATE Utility Commands: EXIT FC HELP HISTORY OBEY OPEN OUT RDF Concepts: Abbreviations RDF error messages: E.g., "help 700" prints an explanation for the RDF error message 700 Help for RDF Error Messages For information about a particular error message (its cause, effect, and recommended recovery steps), enter HELP followed by the message number.
Operating and Monitoring RDF Running RDFSCAN Effect: The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created. Recovery: This is an informational message; no recovery is required. Running RDFSCAN RDFSCAN is an interactive command interpreter through which you begin a session and enter requests to scan and display the content of intermediate entry-sequenced RDF message file produced by the standard EMS filter RDFFLTO.
Operating and Monitoring RDF Using RDFSCAN Starting a Session To start an interactive session with RDFSCAN, enter the RDFSCAN keyword at your TACL prompt, followed by the name of the entry-sequenced file you want to open. For example, to begin an RDFSCAN session and open the file $SYSTEM.RDF.MSGLOG for scanning, enter: >RDFSCAN $SYSTEM.RDF.
Operating and Monitoring RDF Using RDFSCAN Commands Using RDFSCAN Commands To request an RDFSCAN function, you enter a corresponding RDFSCAN command, selected from the list in Table 4-4. All of these commands are unrestricted; they can be entered by any user. Table 4-4. RDFSCAN Commands Command Object Function AT [ record-number ] Specifies the record number at which to begin the next RDFSCAN function. DISPLAY [ ON | OFF ] Enables or disables the display of record numbers for the lines listed.
Operating and Monitoring RDF Requesting Online Help Requesting Online Help Through the RDFSCAN HELP command, you can request brief descriptions of: • • Command syntax (including the syntax for the HELP command itself) Introductory information on using the RDFSCAN utility Help for Command Syntax To obtain syntax information for an individual command, enter HELP followed by the command name.
Operating and Monitoring RDF NOLOG Scan Performing Routine Operational Tasks - Closes the log file. - Reads "n" lines of the RDFLOG and displays them with optional pattern matching. FILE: \WHICH.$SYSTEM.RDF.
Operating and Monitoring RDF Displaying Current Configuration Parameters and Operating Statistics Displaying Current Configuration Parameters and Operating Statistics While RDF is running, you can obtain current configuration information and operating statistics for the RDF environment by using ASAP (see Appendix E, Using ASAP) or by using the RDFCOM utility.
Operating and Monitoring RDF • • • • • Displaying Current Configuration Parameters and Operating Statistics * TMF STOP In Progress * * TAKEOVER In Progress * WRONG PROGRAM VERSION NSA Stop Update Pending Update NSA Stopped The rest of the display provides current information about each RDF process configured. For extractors, receivers, and image trails, the configured ATINDEX value is displayed in parentheses following the object name.
Operating and Monitoring RDF Displaying Current Configuration Parameters and Operating Statistics because the primary system goes down, this save point becomes the receiver’s restart point. The RTD for a receiver is the difference between the “last modified time” of the TMF MAT and the timestamp that identifies the associated restart point.
Operating and Monitoring RDF • Displaying Current Configuration Parameters and Operating Statistics Error lets you know if a process has experienced an error. If the column is blank, no error has occurred. If the column for an updater contains asterisks (*****), the updater has experienced a critical error. If the updater is doing an undo pass, the word undo appears in the Error column.
Operating and Monitoring RDF Changing Configuration Parameters Using RDF Status Data to Control TMF Audit Dumping You can use the STATUS RDF command to determine when the RDF extractor has finished processing the audit file that TMF wants to dump. The TMF/RDF trail listed for the extractor in the STATUS RDF display indicates the TMF audit trail file that the RDF extractor is currently processing.
Operating and Monitoring RDF Reading Log Messages EMS Logs (Collectors) In an RDF configuration, two EMS logs (collectors) exist: one at the primary system and the other at the backup system. The log on the primary system is used by the monitor, RDFCOM, and extractor and RDFNET processes. The log on the backup system is used by the receiver, updater, and purger processes.
Operating and Monitoring RDF Reading Log Messages 2. RDF then closes the log (if it is open). The log remains as configured. The next time RDF needs to write a message to the log, RDF attempts to reopen the configured log. If the error condition persists, RDF repeats the steps just described. Examining RDF Messages Previous RDF products directed their messages to a log device and a log file.
Operating and Monitoring RDF Reading Log Messages The following is a sample display for a backup system. (The column numbers in the top line do not appear in the display, and are included only for reference.
Operating and Monitoring RDF Reading Log Messages Record number: 758 2004/06/04 11:21:46 \LAB1 $Z050 773 RDF Remote Updater Started $INFO -> $BINFO Record number: 760 2004/06/04 11:22:33 \LAB1 $Z052 773 RDF Remote Updater Started $POPPY -> $BPOPPY File: $SYSTEM.RDF.
Operating and Monitoring RDF HP NonStop RDF System Management Manual—529826-003 4- 28 Reading Log Messages
5 Managing RDF You manage the RDF environment by monitoring various things using RDFCOM STATUS commands, the EMS log, and the ASAP product. In managing RDF, you must sometimes react to nonroutine events and conditions that affect the RDF operating environment, by performing a variety of special tasks and activities. Although most of this work is not required on a regular basis, the need for it does arise on occasion.
Managing RDF Recovering From File System Errors Recovering From File System Errors Errors detected by the file system generate error numbers that appear within RDF messages reported in the EMS event log. Of particular importance are the file system errors that can cause RDF event messages 700 (modify operation), 705 (open operation), or 739 (create operation). As an example, file system error 59 appears in the following RDF event message 705: 10:59 \RDF05 $WU02 705 File open error 59 on $DATA07.QD004378.
Managing RDF Recovering From File System Errors Table 5-1. Recovery From File Modification Failures (RDF Event 700) (page 1 of 2) File System Error Recovery Action 1 Check file integrity. The updater process skips the modify operation. RDF reports error 1 if an updater receives a “record not found” error while attempting to perform the operation. 2 An invalid operation occurred. An error 2 could be caused by a variety of reasons.
Managing RDF Recovering From File System Errors Table 5-1. Recovery From File Modification Failures (RDF Event 700) (page 2 of 2) File System Error Recovery Action 122, 211 Repair the device or clear the condition. An error 122 or 211 indicates the loss of the primary CPU of a disk process. This is a normal error from which the RDF process will recover. 130 through 139 Repair the device or clear the condition. 157 Check file integrity. 190 Repair the device or clear the condition.
Managing RDF Recovering From File System Errors Table 5-3 lists the file system error numbers and recovery actions for RDF event 739, which reports file-creation failures. Table 5-3. Recovery From File Creation Failures (RDF Event 739) File System Error Recovery Action 10 The file already exists. Purge the old one. 14 Repair the device or clear the condition. 30 through 37 If the problem persists, alter the hardware configuration or perform system tuning.
Managing RDF Handling Disk Space Problems Handling Disk Space Problems When creating a new image file, the receiver preallocates 16 disk extents. If there is not enough disk space, the receiver encounters a file system error 43 when it tries to preallocate these extents. The receiver retries the allocation every 5 seconds and reports the problem at approximately 60-second intervals. The receiver continues trying to preallocate the disk space indefinitely.
Managing RDF • • Communication Line Failures TMF subsystem crash after which the TMF volume recovery is successful TMF file recovery operation that is not to a timestamp RDF cannot recover from the following events: • • • TMF file recovery operation to a timestamp TMF subsystem crash after which TMF cannot perform a successful volume recovery operation Double system failure (the backup system fails after an RDF takeover), if you are not using the triple contingency feature After a TMF file recovery t
Managing RDF Processor Failures Processor Failures All RDF processes other than RDFCOM run as process pairs. If a CPU failure causes a primary RDF process to fail, the backup process takes over without interruption in service. If any RDF process pair stops unexpectedly, the monitor sends abort messages to the other RDF processes in order to bring about an orderly shutdown of RDF. You can then restart the subsystem by merely issuing a START RDF command. Note.
Managing RDF Processor Failures Receiver Failure If the primary CPU of the receiver process fails, the receiver process in the backup CPU takes over and resynchronizes with the extractor process. The extractor process might have to resend audit data that was generated several seconds earlier. When the CPU that failed comes back up, RDF switches the receiver to run on the reactivated primary CPU.
Managing RDF TMF Audited Volume Crash RDF State Transition Failure Periods during which the RDF updaters (or RDF itself) are either starting or stopping are known as RDF state transitions. In rare instances, when a primary CPU fails for an RDF process during execution of a STOP RDF or STOP UPDATE command, not all RDF processes complete the state transition properly. To minimize the chance of encountering this kind of failure, avoid CPU reloads during RDF state transitions.
Managing RDF TMF Subsystem Crash on the Backup System 3. Reenable all pertinent disk volumes for TMF operations by entering the following command through TMFCOM: ~ENABLE DATAVOLS * When this command is executed, TMF performs its volume recovery operation on the audited volumes, and RDF reads the audit during this operation. 4. Restart RDF through RDFCOM by entering: ]START RDF Note. Normally you start RDF before starting your applications.
Managing RDF File Recovery on the Primary System Volume Recovery Failure RDF cannot recover from a TMF subsystem crash if TMF cannot successfully perform volume recovery. After the TMF crash has been resolved, you must perform the following tasks: 1. Resynchronize the primary and backup databases, following procedures explained in sections 6 and 7. 2. Reinitialize RDF.
Managing RDF Stopping RDF Note that you should not perform a file recovery to a timestamp, first purge, or TOMATPOSITION on your backup system if the location occurs prior to an RDF takeover location. Those file recovery operations normally are used to recover a database that has been corrupted. Under normal circumstances, the best way to recover the backup database is to resynchronize it with your primary database.
Managing RDF Stopping RDF by Stopping TMF For each shutdown procedure, the RDF receiver and updater processes write their current context information to the RDF context file before stopping. If you restart but do not reinitialize RDF, the product retrieves the context information from the context file. The context information enables the RDF processes to resume processing where they stopped before the shutdown, unless an audit trail file that RDF needs has been purged and cannot be restored to disk.
Managing RDF Stopping RDF From the Primary System If the communications lines are down when you stop TMF, the extractor continues to run, but it will not recognize that TMF is shut down because the extractor does not read the data in the MAT until the extractor can transmit data to the receiver on the backup system. If the extractor is not reading the MAT, it cannot encounter the TMF shutdown message.
Managing RDF • • Stopping RDF From the Primary System Issue STATUS RDF commands and wait until all of the RDF Time Delay (RTD) times are zero. Issue the STOP RDF command. Note. Even when no TMF transactions are in progress, TMF periodically writes control points to the MAT, which means that the MAT continues to fill even when no application activity is occurring. This can cause RTD times in the status display to fluctuate.
Managing RDF Stopping RDF From the Backup System Stopping RDF From the Backup System If you issue a STOP RDF command on the primary system when the communications lines are down, then you must also do so on the backup system. That is the only time you should ever issue a STOP RDF command on the backup system. RDF can recover from a communications line failure, as explained under Responding to Operational Failures earlier in this section.
Managing RDF Restarting RDF Restarting RDF If you want to restart RDF and have it resume processing where it stopped at the previous shutdown, you can only do so if you have not reinitialized RDF subsystem since the shutdown. Use the START RDF command to restart RDF. RDF automatically starts with UPDATE ON unless you explicitly specify UPDATE OFF in the START RDF command.
Managing RDF Using a Reverse Trigger 6. On system \B, issue an INITIALIZE RDF command using the INITTIME option and specifying the local system time you noted in step 3. This action initializes the RDF extractor on \B so that it cannot miss any relevant audit information. 7. On system \B, configure the RDF subsystem to run from \B to \A. 8. On system \B, start the RDF subsystem. The RDF subsystem begins replicating database changes from \B to \A.
Managing RDF Reciprocal Configurations The steps for performing a planned switchover from \A to \B in such a configuration are: 1. On system \B, stop RDF subsystem #2. Note the local system time; you’ll need it later. 2. On system \A, stop the business applications that access the primary database (Applications #1). 3. On system \A, stop TMF. 4. Wait for RDF subsystem #1 on \A to shut down. 5. On system \B, restart Applications #1.
Managing RDF Takeover Operations Takeover Operations If the primary system fails and you want to switch application processing to the backup system, you need to issue the TAKEOVER command from the backup system. The TAKEOVER command causes RDF to shut down after bringing the backup database to a consistent state. The RDF Takeover Operation When updating is enabled, updaters apply audit as soon as it is safe-stored in the image trails on the backup system.
Managing RDF Preparing for Takeover Processing Transactions that must be undone during this undo pass are stored in the ZFILUNDO file in the Master Image Trail subvolume. Phase Three Undo Pass This is also known as Network Undo. If you are running in an RDF network and you lose one or more primary systems, you must do a takeover on all backup systems in your RDF network. For a complete description of the takeover operation in an RDF network, see RDF Takeovers Within a Network Environment in section 13.
Managing RDF Monitoring Takeover Outcome The following example shows how to use the TAKEOVER command when RDF is running with updating enabled. The command sequence in the example causes the backup system \TORONTO to take over processing from the primary system \SANFRAN. 1. At the TACL prompt on the backup system (\TORONTO), start an RDFCOM session and specify the control subvolume name: >RDFCOM SANFRAN 2.
Managing RDF Takeover Failure For RDF network takeover considerations, see Section 13, Network Transactions. For super fast takeover, see Tips for Executing Fast Business Takeover Operations in section 1. Takeover Failure If a double CPU failure occurs and the receiver process pair or an updater process pair fails during a takeover operation, you can resume the operation just by entering the TAKEOVER command through RDFCOM again.
Managing RDF Checking Exception Files for Uncommitted Transactions primary database to the exact same state that the backup database was in when the takeover operation completed. Note. You always use the logged MAT position from the 888 event message to initiate the file recovery operation, even if the RDF configuration is replicating auxiliary audit trails.
Managing RDF Preparing for Application Processing on the Backup System Preparing for Application Processing on the Backup System See Tips for Executing Fast Business Takeover Operations in section 1 for information on how you can execute an RDF takeover and resume business activities on your backup system in the shortest amount of time.
Managing RDF Reading the Backup Database Note that if you have an RDF Network, there are some situations where File Recovery with the TOMATPOSITION option is not possible. If that is the case, RDF logs an RDF Event 858 at the end of the takeover operation.
Managing RDF Access to Backup Databases in a Consistent State The following example shows the kind of data inconsistency that can occur if the backup database is read while the database is being updated: Suppose that a file named FILEA resides on $VOL1 on the primary system and that a file named FILEB resides on $VOL2 on this primary system. Suppose transaction number 50 causes changes to both FILEA and FILEB on the primary system.
Managing RDF Access to Backup Databases in a Consistent State If the specified timestamp is not at least five minutes greater than the current time, RDFCOM aborts the command and displays the following message: The specified timestamp must be at least five minutes greater than the current time. The STOP UPDATE command itself is logged to the EMS event log under the general RDF message 835.
Managing RDF RDF and NonStop SQL/MP DDL Operations RDF and NonStop SQL/MP DDL Operations When certain Data Definition Language (DDL) operations are performed on NonStop SQL/MP tables protected by RDF, applications that depend on these operations are briefly denied access to the database while the DDL operations are in progress. These periods of unavailability, commonly called outages, end when the DDL operation completes.
Managing RDF Performing Shared Access DDL Operations Database administrators with a clear understanding of the underlying TMF auditing issues might elect to skip some of these steps as long as the DDL operations and other audited operations are performed in the correct sequence on the primary and backup systems. For example, it is not absolutely necessary to stop TMF (and thus RDF), but it is safest to do so.
Managing RDF RDF and NonStop SQL/MX Operations system \A keeping half of the table on system \A and moving the other half to a table on system \X because RDF on system \X does not know about the shared access NonStop SQL/MP DDL operation (the Stop-RDF-Updater audit records for the operation on system /A go to system /B, not to system /Y).
Managing RDF Making Online Dumps With Updaters Running For a successful backup, follow these steps: 1. Execute a process that opens the image trail file with shared read access. This can be a simple process that you supply to perform only this operation. When the purger determines that all updaters are finished with this image trail file (named, say, AA000007), and have moved on to the next image trail file (named, say, AA000008), then it may try to purge AA000007.
Managing RDF Doing FUP RELOAD Operations With Updaters Running After dumping is finished, you should change the access mode back to protected, as follows: 1. Stop the updaters (issue a STOP UPDATE command on the primary system). 2. Alter the UPDATEROPEN attribute of the RDF configuration to PROTECTED: ALTER RDF UPDATEROPEN PROTECTED 3. Restart the updaters (issue a START UPDATE command on the primary system).
Managing RDF Exception File Optimization Exception File Optimization The RDF exception files reside in the control subvolume on $SYSTEM. The name of each is the name of the updater’s primary system volume. Each updater maintains an exception file in which it identifies every audit record that must be undone on the backup database during a takeover. Typically records must be undone because the outcome of the associated transaction is unknown.
Managing RDF Switching Disks on Updater UPDATEVOLUMES Switching Disks on Updater UPDATEVOLUMES The SCF PRIMARY DISK command causes the disk process to switch to the backup CPU. If you need to perform this switch on an updater's UPDATEVOLUME, you should always issue a STOP UPDATE command first, the SCF PRIMARY DISK command next, and then a START UPDATE command. Note.
6 Maintaining the Databases A vital task in working with RDF is to keep the backup and primary databases synchronized with each other. This section, which is intended for database administrators, begins with a discussion of the synchronized and unsynchronized database states.
Maintaining the Databases Understanding Database States Figure 6-2 shows synchronized databases where the application is running on \PRIMARY, three more transactions (T4, T5, T6) have occurred, and RDF is in the process of applying the data records for these transactions to the backup system. Transaction data for T4 has been applied to the backup database. The data for T5 is still being applied to the backup database, and the data for T6 has not yet been sent to the backup system.
Maintaining the Databases Understanding Database States Figure 6-3 shows synchronized databases where the application is running on \PRIMARY and the transaction data for the three new transactions has been applied to the backup database. Figure 6-3. Synchronized Databases, No Outstanding Audit \PRIMARY \BACKUP Database MAT Image File Database T1 T2 T3 T4 T5 T6 T4 T5 T6 T4 T5 T6 T1 T2 T3 T4 T5 T6 Extractor Updater Figure 6-4 shows synchronized databases where TMF has just been shut down.
Maintaining the Databases Backing Up Altered Database Structures Figure 6-5 shows unsynchronized databases. In this figure, T5 and T6 (transactions 5 and 6) have not been transmitted to the backup system because of a physical disaster, such as fire or flood, or because the primary or backup systems have failed.
Maintaining the Databases NonStop SQL/MP or NonStop SQL/MX Databases Catalog Changes RDF views NonStop SQL/MP and NonStop SQL/MX DDL operations as updates to catalogs. NonStop SQL/MP and NonStop SQL/MX catalogs themselves are audited tables, even on the backup system. NonStop SQL/MP and NonStop SQL/MX DDL operations are not replicated by RDF; therefore, RDF does not apply updates to catalogs.
Maintaining the Databases NonStop SQL/MP or NonStop SQL/MX Databases It is safe to perform these operations just like other DDL operations on the primary system. DDL Operation Example This example shows the SQLCI/MXCI commands for adding an index to a table and the order of the operations: 1. Specify the default catalog for the backup system. CATALOG \BACK.$TEST.DBCAT; 2. Create an index on the backup system. CREATE INDEX \BACK.$DATA1.DB.FIRST ON \BACK.$DATA1.DB.EMPLOYEE( FIRST_NAME, LAST_NAME ); 3.
Maintaining the Databases NonStop SQL/MP or NonStop SQL/MX Databases backup system will be corrupt with regard to their key values. Although the records are physically present in the index on the backup system, NonStop SQL/MP does not see them because the actual key specifier value does not match the expected one.
Maintaining the Databases Enscribe Databases Partition Key Changes If you change a key for any partition on the primary system, you must also change the key for the corresponding partition on the backup system. Table Purges If you use the SQLCI PURGE command to purge a protected table from the primary system, you must also purge the corresponding table from the backup system. You should not purge a table on the backup system until you are sure RDF has completed all processing on the table.
Maintaining the Databases Resynchronizing Databases 2. Stop TMF on the primary system; wait for RDF to read the STOP TMF message in the audit trail and stop itself. 3. Start TMF on the primary system so the operations on audited Enscribe files can be performed. 4. Start RDF so that no audit trails are lost, but do not resume application processing. 5. Perform each operation on Enscribe files on the backup system and the corresponding operation on the primary system. 6.
Maintaining the Databases • Resynchronizing Entire Databases Offline Asterisks (****) appear in the final column of the STATUS RDF display, indicating that an updater process has experienced an unexpected file system error. Note. Resynchronization is not always necessary, however, after a file system error in an RDF process. For example, an updater process reporting an error 122 will restart.
Maintaining the Databases Resynchronizing Individual Tables or Files Offline 2. Make a copy of the tables and files that reside on the particular volume. 3. Restart TMF on the primary system. 4. Wait for RDF to shut down (as the result of the TMF shutdown in Step 1). 5. Copy the table or file to the appropriate volume on the backup system. 6. Add the volume back to the RDF configuration. 7. Restart RDF and your applications.
Maintaining the Databases Resynchronizing Individual Tables or Files Offline HP NonStop RDF System Management Manual—529826-003 6- 12
7 Online Database Synchronization With RDF/IMP, IMPX, or ZLT you can synchronize entire databases or selected volumes, files, tables or even partitions while your applications continue to run. For NonStop SQL/MX databases, see Section 15, NonStop SQL/MX and RDF. Overview The RDF online database synchronization protocol consists of the following general steps (the details of which are discussed later in this section): • • • • • initialize the RDF configuration with the SYNCHDBTIME option.
Online Database Synchronization 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). 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.
Online Database Synchronization 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.
Online Database Synchronization Considerations When Synchronizing Entire Databases 8. When your loaded database is on the backup system and the extractor has logged the message indicating it has completed its role in the online synchronization operation, issue the RDFCOM START UPDATE command on the primary system. Note.
Online Database Synchronization Considerations When Synchronizing Entire Databases reduce the number of image trails by stopping the RDF product and reconfiguring a new RDF environment that has fewer image trails. Alternatively, if your database is so big that it could take more time to load and prepare than you have image space for, then you might want to synchronize one part of the database at a time. When that operation has completed, you would then synchronize the next portion.
Online Database Synchronization Considerations When Synchronizing Entire Databases it, but now does not), and the audit information will not be applied to the backup database. In this particular case the database is not corrupted, but data corruption could occur for other NonStop SQL/MP DDL SHARED ACCESS operations.
Online Database Synchronization Considerations When Synchronizing Entire Databases Special Consideration for Enscribe Files If you create empty Enscribe files on your primary system, you should create them with the audit attribute set off. This is particularly important if you create them on volumes protected by RDF. If you create them as audited files on database volumes that are being protected by RDF, the updaters also create them on the backup system.
Online Database Synchronization Considerations When Synchronizing Entire Databases Enscribe Queue File Issues For ENSCRIBE queue files, a different method of obtaining the fuzzy copy is required. You must use the FUP COPY command with the SHARE option specified, and with “FIRST 1” specified. For example, the following command copies the contents of file QUEUE1 to QUEUE2.
Online Database Synchronization Considerations When Synchronizing Entire Databases regarding differences in table and catalog versions. Consult the HP NonStop SQL/MP Version Management Guide. • You can create and load the duplicate tables on the primary system and then move them to the backup system using SQLCI DUP commands or BACKUP/RESTORE and tapes. In either case, however, the tables must be registered in a catalog on the backup system.
Online Database Synchronization Example of Synchronizing An Entire Database Online Example of Synchronizing An Entire Database Online Following is a summary of the steps necessary to perform an online synchronization of an entire database. 1. Issue the following RDFCOM command: STOP RDF 2. Purge the RDF control subvolume and then issue the following RDFCOM command: INITIALIZE RDF, BACKUPSYSTEM \RDFB, SYNCHDBTIME 17JUN2004 17:05 ! Note.
Online Database Synchronization Example of Synchronizing An Entire Database Online reset set type r, no audit set buffered, ext(10,10) set rec 4050, block 4096 set maxextents 16 set code 4700 set part (1, $data2, 2, 2 ) set altkey (1, file 0, keyoff 6, keylen set altkey (2, file 0, keyoff 6, keylen set altkey (3, file 0, keyoff 6, keylen set altkey (4, file 0, keyoff 6, keylen set altkey (5, file 0, keyoff 6, keylen set altfile (0, $data3.test.altf0200 ) create $data3.test.part0200 set altfile (0, $data3.
Online Database Synchronization Synchronizing Selected Database Portions Online corresponding database volumes on the primary system ($DATA0 and $DATA1). Issue the following commands: volume $data2.test fup dup *,\rdfb.$data0.test.* fup alter \rdfb.$data0.test.part0100, & altfile (0, \rdfb.$data0.test.altf0100 ) fup alter \rdfb.$data0.test.part0101, & altfile (0, \rdfb.$data0.test.altf0101 ) volume $data3.test fup dup *,\rdfb.$data1.test.* fup alter \rdfb.$data1.test.part0200, & altfile (0, \rdfb.$data1.
Online Database Synchronization 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.
Online Database Synchronization Partial Database Synchronization Issues Example #3 – Synchronization of an Individual File or Partition on a Volume Suppose you just need to re-synchronize a single file or partition on an existing volume in your RDF configuration. You would first stop your current RDF subsystem. You then delete your current RDF configuration and initialize a new RDF subsystem, using the SYNCHDBTIME option.
Online Database Synchronization Partial Database Synchronization Issues on the primary system. You must change this to point to your alternate key file on your backup system. Use a FUP ALTER command to alter the file label manually. For example: FUP ALTER $DATA.TEST.PART0100, ALTFILE ( 0, \BACKUP.$DATA.TEST.ALTF0100 ) Entry-sequenced and Unstructured Files Currently there is no reliable mechanism to synchronize these file types online. Entrysequenced and unstructured files should be synchronized offline.
Online Database Synchronization Partial Database Synchronization Issues You must load all the partitions of a relative file. Therefore, only one command is possible. FUP LOAD $DATA1.TEST.PART0100, $DATA1.TEMP.PART0100, SHARE You can then use BACKUP and RESTORE (or FUP DUP) with the PARTONLY option to copy the loaded partition you need to the backup system. Entry-sequenced and Unstructured Files Currently there is no reliable mechanism to synchronize these file types online.
Online Database Synchronization Partial Database Synchronization Issues Described below is a set of steps that can be used to synchronize individual partitions of NonStop SQL/MP tables (either primary or secondary partitions). Requirements for Synchronization of Individual Partitions The following methods work only if all the partitions of a given table still reside on disk on the backup system.
Online Database Synchronization Partial Database Synchronization Issues Key-Sequenced Tables Note. Because the SQLCI LOAD operation generates new SYSKEY values in the backup table, key-sequenced tables containing SYSKEYs cannot be synchronized online. The most effective means of describing this method is to use an example. Suppose you have a table named PART whose primary partition is named $DATA.TEST.
Online Database Synchronization Partial Database Synchronization Issues 8. If you created the duplicate table on the primary system, then use the RESTORE utility to put the entire duplicate table with all its partitions onto disk on the backup system. Note that you must use MAP NAMES to correct the system name. Thus, $DATA.DUP.PART is now on the backup system. If you created the duplicate table directly on the backup system, skip this step. 9.
Online Database Synchronization Partial Database Synchronization Issues 2. Use the SQLCI LOAD command with the PARTONLY option to load the partition directly from the primary system to the backup system (without having to create a duplicate table). 3. When the load has completed, issue the RDFCOM STOP SYNCH command. 4. Create all required indexes for the table on the backup system. 5.
Online Database Synchronization Partial Database Synchronization Issues 8. If you created the duplicate table on the primary system, then use the RESTORE utility to put the entire duplicate table with all its partitions onto disk on the backup system. Note that you must use MAP NAMES to correct the system name. Thus, $DATA.DUP.PART is now on the backup system. If you created the duplicate table directly on the backup system, skip this step. 9.
Online Database Synchronization Phases of Online Database Synchronization Phases of Online Database Synchronization Online database synchronization, whether for entire databases or selected volumes, occurs in two phases for both the extractor and all updaters.
Online Database Synchronization Updater Phase 2 Phase 2 Phase 2 completes when the extractor is certain the synch-complete image record has been successfully written in all image trails, and the extractor’s restart location is at a point in the audit trail following the TMP control point record associated with the completion of phase 1, part 3, above. Upon completion of phase 2, the extractor logs message 782. Updater Phase 2 You cannot start the updaters until the extractor has completed phase 2. Note.
Online Database Synchronization When Is Online Database Synchronization Complete? When Is Online Database Synchronization Complete? The following RDF messages assist you in knowing when the various phases of online database synchronization are complete: Extractor Messages Messages 766, 767, and 768 in combination report the completion of phase 1. Message 782 reports the completion of phase 2. Message 782 indicates that the extractor has finished its involvement in the online synchronization operation.
8 Entering RDFCOM Commands To manage, operate, and control RDF and its environment, you enter commands through the RDFCOM online utility. This section, directed to system managers and operators, describes the RDFCOM commands and their attributes.
Entering RDFCOM Commands Where Issued Where Issued Some RDFCOM commands can be issued only from the primary system, others only from the backup system, and still others from either system. For each command, the allowed systems are listed under “Where Issued.” For your convenience, they are also summarized in Table 8-1.
Entering RDFCOM Commands Usage Guidelines RDFNET NETWORK TRIGGER P P P P P P P E P P P P P P P E COPYAUDIT OTHER OBJECTS VOLUME P UPDATE PURGER P RECEIVER ALTER RDF P MONITOR ADD IMAGETRAIL EXTRACTOR Table 8-1.
Entering RDFCOM Commands Usage Guidelines RDFNET NETWORK TRIGGER S S S S S S S S S S S S S S S S COPYAUDIT OTHER OBJECTS VOLUME S UPDATE PURGER S RECEIVER ALTER RDF S MONITOR ADD IMAGETRAIL EXTRACTOR Table 8-2.
Entering RDFCOM Commands Output Displayed Output Displayed For the RDFCOM commands that display output at your terminal (for example, the INFO, SHOW, and STATUS series of commands), the elements that appear are explained under “Output Displayed.” Examples Under the heading “Examples,” each command description presents one or more examples showing how the command is used. For commands that display information, sample output also appears.
Entering RDFCOM Commands Disk File Names Disk File Names The syntax for a file name that identifies a disk file is: [system.][[volume.]subvol.]filename or [system.][volume.]temp-filename system specifies the name of the system on which the file resides. A system name consists of a backslash (\) followed by one to seven alphanumeric characters; the first alphanumeric character must be a letter. volume specifies the name of the volume on which the file resides.
Entering RDFCOM Commands Nondisk Device Names Nondisk Device Names The syntax for a file name that identifies a nondisk device is: [system.]device-name[.qualifier] or [system.]ldev-number system specifies the name of the system on which the device resides. A system name consists of a backslash (\) followed by one to seven alphanumeric characters; the first alphanumeric character must be a letter. device-name specifies the name of a device.
Entering RDFCOM Commands Process File Names Process File Names RDFCOM commands can refer to (and display information about) named processes. In these commands, process names can include no more than five characters: a dollar sign followed by one letter followed by one to three alphanumeric characters.
Entering RDFCOM Commands Command Overview ADD The ADD command applies configuration parameter values for the specified process or other object from the RDF configuration memory table to the RDF configuration file. ADD {RDF {MONITOR {EXTRACTOR {RECEIVER {IMAGETRAIL $volume {PURGER {RDFNET {NETWORK {[VOLUME] $volume {TRIGGER trigger-type } } } } } } } } } } RDF applies RDF global configuration parameters. MONITOR applies configuration parameters for the monitor.
Entering RDFCOM Commands Command Overview [VOLUME] $volume applies configuration parameters for an updater process, implicitly identifying the updater process by the name of the volume on the primary system for which this process is responsible. The updater volume must be audited by TMF. TRIGGER trigger-type applies configuration parameters for a trigger entity. trigger-type is either REVERSE or TAKEOVER. Where Issued Primary system only.
Entering RDFCOM Commands Command Overview begins reading from the current image file at the same place that the receiver process begins writing. Caution. After RDF is configured and running, do not add an updater process unless a STOP TMF command has shut down RDF; otherwise, you cannot be sure that the data on the newly added backup system volume is synchronized with the data on the corresponding primary system volume.
Entering RDFCOM Commands Command Overview To define $SYSTEM.RDFIMP as the location of the RDF software, enter the following commands: ]SET RDF SOFTWARELOC $SYSTEM.RDFIMP ]ADD RDF When the preceding command sequence is executed, all of the other RDF global parameters are set to their default values, as follows. (In this list, \LONDON is the system at which you issued the command sequence.
Entering RDFCOM Commands Command Overview To define a reverse trigger, enter a command sequence such as the following: SET SET SET SET SET SET ADD TRIGGER TRIGGER TRIGGET TRIGGER TRIGGER TRIGGER TRIGGER PROGRAM INFILE OUTFILE WAIT CPU PRIORITY REVERSE $SYSTEM.RDF.RDFCOM $DATA01.RDFCONF.
Entering RDFCOM Commands Command Overview ALTER The ALTER command changes the setting of the specified parameter in the RDF configuration file to the supplied value.
Entering RDFCOM Commands Command Overview RDF State Requirement While RDF is running, the only configuration parameters you can alter are the log file, the purge time, the RDF updater delay, and the priority of each RDF process. You can also change the RDF updater open while RDF is running, but updating must be stopped. To change the setting of any other parameter, you must first stop RDF.
Entering RDFCOM Commands Command Overview To change the primary and backup CPUs for the master receiver process to CPUs 3 and 4 respectively, enter an ALTER RECEIVER CPUS command: ]ALTER RECEIVER CPUS 3:4 Remember you cannot do this particular alter operation while RDF is running.
Entering RDFCOM Commands Command Overview COPYAUDIT This command is only for use with the triple contingency feature. If the primary system fails, you must execute two takeovers: one on each backup system involved in the triple contingency protocol. Upon successful completion of both takeovers, the databases on the two backup systems will almost assuredly not be identical: one of the extractors will have been further ahead of the other in its RDF processing when the failure occurred.
Entering RDFCOM Commands Command Overview system that is behind, specifying the name of the other backup system and its RDF control subvolume. For the following discussion, assume that you have established two RDF configurations, as follows: RDF Configuration #1: \A ------------------> \B (The RDF control subvolume is A1 on both systems.) RDF Configuration #2: \A ------------------> \C (The RDF control subvolume is A2 on both systems.
Entering RDFCOM Commands Command Overview unknown at the time of the original takeover. Because RDFCOM added more audit information to the image trail, there is a chance that the outcome of some of these transactions is now known. Therefore, RDFCOM repositions the updater’s restart location back to the first record that it could not previously apply. (If there were no exception records, then RDFCOM leaves the updater’s restart location unchanged.
Entering RDFCOM Commands Command Overview DELETE The DELETE command deletes the entire configuration record for the specified secondary image trail, updater process, or trigger from the RDF configuration file. DELETE {IMAGETRAIL $volume} [ATINDEX audittrail-index-number] {[VOLUME] $volume } {$volume } {TRIGGER type } IMAGETRAIL $volume deletes a secondary image trail from the configuration, implicitly identifying that trail by the name of the volume on the backup system where it is stored.
Entering RDFCOM Commands Command Overview RDF State Requirement After RDF is initialized, you can issue a DELETE command only when RDF is stopped. Usage Guidelines For the DELETE command to have any effect, a configuration record must already exist for the secondary image trail or updater process associated with the volume name supplied (that is, someone must have previously issued an ADD IMAGETRAIL or ADD VOLUME command for the volume).
Entering RDFCOM Commands Command Overview Now assume that RDF is protecting primary system data volume $DATA06, which is configured to auxiliary audit trail AUX01. Assume also that the changes are being replicated to backup system volume $DATA6, and that the updater for that volume is acquiring its audit data from secondary image trail volume $SECITB.
Entering RDFCOM Commands Command Overview EXIT The EXIT command ends your current RDFCOM session. EXIT Where Issued Primary or backup system. Security Restrictions None; anyone can enter the EXIT command. RDF State Requirement You can issue the EXIT command at any time, whether or not RDF has been started. Usage Guidelines If you issue the EXIT command in your current RDFCOM session, RDFCOM terminates the session and returns control to the operating system.
Entering RDFCOM Commands Command Overview FC The FC (fix command) command enables you to selectively examine, edit, or repeat a previously issued RDFCOM command. {FC} [text] {? } [text] {! } [text] {FC} [ text ] requests RDFCOM to display the most recently issued command that begins with the specified text string and issue a period (.) prompt for your input. You can then use the subcommands R, I, and D to replace, insert, and delete characters in the command line.
Entering RDFCOM Commands Command Overview When you enter the ? or ! character instead of the keyword FC, the requested command appears but you are not prompted for subcommands to change it; use the ? or ! when you only wish to display the command, not change it. The FC command is a standard feature of many HP software products. For more information about how to use this command, see the TACL Reference Manual.
Entering RDFCOM Commands Command Overview You correct this entry by entering the FC command followed by the D (for delete) subcommand under the extra character displayed: ]FC ]SHOW RDDF . D ]SHOW RDF . RDF SOFTWARELOC RDF LOGFILE RDF PRIMARYSYSTEM RDF UPDATERDELAY RDF UPDATERTXTIME RDF UPDATERRTDWARNING RDF UPDATEROPEN RDF NETWORK RDF NETWORKMASTER RDF UPDATEREXCEPTION RDF REPLICATEPURGE RDF OWNER $SYSTEM.RDF $0 \MICKEY 10 60 60 PROTECTED OFF OFF ON OFF SUPER.
Entering RDFCOM Commands Command Overview HELP The HELP command displays explanatory text about RDFCOM commands and RDF messages. HELP [ABBREVIATIONS ] [ALL ] [command ] [RDF-msg-number] ABBREVIATIONS lists the allowed abbreviations for RDFCOM command keywords. ALL lists all RDFCOM commands. command displays information for the RDFCOM command specified by command. RDF-msg-number displays information for the RDF message specified by RDF-msg-number. Where Issued Primary or backup system.
Entering RDFCOM Commands Command Overview Examples To display the syntax of the ADD command, enter: ]HELP ADD RDFCOM displays the following: { { { { ADD { { { { { { { RDF MONITOR EXTRACTOR RECEIVER IMAGETRAIL $volume PURGER RDFNET NETWORK TRIGGER VOLUME $volume $volume } } } } } } } } } } } Cannot be performed with RDF running. Only a user in the SUPER group can execute this command.
Entering RDFCOM Commands Command Overview Utility Commands: EXIT FC HELP HISTORY OBEY OPEN OUT RDF Concepts: Abbreviations RDF error messages: E.g.
Entering RDFCOM Commands Command Overview HISTORY The HISTORY command displays the ten most recently issued RDFCOM commands (including the HISTORY command itself). HISTORY Where Issued Primary or backup system. Security Restrictions None; anyone can enter the HISTORY command. RDF State Requirement You can enter the HISTORY command at any time, whether or not RDF has been started.
Entering RDFCOM Commands Command Overview INFO The INFO command displays the current configuration parameter values from the configuration file for the specified process or other object.
Entering RDFCOM Commands Command Overview If you do not specify a command file for the text, TACL supplies the name of its current default output destination—usually the terminal from which you began your session. The subsystem saves the text in the command file, also embedding the appropriate SET and ADD commands.
Entering RDFCOM Commands Command Overview VOLUME * displays the current configuration parameter values for all updater processes. [VOLUME] $volume displays the current configuration parameter values for an updater process, implicitly identifying the updater process by the name of the volume on the primary system for which this process is responsible. Where Issued Primary or backup system. Security Restrictions None; anyone can enter the INFO command.
Entering RDFCOM Commands RDF RDF RDF RDF RDF RDF RDF RDF UPDATERDELAY 10 UPDATERTXTIME 10 UPDATERRTDWARNING 60 UPDATEROPEN PROTECTED NETWORK OFF NETWORKMASTER OFF UPDATEREXCEPTION OFF REPLICATEPURGE OFF MONITOR CPUS 1:2 MONITOR PRIORITY 165 MONITOR PROCESS $MON1 EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR PURGER PURGER PURGER PURGER PURGER ATINDEX 0 CPUS 2:1 PRIORITY 165 PROCESS $EXT RTDWARNING 60 CPUS 3:2 PRIORITY 165 PROCESS $PURG RETAINCOUNT 50 PURGETIME 60 RECEIVER RECEIVER RECEIVER RECEIVER
Entering RDFCOM Commands VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME Command Overview TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER $DATA03 ATINDEX 0 CPUS 2:1 PRIORITY 160 UPDATEVOLUME $DATA3 IMAGEVOLUME $SECIT2 PROCESS $UP03 PROGRAM $SYSTEM.RDF.RDFCOM INFILE $DATA01.RDF.RDFCONF OUTFILE $DATA01.RDF.OUTFILE CPUS 0:1 PRIORITY 150 NOWAIT REVERSE Note that the primary system name is set implicitly and the backup system name is set in the INITIALIZE RDF command.
Entering RDFCOM Commands Command Overview SET EXTRACTOR PROCESS $EXT2 SET EXTRACTOR RTDWARNING 60 ADD EXTRACTOR INFO MONITOR Command To display the current configuration parameters for the monitor process, enter: ]INFO MONITOR RDF displays output in the following format: MONITOR PROCESS $MON MONITOR CPUS 2:1 MONITOR PRIORITY 170 You would see this particular output, for example, if you originally configured the monitor to run in CPUs 2 and 1 at the default priority of 165, but later changed the priority
Entering RDFCOM Commands Command Overview INFO VOLUME Command Suppose that you configured an updater process named $UP1 to back up all changes made to audited files on the primary volume named $DATA01, and that the corresponding volume on the backup system is $DATA1. Also suppose $UP1 was configured to the secondary image trail $SECIT1 on the backup system (and that $SECIT1 was previously added to the RDF configuration using an ADD IMAGETRAIL command).
Entering RDFCOM Commands VOLUME VOLUME VOLUME VOLUME VOLUME Command Overview CPUS 4:5 IMAGEVOLUME $SECIT2 PRIORITY 160 PROCESS $UP03 UPDATEVOLUME $DATA3 INFO PURGER Command To display the current configuration parameters for the purger process, enter the following command: ]INFO PURGER The output shows that the purger is configured with the following parameter values: running in CPUs 3 and 2, with a priority of 165, with a retaincount of 50, with a purgetime of 60, and with the process name $PURG: PURGE
Entering RDFCOM Commands Command Overview INFO TRIGGER Command With OBEYFORM Option Like all INFO commands, INFO TRIGGER supports the optional OBEYFORM parameter. The output of an INFO TRIGGER REVERSE, OBEYFORM command might be: SET SET SET SET SET SET ADD TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER TRIGGER PROGRAM $SYSTEM.RDF.RDFCOM INFILE $DATA01.RDF.RDFCONF OUTFILE $DATA01.RDF.
Entering RDFCOM Commands Command Overview INITIALIZE RDF The INITIALIZE RDF command creates the RDF configuration and context files for establishment of a new RDF configuration. Note. If you plan to initialize more than one RDF subsystem on your primary system, then you must open each new control subvolume before you initialize and configure your new RDF environment. This means that after you have initialized one RDF subsystem, you must enter an OPEN command, specifying the new control subvolume.
Entering RDFCOM Commands Command Overview month is the first three letters of the month, such as JAN, FEB, MAR. year is a four-digit number greater than 1996. hour is a number from 0 to 23. min is a number from 00 to 59. min must be preceded by a colon (:). INITTIME : | NOW is a timestamp used for online product initialization. It has the same format as the timestamp parameter described above. NOW causes RDF to be initialized at the current date and time.
Entering RDFCOM Commands Command Overview SYNCHDBTIME : is a timestamp used for online database synchronization. It has the same format as the timestamp parameter described above. There are no special considerations for specifying the synchdbtime parameter, except that it must designate a time earlier than the present time. The SYNCHDBTIME parameter can only be used if RDF/IMPX or ZLT is installed on both the primary and backup systems.
Entering RDFCOM Commands • Command Overview If you include the INITTIME option without the ! option, RDFCOM displays: Do you wish to proceed? [Y/N] Enter Y or YES to proceed; enter N or NO to cancel the command. If you enter Y or YES, RDFCOM displays: Please wait while RDF searches for the specified timestamp. Initialization point for 12JAN2004 14:30 has been found. RDF will start at RBA: 376275 MAT file: $AUDIT.ZTMFAT.
Entering RDFCOM Commands Command Overview Usage Guidelines If your RDF subsystem is running and you do not include the TIMESTAMP, INITTIME, or SYNCHDBTIME options in the INITIALIZE RDF command, then you must stop, delete, and reconfigure TMF before entering the INITIALIZE RDF command. Before issuing the INITIALIZE RDF command within an existing RDF configuration, you must first purge all files from the control subvolume on both the primary and backup systems.
Entering RDFCOM Commands • Command Overview If you plan to include the TIMESTAMP option in the INITIALIZE RDF command, make sure that the primary system database is backed up after the TMF shutdown so that the backup database can be restored at this point in the audit trail. Consider the following example: a. TMF and RDF subsystems are running. b. TMF subsystem is stopped, and RDF subsystem subsequently stops. c. TMF subsystem is started and application processing resumed. d. TMF subsystem is stopped.
Entering RDFCOM Commands Command Overview identical before entering the INITIALIZE RDF command. For more information about database synchronization, see Understanding Database States in section 6. Examples The following INITIALIZE RDF command, issued on the primary system, \LON, initializes the subsystem to 2:30 pm, January 12, 2004: ]INITIALIZE RDF, BACKUPSYSTEM \CHI, TIMESTAMP 12JAN2004 14:30 Do you wish to proceed? [Y/N] Y Please wait while RDF searches for the specified timestamp.
Entering RDFCOM Commands Command Overview OBEY The OBEY command executes a series of commands entered in a command file. OBEY [\system.][$volume.][subvolume.]file system identifies the system on which the command file is stored. volume identifies the disk volume on which the command file is stored. subvolume identifies the subvolume on which the command file is stored. file identifies the command file, which contains one or more valid RDFCOM commands. Where Issued Primary or backup system.
Entering RDFCOM Commands Command Overview RDFCOM returns an error message if the command file cannot be opened or does not exist, or if any command within the command file is syntactically incorrect or otherwise in error. After this message appears, RDFCOM closes the command file and reads its next command from the file from which it read the OBEY command.
Entering RDFCOM Commands Command Overview OPEN The OPEN command identifies the RDF control subvolume to which subsequent RDFCOM commands in this session apply. On the primary and backup systems, the RDF configuration and context files are stored in the RDF control subvolume on $SYSTEM. On the backup system, the image trail files for each trail are stored in the RDF control subvolume on the associated image trail volume.
Entering RDFCOM Commands • Command Overview Sequence B: >RDFCOM DENVER3 ]STATUS RDF Remember that, when you enter the RDFCOM command without specifying a control subvolume, RDFCOM assumes that the control subvolume name is the same as that of the local system on which the RDFCOM is running (without the backslash and with no suffix character). Thus, the OPEN and STATUS commands shown in Sequence A and Sequence B will only work if a configuration file exists on the control subvolume DENVER3.
Entering RDFCOM Commands Command Overview OUT The OUT command redirects the output of the current RDFCOM session to the specified device or file. OUT [\system.][$volume.][subvolume.][file] system identifies the system on which the output file is stored. volume identifies the disk volume on which the output file is stored. subvolume identifies the subvolume on which the output file is stored. file specifies the name of the file or device to which RDFCOM is to direct subsequent output.
Entering RDFCOM Commands Command Overview file that already exists, this must be an EDIT file; RDFCOM appends its output to that file. RDFCOM continues to direct session output to the designated file or device until you issue another OUT command or until you terminate the session, whichever happens first. If you do not specify an OUT command in your session, RDFCOM directs output to the current default output destination—usually the terminal from which you issued the RDFCOM command to start the session.
Entering RDFCOM Commands Command Overview RESET The RESET command resets all configuration parameters for the specified entity to their default values within the RDF configuration memory table. The parameters within the configuration file do not change, however, unless you issue a corresponding ADD command. RESET {RDF {MONITOR {EXTRACTOR {RECEIVER {VOLUME {IMAGETRAIL {PURGER {RDFNET {NETWORK {TRIGGER } } } } } } } } } } RDF resets the values for the RDF global options.
Entering RDFCOM Commands Command Overview NETWORK resets the values for the network configuration record. TRIGGER resets the values for a TRIGGER record. For all of the default parameter values for the RDF global options and the individual processes see the SET EXTRACTOR, SET IMAGETRAIL, SET MONITOR, SET PURGER, SET RDF, SET RDFNET, SET RDFNETWORK, SET RECEIVER, SET VOLUME, and SET TRIGGER command descriptions. Where Issued Primary system only.
Entering RDFCOM Commands Command Overview To reset the updater process parameters in the configuration memory table to their default values, enter: ]RESET VOLUME To reset the trigger parameters in the configuration memory table to their default values, enter: ]RESET TRIGGER HP NonStop RDF System Management Manual—529826-003 8- 55
Entering RDFCOM Commands Command Overview SET EXTRACTOR The SET EXTRACTOR command sets extractor process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD EXTRACTOR command.
Entering RDFCOM Commands Command Overview RTDWARNING rtd-time specifies the the RTD warning threshold (in seconds, 0 or greater) for the extractor. This threshold is used by the STATUS RTDWARNING command to determine if the extractor is to be included in its display. The display includes only those RDF processes (extractor or updaters) whose RTD exceeds the configured threshold. The default is 60 seconds.
Entering RDFCOM Commands Command Overview Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set, as follows: • • • If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an ATINDEX value of 1. If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail with an ATINDEX of 1.
Entering RDFCOM Commands Command Overview SET IMAGETRAIL The SET IMAGETRAIL command associates an image trail with a specific audit trail on the primary system. The supplied value is not applied to the RDF configuration file, however, until you issue an ADD IMAGETRAIL command. SET IMAGETRAIL ATINDEX audittrail-index-number ATINDEX audittrail-index-number is an integer value identifying a configured TMF audit trail on the primary system. 0 specifies the MAT.
Entering RDFCOM Commands Command Overview SET MONITOR The SET MONITOR command sets monitor process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD MONITOR command.
Entering RDFCOM Commands Command Overview Usage Guidelines The SET MONITOR command enters the parameter values specified for the monitor in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command.
Entering RDFCOM Commands Command Overview SET NETWORK The SET NETWORK command sets RDF network configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD NETWORK command.
Entering RDFCOM Commands Command Overview RDF State Requirements None. Usage Guidelines The SET NETWORK command enters the RDF network parameter values specified in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command.
Entering RDFCOM Commands Command Overview SET PURGER The SET PURGER command sets purger process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD PURGER command.
Entering RDFCOM Commands Command Overview RETAINCOUNT num specifies how many image trail files must be retained on disk for each image trail (including the image trail file currently in use). num must be within the range 2 to 5000. If you do not explicitly set this configuration parameter, the default value is 2. This configuration parameter is only relevant for the triple contingency feature; otherwise, this parameter should be left at its default value. The importance of this parameter is as follows.
Entering RDFCOM Commands Command Overview just begun reading file AA000013. Also assume that there are no long-running transactions that span from file AA000010 to file AA000013. Files AA000010 through AA000012 might no longer needed, but, because the RETAINCOUNT is set to three, the purger process can only purge AA000010 (it must keep AA000011 and AA000012 on disk).
Entering RDFCOM Commands Command Overview SET RDF The SET RDF command sets RDF global configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD RDF command. SET RDF global-option where global-option is: {LOGFILE $ems-collector-name {UPDATERDELAY delay-time {UPDATERTXTIME tx-time {UPDATERRTDWARNING rtd-time {UPDATEROPEN {PROTECTED | SHARED} {SOFTWARELOC $volume.
Entering RDFCOM Commands Command Overview UPDATERTXTIME tx-time specifies the maximum transaction duration (in seconds, from 10 to 300) for all updater processes. The default is 60 seconds. RDF updaters operate in transaction mode. Updater transactions are essentially long-running transactions that pin audit trail files on the backup system and can affect the duration of backout operations if an updater transaction aborts for any reason.
Entering RDFCOM Commands Command Overview To change the configured updater access-mode, do as follows: 1. Issue a STOP UPDATE command. 2. Issue an ALTER RDF UPDATEROPEN command specifying the desired access mode 3. Issue a START UPDATE command. SOFTWARELOC $volume.subvolume specifies where the RDF software is installed. The default is $SYSTEM.RDF. NETWORK {ON | OFF} specifies whether or not you are configuring an RDF network.
Entering RDFCOM Commands Command Overview LOCKSTEPVOL $volume specifies the primary system disk volume on which the RDF lockstep file (ZRDFLKSP.) is to be located. The specified volume must be configured to the Master Audit Trail (MAT), and either the entire volume or at least the lockstep file must be protected by the RDF subsystem. For information about the RDF lockstep capability, see Section 14, Process-Lockstep Operation.
Entering RDFCOM Commands Command Overview individual user can be assigned a separate super-user group userid. If one user is assigned SUPER.FIRST and another SUPER.SECOND, for example, they can both log on with their userid and be able to start or stop RDF. The RDF processes do not run under SUPER.FIRST or SUPER.SECOND, however, but under SUPER.RDF (the RDF OWNER assigned during configuration). The same principal applies to the other eight users.
Entering RDFCOM Commands Command Overview SET RDFNET The SET RDFNET command sets RDFNET process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD RDFNET command.
Entering RDFCOM Commands Command Overview Usage Guidelines The SET RDFNET command enters the parameter values specified for the RDFNET process in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command.
Entering RDFCOM Commands Command Overview SET RECEIVER The SET RECEIVER command sets receiver process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD RECEIVER command.
Entering RDFCOM Commands Command Overview RDFVOLUME $volume specifies which disk volume on the backup system is to be used for the receiver’s master image trail (the image trail to which the receiver writes all commit/abort records). The default is $SYSTEM. Note that this attribute applies only to the master receiver (the receiver process configured with an ATINDEX value of 0). It is ignored for auxiliary receivers. For best performance, do not use $SYSTEM as the RDFVOLUME.
Entering RDFCOM Commands Command Overview The default is SLOWMODE OFF. Where Issued Primary system only. Security Restrictions None. RDF State Requirements None. Usage Guidelines The SET RECEIVER command enters the parameter values specified for the receiver in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command.
Entering RDFCOM Commands Command Overview Examples To configure a receiver process named $RCV0 to run in CPUs 0 and 1, with the RDF master image files residing on the volume $IMAGE and having primary and secondary extents of 1000 pages each, issue the following commands: ]SET ]SET ]SET ]SET ]ADD RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER PROCESS $RCV0 CPUS 0:1 RDFVOLUME $IMAGE EXTENTS (1000,1000) By default, in this example the receiver process is associated with the MAT and will run at a priority of
Entering RDFCOM Commands Command Overview SET TRIGGER The SET TRIGGER command sets trigger parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD TRIGGER command. The trigger type (REVERSE or TAKEOVER) is specified in the ADD TRIGGER command.
Entering RDFCOM Commands Command Overview WAIT causes RDF to wait for the trigger process to terminate before shutting down. This is the default value. NOWAIT specifies that once the trigger process is launched, RDF can immediately proceed to shut down. Where Issued Primary system; backup system when the primary is not available. Security Restrictions None. RDF State Requirements None.
Entering RDFCOM Commands Command Overview Example This example shows how to configure an RDF environment to replicate from \LEFT to \RIGHT, with the ability to reverse replication so it goes from from \RIGHT to \LEFT. The RDF configuration on \LEFT includes the following (the standard SET/ADD RDF, EXTRACTOR, RECEIVER, PURGER, IMAGETRAIL and VOLUME configuration commands are omitted): INITIALIZE RDF, BACKUPSYSTEM \RIGHT ! SET TRIGGER PROGRAM $SYSTEM.RDF.RDFCOM SET TRIGGER INFILE $DATA01.RDFCONF.
Entering RDFCOM Commands Command Overview SET VOLUME The SET VOLUME command sets updater process configuration parameters within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD VOLUME command. SET VOLUME volume-option where volume-option is: {ATINDEX audittrail-index-number {CPUS primary-CPU : backup-CPU {PRIORITY priority {PROCESS process-name {IMAGEVOLUME $volume {UPDATEVOLUME $volume {INCLUDE subvol.
Entering RDFCOM Commands Command Overview IMAGEVOLUME $volume identifies a disk volume associated with a secondary image trail previously added to the RDF configuration (by way of an ADD IMAGETRAIL command), implicitly associating this updater process with that trail. This parameter is required. There is no default. An updater must always be explicitly associated with a secondary image trail.
Entering RDFCOM Commands Command Overview Usage Guidelines The SET VOLUME command enters the parameter values specified for the updater in this command into the RDF configuration table in memory. This table serves as an input buffer only, and so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command. For ATINDEX values greater than 0, the specified value must match the audit trail number of a configured auxiliary audit trail.
Entering RDFCOM Commands Command Overview Examples Suppose that one of the volumes containing audited files on the primary system is named $DATA01 and you want to create an updater process named $U01 to maintain a copy of that volume, named $DATA1, on the backup system.
Entering RDFCOM Commands Command Overview SHOW The SHOW command displays the current parameter values contained in the RDF configuration memory table for the specified process. With this command, you can confirm the parameter values before issuing the ADD command that actually applies them to the configuration file.
Entering RDFCOM Commands Command Overview VOLUME displays the current configuration parameter values for an updater process. Where Issued Primary or backup system. Security Restrictions None; anyone can issue the SHOW command. RDF State Requirements You can enter the SHOW command at any time. Usage Guidelines This command retrieves information from the RDF configuration memory table, which serves as an input buffer for a subsequent ADD command.
Entering RDFCOM Commands Command Overview Examples Examples of several SHOW commands follow: SHOW RDF Command To display the global configuration parameter values specified by a series of SET RDF commands, enter: ]SHOW RDF In response, RDFCOM displays something such as the following: RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF SOFTWARELOC $SYSTEM.
Entering RDFCOM Commands Command Overview RDFCOM includes the line containing PROCESS process-name in the display only if the process name was specified in a SET command. SHOW PURGER Command Suppose that a series of SET PURGER commands specifies that a purger process named $PURG is to run in CPUs 3 and 2 at priority 165 with a RETAINCOUNT of 50.
Entering RDFCOM Commands Command Overview SHOW RDFNET Command Suppose that a series of SET RDFNET commands specifies the RDFNET process named $MNET is to run in CPUs 0 and 1 at priority 180.
Entering RDFCOM Commands Command Overview START RDF The START RDF command starts RDF. START RDF [, UPDATE {ON | OFF}] UPDATE ON enables update processing on the backup system; this is the default value. UPDATE OFF disables update processing on the backup system. RDF image files are not purged from the backup system. Where Issued Primary system only.
Entering RDFCOM Commands Command Overview When RDF starts, it automatically executes an implicit VALIDATE CONFIGURATION command with the following results: • • If any parameter value in the RDF configuration file is incorrect, RDFCOM displays an error message, and the START RDF operation fails. If all of the parameters in the RDF configuration file are correct, RDF copies the configuration file from the primary system to the backup system, displays any warning messages, and starts the RDF processes.
Entering RDFCOM Commands Command Overview START UPDATE The START UPDATE command starts all updater processes on the backup system. START UPDATE Where Issued Primary system only. Security Restrictions You can issue the START UPDATE command if you are a member of the super-user group and have a remote password from the RDF primary system to the backup. RDF State Requirement Before you can issue this command, RDF must be running.
Entering RDFCOM Commands Command Overview STATUS The STATUS command displays current configuration information and operational statistics for the RDF environment, or specified portions thereof. Note that all forms of the STATUS command, except STATUS RTDWARNING, automatically include information and statistics for the monitor process.
Entering RDFCOM Commands Command Overview RTDWARNING requests information and statistics for only those processes (the extractor or any updater) that have fallen behind the configured RTD threshold (rtd-time). For information about setting that threshold, see the SET RDF command. Note that each time this command is issued and a process is displayed because it has fallen behind the RTD warning threshold, an EMS event is generated for that process.
Entering RDFCOM Commands Command Overview STATUS RDF Command Output Display The STATUS RDF command presents its display in the following format: RDFCOM - T0346A07 - 18JAN05 (C)2005 Hewlett-Packard Development Company, L.P. Status of \RDF04 -> \RDF05 RDF 2005/01/22 16:26:49.082 Control Subvol: $SYSTEM.
Entering RDFCOM Commands Command Overview For extractors, receivers, and image trails, the configured ATINDEX value is displayed in parentheses following the object name. In the above example, the extractor $RE00 and receiver $RR00 are associated with the MAT, while the extractor $RE01 and receiver $RR01 are associated with auxiliary audit trail AUX01. Because of insufficient space, however, ATINDEX values could not be displayed explicitly for updaters.
Entering RDFCOM Commands Command Overview The RTD value reported for each updater process is the difference between the “last modified time” of the TMF master audit trail (MAT) and the timestamp in the most recent image record seen by the particular updater. The RTD value reflects, in the most general sense, the amount of time by which the backup database is lagging behind the primary database.
Entering RDFCOM Commands Command Overview Rel Byte No The seventh column specifies where in the specified file the particular process is currently reading. If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the RTD Time, Sequence, and Rel Byte No fields, and an appropriate file-system error number in the Error field. Cpus The eighth column specifies the CPUs in which each process pair is running.
Entering RDFCOM Commands Command Overview Special Messages If you issue the STATUS RDF command while an RDF TAKEOVER operation is in progress, RDF displays the current state as “TAKEOVER IN PROGRESS.
Entering RDFCOM Commands Command Overview STOP RDF The STOP RDF command shuts down RDF. STOP RDF { [, DRAIN ] } { [, REVERSE ] } DRAIN causes the following actions: • • • • All TMF audit records up to the time the command is entered are replicated to the image trails on the backup node. The RDF processes shut down in a manner similar to when a stop TMF record is encountered in the audit trail. Each updater shuts down after it has applied all audit records up to the stop point.
Entering RDFCOM Commands Command Overview Where Issued You can issue the STOP RDF, DRAIN and STOP RDF, REVERSE commands only at the primary system. Security Restrictions You can issue the STOP RDF command if you are a member of the super-user group that initialized RDF and have a remote password from the RDF primary system to the backup. RDF State Requirement You can issue the STOP RDF, DRAIN and STOP RDF, REVERSE commands only while RDF is running and update is on.
Entering RDFCOM Commands • Command Overview All communications lines to the primary system are down. If the decision has been made to stop RDF on the backup system, issue a STOP RDF command at the backup system. All processes running on the backup system write context information to a context file and then stop. If the communications lines between the primary and backup systems are up, a STOP RDF command issued at the backup system fails, and RDFCOM displays an error message. Note.
Entering RDFCOM Commands Command Overview Examples To request RDFCOM to stop RDF, enter: ]STOP RDF To request RDFCOM to replicate all audit records up to the time the command was issued, and bring RDF to a controlled stop, enter: ]STOP RDF, DRAIN To request RDFCOM to replicate all audit records up to the time the command was issued, and run the configured reverse trigger program, enter: ]STOP RDF, REVERSE HP NonStop RDF System Management Manual—529826-003 8-103
Entering RDFCOM Commands Command Overview STOP SYNCH The STOP SYNCH command is used as part of the online database synchronization protocol. STOP SYNCH Where Issued Primary system. Security Restrictions You can issue the STOP SYNCH command if you are a member of the super-user group and have a remote password from the RDF primary system to the backup. RDF State Requirement You can issue the STOP SYNCH command only when RDF is running.
Entering RDFCOM Commands Command Overview STOP UPDATE The STOP UPDATE command suspends updating of the backup database and stops all updater processes. When all updater processes are stopped, RDF issues a 910 EMS message. STOP UPDATE [ , TIMESTAMP : ] If you use the stop-update-to-time version of this command, the TIMESTAMP parameter suspends updating at the specified time.
Entering RDFCOM Commands Command Overview Security Restrictions You can issue the STOP UPDATE command if you are a member of the super-user group and have a remote password from the RDF primary system to the backup. RDF State Requirement You can issue the STOP UPDATE command only when RDF is running.
Entering RDFCOM Commands Command Overview Examples To suspend updating activities and stop the updater processes, enter the following command: STOP UPDATE To suspend updating activities and stop the updaters from processing transactions committed by 2:30 P.M.
Entering RDFCOM Commands Command Overview TAKEOVER The TAKEOVER command causes the backup database to become transactionally consistent and available as the database of record. TAKEOVER [!] ! Causes the takeover to be performed immediately, with no attempt to verify that the primary system is inaccessible. Be careful. If you include the "!" and the primary system is still accessible, executing the TAKEOVER command could put your backup database out of synchronization with the primary database.
Entering RDFCOM Commands Command Overview Usage Guidelines The TAKEOVER command is customarily issued when the primary system fails or otherwise becomes unavailable, and makes the backup database the primary database. Caution. The TAKEOVER command is not a normal operational command. Operators should never issue this command strictly on their own initiative. Issue this command only when specifically told to do so by someone in high authority.
Entering RDFCOM Commands Command Overview For more information about undo processing during a takeover operation, see Takeover Operations in section 5. During a TAKEOVER operation, RDF completes all the processing it can on the backup system, writes information about pending records (data audit records for which no commit/abort records have been received on the backup system) to the exception file, and stops RDF on the backup system.
Entering RDFCOM Commands Command Overview Limitation When building the undo list for an RDF takeover operation, the purger has a limit of 655,360 transactions. If this limit is exceeded, the purger process logs an RDF event 853 and abends. In this situation, contact your service provider. Example The following command sequence initiates RDF TAKEOVER processing in which the backup system \TORONTO takes over processing from the primary system \SANFRAN. 1.
Entering RDFCOM Commands Command Overview UNPINAUDIT The UNPINAUDIT command unpins TMF audit trail files on the primary system. UNPINAUDIT Where Issued Primary system only. Security Restrictions You can issue the UNPINAUDIT command if you are a member of the super-user group. RDF State Requirement You can only issue the UNPINAUDIT command while RDF is stopped.
Entering RDFCOM Commands Command Overview VALIDATE CONFIGURATION The VALIDATE CONFIGURATION command validates the parameters in the RDF configuration file. VALIDATE CONFIGURATION Where Issued Primary system only. Security Restrictions You can issue the VALIDATE CONFIGURATION command if you are a member of the super-user group. RDF State Requirement You can only issue the VALIDATE CONFIGURATION command while RDF is stopped.
Entering RDFCOM Commands • • • Command Overview The volumes for the image files have enough room for two more image files (for an RDF restart). The primary volumes associated with the updater processes are valid and are being audited to the TMF audit trail. The backup volume associated with each updater process (specified by the UPDATEVOLUME option of the SET VOLUME command) exists on the backup system. If RDFCOM detects any configuration errors, it displays an appropriate message.
9 Entering RDFSCAN Commands All RDF messages are directed to an EMS event log (collector). To examine that log without looking at all events for the entire system, you first use the standard EMS filter RDFFLTO to create an intermediate entry-sequenced file copy of the RDF log, and then enter commands through the RDFSCAN online utility. This section, which is addressed to system managers and operators, describes the RDFSCAN commands and their attributes.
Entering RDFSCAN Commands Command Description Elements Command Description Elements The RDFSCAN command descriptions include the same elements as the RDFCOM command descriptions appearing in Section 8, except for the following items, which are not included because they are the same in all cases: • • • Where Issued: All RDFSCAN commands can be issued at either the primary or backup node.
Entering RDFSCAN Commands AT AT The AT command specifies the record in the intermediate entry-sequenced file at which RDFSCAN begins the next operation. AT [record-number] record-number identifies the record by its record number. Record number 0 specifies the first record (RDF message) in the file. Usage Guidelines Messages generated by RDF are written to an EMS event log.
Entering RDFSCAN Commands DISPLAY DISPLAY The DISPLAY command enables or disables the display of line (record) numbers in subsequent RDFSCAN output. DISPLAY {ON | OFF} ON enables the display of record numbers. OFF disables the display of record numbers. Usage Guidelines The DISPLAY function is automatically enabled if pattern matching is enabled and is automatically disabled if pattern matching is disabled.
Entering RDFSCAN Commands DISPLAY If you issue a LIST 4 command only, without setting the display feature on, RDFSCAN displays the following: Enter the next RDFscan function you want: LIST 4 2004/06/11 15:13:30 \LAB1 $LEXT 774 RDF Local Extractor Started 2004/06/11 16:10:01 \LAB1 $RDFCOM 835 STOP UPDATE 2004/06/11 16:10:06 \LAB1 $ZRDF 808 Update mode has been set OFF 2004/06/11 16:49:56 \LAB1 $RDFCOM 835 STOP RDF File: $SYSTEM.SANFRAN.
Entering RDFSCAN Commands EXIT EXIT The EXIT command ends your current RDFSCAN session. EXIT Usage Guidelines When you issue the EXIT command, RDFSCAN terminates your session and returns control to the TACL command interpreter. You can also end your session by pressing the Control and Y keys at the same time (Ctrl-Y), which is equivalent to issuing the EXIT command.
Entering RDFSCAN Commands FILE FILE The FILE command selects a file generated by the RDFFLTO filter to which subsequent RDFSCAN commands apply. FILE [\system.][$volume.][subvolume.]file \system identifies the system on which the file is stored. $volume identifies the disk volume on which the file is stored. subvolume identifies the subvolume on which the file is stored. file identifies the file that you want to examine.
Entering RDFSCAN Commands When it receives this command, RDFSCAN displays a message of the following format, followed by a prompt for a new command: File: $SYSTEM.GOLDGT.
Entering RDFSCAN Commands HELP HELP The HELP command displays the syntax of RDFSCAN commands or introductory information about the RDFSCAN utility. HELP [ ALL ] [ INTRO ] [ command ] ALL displays the syntax of all RDFSCAN commands. INTRO displays information on how to use the RDFSCAN utility. command displays the syntax of the RDFSCAN command indicated by command.
Entering RDFSCAN Commands LIST LIST The LIST command displays a specified number of log messages that contain the current match pattern. LIST number number is the maximum number of log records to be shown. Usage Guidelines If you omit the number of records to be listed, RDFSCAN prompts you as follows: Enter count to list: The search begins at the current record (the record number specified in an immediately preceding AT command).
Entering RDFSCAN Commands Enter the next RDFSCAN function you want: LIST 4 Record number: 553 2004/06/08 04:13:49 \LAB1 $AU02 790 Backup Process Created in Processor 03 Record number: 554 2004/06/08 04:13:49 \LAB1 $AU02 718 Switched to original Primary Processor Record number: 792 2004/06/08 05:01:35 \LAB1 $AU02 790 Backup Process Created in Processor 03 Record number: 793 2004/06/08 05:01:35 \LAB1 $AU02 718 Switched to original Primary Processor File: $SYSTEM.SANFRAN.
Entering RDFSCAN Commands LOG LOG The LOG command selects a file to which subsequent LIST commands copy their output in addition to the standard output device. When you issue the LOG command followed by a LIST command, RDFSCAN continues to display the LIST records on the standard device and also copies them to the file specified in the LOG command. LOG [\system.][$volume.][subvolume.]file \system identifies the system on which the destination file is located.
Entering RDFSCAN Commands LOG Output Displayed The LOG command copies the records to the destination file in the same format used by the LIST command. Examples Suppose you are examining the entry-sequenced file $SYSTEM.SANFRAN.RDFLOG from within an RDFSCAN session on the primary node \SANFRAN and that your default volume and subvolume are $SYSTEM and SANFRAN, respectively. To copy all records that you examine with the LIST command to the file named $SYSTEM.SANFRAN.
Entering RDFSCAN Commands MATCH MATCH The MATCH command specifies a pattern to search for in the file. RDFSCAN searches for the specified character string without regard for uppercase or lowercase. MATCH text text specifies a match pattern. Usage Guidelines The match pattern you specify in the MATCH command is used in searches subsequently conducted by the LIST and SCAN commands. Pattern matching is disabled until you enter a MATCH command.
Entering RDFSCAN Commands Enter the next RDFSCAN function you want: LIST 5 Record number: 1134 2004/06/04 11:31:50 \LAB2 $Z048 709 Log File Opened Altered $SYSTEM.SANFRAN.RDFLOG Record number: 1356 2004/06/04 13:22:51 \LAB2 $Z048 709 Log File Opened Altered $SYSTEM.SANFRAN.RDFLOG Record number: 1519 2004/06/04 15:28:22 \LAB2 $Z049 709 Log File Opened Altered $SYSTEM.SANFRAN.RDFLOG Record number: 3458 2004/06/04 18:17:53 \LAB2 $Z050 709 Log File Opened Altered $SYSTEM.SANFRAN.
Entering RDFSCAN Commands NOLOG NOLOG The NOLOG command disables LIST command copying that was previously enabled by a LOG command. NOLOG Usage Guidelines When you issue the NOLOG command, RDFSCAN stops copying records to the file specified in the LOG command. However, RDFSCAN continues to display at your terminal all records accessed by subsequent LIST commands. Examples The following command disables the copying of LIST command output: Enter the next RDFSCAN function you want: NOLOG File: $SYSTEM.
Entering RDFSCAN Commands SCAN SCAN The SCAN command scans a specific number of messages in the file and displays all of those in that range that contain the current match pattern. SCAN number number is the number of messages to scan within the log file.
Entering RDFSCAN Commands SCAN Examples The commands in this example specify displaying all messages in the file from record 1000 through record 2000 that contain the match pattern $AU02: Enter the next RDFSCAN function you want: AT 1000 File: $SYSTEM.SANFRAN.RDFLOG, current record: 1000, last record: 2955 Enter the next RDFSCAN function you want: MATCH *$AU02* File: $SYSTEM.SANFRAN.
10 Triple Contingency The triple contingency feature makes it possible for your applications to resume running with full RDF protection within minutes after loss of your primary system. Note. Replication of network transactions is not supported in conjunction with the triple contingency feature, nor is the replication of auxilary audit trails.
Triple Contingency How Does It Work? How Does It Work? In general, the triple contingency feature works as follows: • • • • • The RETAINCOUNT configuration parameter on both backup systems prevents the purger process from purging image trail files that might be needed for triple contingency recovery. If the primary system fails, you execute two takeovers: one on each backup system.
Triple Contingency Software Requirements Software Requirements You must be running the same release of RDF on all three systems (the primary system and both backup systems). The two RDF subsystems should be configured identically with respect to both backup systems.
Triple Contingency The RETAINCOUNT Configuration Parameter The RETAINCOUNT Configuration Parameter The purger RETAINCOUNT parameter specifies how many image trail files (including the one currently in use) must be retained on disk for each image trail. The default value for this parameter is two. The importance of this parameter is as follows.
Triple Contingency The COPYAUDIT Command RETAINCOUNT is set to three, the purger process can only purge AA000010 (it must keep AA000011 and AA000012 on disk). Thus, as long as the RTD times of the extractors on the two backup systems are less than 36 hours apart, the triple contingency protocol will work successfully.
Triple Contingency The COPYAUDIT Command where sys is the name of the other system (the backup system that has the most amount of audit information) and subvol is the name of the RDF control subvolume on that system. For the following discussion, assume that you have established two RDF configurations, as follows: RDF Configuration #1: \A ------------------> \B (The RDF control subvolume is A1 on both systems.
Triple Contingency COPYAUDIT Restartability COPYAUDIT Restartability The COPYAUDIT command is restartable. If an error condition aborts execution of a COPYAUDIT command, you merely correct the condition and then reissue the command. Upon restart, RDFCOM quickly checks the local system image files it had previously created to be sure they are still correct, deletes the file it was working on at the time of the error condition, and then resumes copying.
Triple Contingency Using ZLT to Achieve the Same Protection then continue application processing from system \B to system \C or from system \C to system \B within minutes of losing system \A. Using ZLT to Achieve the Same Protection To achieve the same result using the RDF/ZLT product you configure system \B as the ZLT standby node for both RDF subsystems #1 and #2. Upon losing system \A, you connect the remote mirrors to system \B and issue TAKEOVER commands on both systems \B and \C.
11 Subvolume- and File-Level Replication By default, RDF provides volume-level protection, wherein changes to all audited files and tables on each protected primary system data volume are replicated to an associated backup system data volume. RDF/IMP, IMPX, and ZLT also support subvolume- and file-level replication. To use this capability, you supply INCLUDE and EXCLUDE clauses when configuring updaters to identify specific subvolumes and files you want either replicated or not replicated. Note.
Subvolume- and File-Level Replication EXCLUDE Clauses EXCLUDE Clauses EXCLUDE clauses explicitly designate those subvolumes, files, and tables residing on a particular primary system data volume that you do not want replicated. All other audited files and tables on the particular volume are replicated. In the following example, changes to all audited files and tables on $DATA01 are replicated, except MMTEST10.
Subvolume- and File-Level Replication INCLUDE and EXCLUDE Processing INCLUDE and EXCLUDE Processing You can specify a maximum of 100 INCLUDE and EXCLUDE parameters for each volume, in any combination. When you specify both INCLUDE and EXCLUDE clauses for a given volume, the clauses are processed hierarchically, with the INCLUDE clauses processed first and EXCLUDE clauses processed second. Note.
Subvolume- and File-Level Replication Summary Examples Summary Examples Consider the following updater configuration example, where the primary system is \PRIMARY and the backup system is \BACKUP: SET SET SET SET SET ADD VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME CPUS 1:2 IMAGEVOLUME $IMAGE PRIORITY 185 PROCESS $MM01 UPDATEVOLUME $DATA01 $DATA01 In the above example, all audited files and tables on \PRIMARY.$DATA01 are replicated to \BACKUP.$DATA01.
12 Auxiliary Audit Trails In addition to the master audit trail (MAT), RDF/IMPX and ZLT support protection of up to 15 auxiliary audit trails. If you want to protect data volumes associated with an auxiliary audit trail, you must configure an auxiliary extractor and an auxiliary receiver for that trail. Thus, for each auxiliary audit trail, there will be one auxiliary extractor-receiver pair. Auxiliary Extractor An auxiliary extractor can only be configured to a single auxiliary audit trail.
Auxiliary Audit Trails Error conditions values of 1 through 15 must protect volumes associated with configured auxiliary audit trails AUX01 through AUX15, respectively. A master extractor and receiver are required, because TMF control records are required on the backup system in the event of an RDF takeover operation or a stopupdate-to-time operation. Auxiliary extractors and receivers are optional. For each extractor, there must be a corresponding receiver with the same atindex value.
Auxiliary Audit Trails Configuring Updaters Configuring Updaters The SET VOLUME command includes the following optional syntax: ATINDEX atindex where atindex is an integer value from 0 through 15 specifying the audit trail to which that data volume is mapped on the primary system. 0 specifies the MAT, and the data volume on the primary system must be mapped to the MAT.
Auxiliary Audit Trails Takeover Ramifications Takeover Ramifications If an auxiliary extractor is running behind the master extractor when you issue a TAKEOVER command, a transaction just committed on the primary system (and who’s commit record was received by the master receiver) could be backed out on the backup system. This could happen under the following circumstances: • • • In addition to the MAT, you have configured RDF to protect one or more auxiliary audit trails.
Auxiliary Audit Trails Using Expand Multi-CPU Paths To set up our three paths in processors 3, 5, and 7, for example, you would put matching Expand line-handlers in processor 3 on both systems, in processor 5 on both systems, and in processor 7 on both systems. Within RDF you would then configure processor 3 as the primary CPU for the master extractor and receiver, processor 5 as the primary CPU for the AUX01 extractor and receiver, and processor 7 as the primary CPU for the AUX02 extractor and receiver.
Auxiliary Audit Trails Using Expand Multi-CPU Paths HP NonStop RDF System Management Manual—529826-003 12- 6
13 Network Transactions The RDF/IMPX and RDF/ZLT products are able to guarantee backup database consistency for transactions that update data residing on more than one RDF primary system. RDF/IMPX and RDF/ZLT can map the volumes being protected to both the MAT and auxiliary audit trails. Note. Network transaction processing is currently not supported in configurations that use the triple contingency feature. You must use RDF/IMPX or RDF/ZLT to protect all databases open to network transactions.
Network Transactions Configuration Changes Configuration Changes To support network transactions, several configuration attributes and a configuration record have been added to the RDF configuration file. Order of Configuration Steps The order in which you perform the steps in the network configuration procedure is as follows: 1. Perform a cleanup operation purging the RDF control subvolumes on the network master and all non-network master subsystems. 2.
Network Transactions NETWORKMASTER Attribute NETWORKMASTER Attribute This attribute, located in the RDF configuration record, specifies whether or not the particular system is the master of the RDF network. Each RDF network has one, and only one, network master. To set this attribute, use the following RDFCOM command: SET RDF NETWORKMASTER {ON | OFF} When this attribute is set to OFF (the default value), the particular system is not the network master.
Network Transactions Network Configuration Record PRIMARYSYSTEM Network Attribute This is the name of a primary system. It is set by the following RDFCOM command: SET NETWORK PRIMARYSYSTEM system-name There is no default value. Each primary system within an RDF network must be unique within the network. An RDF network cannot contain two or more RDF subsystems with the same primary system (that is, it cannot contain RDF subsystems for \A to \B and \A to \C).
Network Transactions RDF Network Synchronizer (RDFNET) Process RDF Network Synchronizer (RDFNET) Process RDF/IMPX and RDF/ZLT include an RDF executable process, the RDFNET process, that can only be configured within a network master RDF subsystem (and can therefore only be started on the network master’s primary system). This process provides a synchronization point within the image trails of all backup systems in an RDF network.
Network Transactions RDF Takeovers Within a Network Environment RDF Takeovers Within a Network Environment With RDF/ZLT, no committed data from any primary system in the RDF network is lost. The discussions that follow regarding loss of data in a network takeover only apply to non-RDF/ZLT environments. If you have configured an RDF network and must initiate a takeover on a backup system in the network, then you must execute a takeover on all the backup systems in the network.
Network Transactions Takeover Phase 3 – Network Undo Takeover Phase 3 – Network Undo Note that with RDF/ZLT no undo operations are performed during the network undo phase because no committed transactions are undone. Phase three determines if network transaction data is missing from any of the backup systems in the RDF network, and marks those transactions to be undone on all of the systems.
Network Transactions Communication Failures During Phase 3 Takeover Processing have to go through 60 minutes of data to determine what must be undone due to data missing on the system that had fallen behind. A variation of the first example is that no extractors have fallen behind, but you have 25 systems in your RDF network.
Network Transactions The Effects of Undoing Network Transactions If an RDF event 888 is reported, then the specified File Recovery position is based on both phase 1 and phase 3 processing. Each system logs its own File Recovery position. While that position may differ from one backup system to the next, the logged position for any single system is correct.
Network Transactions The Effects of Undoing Network Transactions system \Y). Assume that network transactions originate on both \A and \B, and that they update data on both \A and \B. Assume further that each system also executes local, non-network, transactions. More specifically, assume that system \A (the network master) executes the following: 1. T10 (network transaction started on \A) 2. T11 (non-network transaction) 3. T11 commit 4. T10 commit 5. T12 (network transaction started on \A) 6.
Network Transactions The Effects of Undoing Network Transactions Assume that the primary system \B goes down after having transmitted the commit record for T13 to its backup system \Y. At that point \Y has the commits for T10, T13, T20, T21, T22 and T36. \Y only has to perform local undo (during which T12 is undone). The purger on \X (the network master) determines that the first transaction requiring network undo is T12 because that transaction was active on both \A and \B when \B went down.
Network Transactions Takeover and the RETAINCOUNT Value If we return to the issue of T13 in the example further above, note that the commit sequence differs on \A and \B. When the purger on \A determines that T12, T14, and T15 must be undone, it also determines that the results of T13 can be kept intact because T13 had to have completed on \B before T12. Why? The commit records on \A guarantee that both T12 and T13 did indeed commit.
Network Transactions Network Configurations and Shared Access NonStop SQL/MP DDL Operations Network Configurations and Shared Access NonStop SQL/MP DDL Operations Under certain circumstances after a shared access NonStop SQL/MP DDL operation, takeover network undo processing leads to an abort with database corruption. To avoid this problem, use the following protocol when performing shared access NonStop SQL/MP DDL operations in a network environment: 1.
Network Transactions RDF Re-Initialization in a Network Environment See Appendix C for the error messages that can occur during validation steps. Note. It is strongly recommended that you validate the configurations of all RDF subsystems in your RDF network with the RDFCOM VALIDATE CONFIGURATION command before you attempt to start any. This would then guarantee that your entire RDF network is configured correctly before you start any of the individual RDF subsystems.
Network Transactions RDF Networks and ABORT or STOP RDF Operations RDF Networks and ABORT or STOP RDF Operations If no network transactions are active, you can stop RDF on any subsystem at any time without affecting the other systems in an RDF network. The same is true with regard to an RDF monitor process aborting its RDF subsystem. There is, however, one exceptional situation. The RDFNET process runs on the network master’s primary system.
Network Transactions Sample Configurations committed T10 at 12:05. Assume further that you had previously issued a stop-updateto-time operation on system \A, specifying 12:01 P.M. When the stop-update-to-time operation completes, the data for T10 is backed out of system \A’s backup database because T10 committed after 12:00 P.M.
Network Transactions Sample Network Master Configuration SET RECEIVER SLOWMODE OFF SET RECEIVER PROCESS $MR41 ADD RECEIVER SET SET SET SET SET ADD PURGER PURGER PURGER PURGER PURGER PURGER CPUS 3:2 PRIORITY 185 PROCESS $RP40 RETAINCOUNT 5 PURGETIME 60 SET IMAGETRAIL ATINDEX 0 ADD IMAGETRAIL $DATA06 SET SET SET SET ADD NETWORK NETWORK NETWORK NETWORK NETWORK PRIMARYSYSTEM \RDF04 BACKUPSYSTEM \RDF06 REMOTECONTROLSUBVOLUME RDF04 PNETTXVOLUME $DATA07 SET SET SET SET ADD NETWORK NETWORK NETWORK NETWORK
Network Transactions Sample Non Network Master Configuration Sample Non Network Master Configuration The configuration that follows is for an RDF subsystem running from \RDF05 to \RDF06, where the network master is \RDF04: SET SET SET SET SET SET SET SET SET ADD RDF RDF RDF RDF RDF RDF RDF RDF RDF RDF SOFTWARELOC $SYSTEM.
Network Transactions RDFCOM STATUS Display SET SET SET ADD NETWORK PRIMARYSYSTEM \RDF04 NETWORK BACKUPSYSTEM \RDF06 NETWORK REMOTECONTROLSUBVOLUME RDF04 NETWORK SET SET SET SET SET SET ADD VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME ATINDEX 0 CPUS 1:2 IMAGEVOLUME $DATA06 PRIORITY 185 PROCESS $RU53 UPDATEVOLUME $DATA08 $DATA08 RESET VOLUME RDFCOM STATUS Display The following illustrates the RDFCOM STATUS display for a network master (note that it includes the RDFNET process).
Network Transactions RDFCOM STATUS Display HP NonStop RDF System Management Manual—529826-003 13-20
14 Process-Lockstep Operation The RDF/IMPX and RDF/ZLT products include the process-lockstep operation, which is process-based. That is, when a process invokes the lockstep operation for a business transaction, the process must wait until all audit records associated with that business transaction are safely stored in image trails on the backup system before continuing.
Process-Lockstep Operation Starting a Lockstep Operation The RDF/IMPX and RDF/ZLT independent product CDs include the following files associated with the lockstep capability: SLOCKCOB Sample code for invoking the DoLockstep procedure from a COBOL 85 program. LSGO RDF lockstep gateway object code. LSLIBTO DoLockstep procedure object code. FDOLOCK Forward declarations of the DoLockstep procedure call.
Process-Lockstep Operation Invoking DoLockStep by way of TAL Invoking DoLockStep by way of TAL The lockstep software provided with the RDF/IMPX and RDF/ZLT products includes a TAL header file containing the DoLockstep procedure declaration and the corresponding object file. You must modify your program to source in the header file FDOLOCK. For example, include the following lines of code where you add procedure declarations.
Process-Lockstep Operation The Lockstep Transaction backup nodes should go down after the application has called DoLockstep, the application will wait until the line comes back up and the lockstep audit data is safely stored. DoLockstep returns one of the following three states: LockStepDone (value is 31428) All audit data associated with the lockstep operation has been safely stored in the image trail on the backup system.
Process-Lockstep Operation Multiple Concurrent Lockstep Operations SET RDF LOCKSTEPVOL volume Where volume is a volume name and the volume is configured to the MAT. Additionally you must ensure that you add an updater to protect either the volume or the lockstep file. The full file name is volume.ZRDFLKSP.. If you only need to protect this file on this volume, then INCLUDE it when you configure the updater for the volume.
Process-Lockstep Operation The Lockstep Gateway Process The Lockstep Gateway Process The RDF lockstep gateway process is managed by the Subsystem Control Facility (SCF). To start a lockstep gateway process, you must create and execute an SCF script file. The recommended script settings are: ASSUME PROCESS $ZZKRN ADD #LSGO, NAME $ZLSGW, CPU FIRSTOF (1,2,3), PROGRAM volume.subvolume.
Process-Lockstep Operation Disabling Lockstep Disabling Lockstep To disable lockstep processing: 1. Change ENABLE to DISABLE in the STARTUPMSG attribute script. 2. Manually delete the RDF lockstep gateway process from SCF. 3. Run the changed SCF script. When SCF restarts the gateway, lockstep processing is disabled. Thus, if your application calls DOLOCKSTEP, the gateway will return control immediately to the application without doing lockstep processing.
Process-Lockstep Operation Lockstep Performance Ramifications Lockstep Performance Ramifications By definition, a lockstep operation will increase the response time of your application because, after having invoked DoLockstep, the application must wait for the data to become safely stored in the backup system’s image trail. The extractor and receiver processes have been streamlined to facilitate lockstep processing, but a short delay is unavoidable.
Process-Lockstep Operation Lockstep Operation Event Messages 2 A STARTUPMSG argument is missing for the lockstep gateway. Cause. You are missing either the ENABLE/DISABLE argument, or you have not specified the name of the RDF extractor. Effect. The lockstep gateway stops. Recovery. In your SCF script for starting the lockstep gateway, you must specify either ENABLE or DISABLE and the RDF extractor process name with the STARTUPMSG attribute. Note that the process name must not include a node name.
Process-Lockstep Operation Lockstep Operation Event Messages 5 The lockstep gateway received error errnum from the RDF extractor procname. errnum is a file-system error number. procname is the name of the process that is in use. Cause. When the gateway attempted to obtain the name of the RDF lockstep file from the extractor, it received the indicated error.
Process-Lockstep Operation Lockstep Operation Event Messages 7 Open error errnum on filename. errnum is a file-system error number. filename is the name of a lockstep file. Cause. The lockstep gateway received the specified error while attempting to open the specified lockstep file. Effect. The lockstep gateway stops. Recovery. Correct the error condition and restart the lockstep gateway. 8 Error errnum received when attempting to obtain info on file filename. errnum is a file-system error number.
Process-Lockstep Operation Lockstep Operation Event Messages Cause. The lockstep gateway received the specified error while attempting to update the specified lockstep file. Effect. The lockstep gateway stops. Recovery. Correct the error condition and restart the lockstep gateway. 10 The RDF lockstep file filename has an incorrect file code. filename is the name of a lockstep file. Cause. The specified lockstep file has the wrong file code. Effect. The lockstep gateway stops. Recovery.
Process-Lockstep Operation Lockstep Operation Event Messages Recovery. This is an internal error, but the gateway is restarted. If the problem persists, contact the Global Customer Support Center (GCSC) or your service provider. 13 Invalid data returned from the RDF Extractor. Cause. The lockstep gateway sent a request to the RDF extractor, and the latter returned invalid data. Effect. The lockstep gateway stops. Recovery. This is an internal error, but the gateway is restarted.
Process-Lockstep Operation Lockstep Operation Event Messages 16 Error errnum encountered while responding to the applications that called DOLOCKSTEP. errnum is a file-system error number. Cause. The gateway encountered the included error while trying to reply to the calling applications. Effect. The lockstep gateway stops. Recovery. This is an internal error, but the gateway is restarted. If the problem persists, contact the Global Customer Support Center (GCSC) or your service provider.
Process-Lockstep Operation Lockstep Operation Event Messages 19 Invalid process name procname for lockstep gateway. procname is the invalid process name. Cause. The required process name is $ZLSGW, but you supplied the specified name in your SCF script. Effect. The lockstep gateway stops. Recovery. You must change your SCF script and use the required process name. 20 PROCESS_GETINFO_ error errnum on lockstep gateway. errnum is a file-system error number. Cause.
Process-Lockstep Operation Lockstep Operation Event Messages 22 Open error errnum on RDF master extractor procname. errnum is a file-system error number. procname is the name of an extractor process. Cause. The specified error was returned when the lockstep gateway attempted to open the RDF extractor. Effect. The gateway continues trying to open the extractor and will repeat this message every five minutes until the open is successful. Recovery. This is an informational message.
Process-Lockstep Operation Lockstep Operation Event Messages 24 Error errnum returned when attempting to lock the lockstep file filename. errnum is a file-system error number. filename is the name of a lockstep file. Cause. The specified error was returned when the lockstep gateway attempted to lock the specified file. Effect. The lockstep gateway stops. Recovery. SCF automatically restarts the gateway.
Process-Lockstep Operation Lockstep Operation Event Messages 27 Lockstep Gateway Started. Cause. The lockstep gateway is started. Effect. The lockstep gateway continues its initialization activity. Recovery. This is an informational message; no recovery is required. 28 RDF extractor procname responded with error errnum to lockstep request. procname is the name of an extractor process. errnum is a file-system error number. Cause.
Process-Lockstep Operation Lockstep Operation Event Messages 30 ENDTRANSACTION error errnum encountered on lockstep transaction. errnum is a file-system error number. Cause. The specified error was encountered on ENDTRANSACTION. Effect. If the error is retryable, the lockstep gateway starts a new transaction. If the error is unexpected, the gateway stops. Recovery. This is an informational error, unless the gateway stops.
Process-Lockstep Operation Lockstep Operation Event Messages HP NonStop RDF System Management Manual—529826-003 14-20
15 NonStop SQL/MX and RDF RDF supports replication of NonStop SQL/MX user tables (file code 550) and indexes (file code 552). These operations are supported in much the same way as they are with NonStop SQL/MP, and the same types of data and DDL operations are replicated.
NonStop SQL/MX and RDF Obtaining ANSI Object Names From Updater Event Messages Obtaining ANSI Object Names From Updater Event Messages Updater event messages list Guardian filenames. If an updater generates an event against an MX object (subvolume name starts with ZSD), you can obtain the ANSI name of the object by issuing a FUP INFO , DETAIL command.
NonStop SQL/MX and RDF Creating NonStop SQL/MX Primary and Backup Databases from Scratch Where catalog is the local catalog, node is the remote system where you want the local catalog registered, and volume is where the local catalog is to be registered on the remote system. For example, the following command (if executed on the primary system) registers the primary catalog on volume $DATA00 of the backup system: REGISTER CATALOG pcat ON \bnode.
NonStop SQL/MX and RDF Creating NonStop SQL/MX Primary and Backup Databases from Scratch For the rest of this procedure assume that the above query returns the value ZSDXYZ3A. 5. Create the schema on the backup system using the same schema name and the same subvolume name as on the primary system. Because RDF is replicating based on the underlying Guardian file locations, you must use the LOCATION clause.
NonStop SQL/MX and RDF Creating NonStop SQL/MX Primary and Backup Databases from Scratch Now, the full CREATE TABLE statement for CAT.SCH.TAB1, including the full Guardian names of the partitions, can be displayed in MXCI by using the command: SHOWDDL PCAT.SCH.TAB1; Assume the system generates the following Guardian file names: $DATA02.ZSDXYZ3A.KQY8KY00 $DATA03.ZSDXYZ3A.KQY8RK00 $DATA04.ZSDXYZ3A.
NonStop SQL/MX and RDF Creating a NonStop SQL/MX Backup Database From an Existing Primary Database the updater will wait until you have created such a file. At this point, you will have to correct the naming problem as described under Correcting Incorrect NonStop SQL/MX Name Mapping. When you have completed Steps 6 and 7 for each table and index, the primary database is ready for transaction activity, and the backup database is ready for RDF to replicate that transaction activity.
NonStop SQL/MX and RDF Creating a NonStop SQL/MX Backup Database From an Existing Primary Database 3. If you want each catalog to be seen from both systems, register your primary and backup catalogs. See Step 3 in Creating NonStop SQL/MX Primary and Backup Databases from Scratch, above, for instructions and examples. 4. Use the MXGNAMES utility to generate the LOCATION clauses for the RESTORE utility. To generate a location clause for a single table on the primary node called CAT.SCH.
NonStop SQL/MX and RDF Online Database Synchronization With NonStop SQL/MX Objects For example, assume you have the objects on your primary system that have the following fully qualified Guardian names: \pnode.$DATA01.ZSDABCDEF.FILE100 \pnode.$DATA02.ZSDABCDEF.FILE100 \pnode.$DATA03.ZSDABCDEF.FILE100 For the RESTORE command, you must name the qualified Guardian filenames of your source objects and also the qualified Guardian filenames of your target objects in the LOCATION clause. LOCATION ( \pnode.
NonStop SQL/MX and RDF Creating the Fuzzy Copy on the Primary System 2. Create a temporary schema for your temporary catalog. Follow the instructions given in Step 2 of the procedure Creating a NonStop SQL/MX Backup Database From an Existing Primary Database, above (but follow those instructions on your primary system instead of on the backup system). Note, the name of the temporary schema must be identical to the name of the schema whose objects you want replicated.
NonStop SQL/MX and RDF Creating the Fuzzy Copy on the Primary System 8. If you want each catalog to be seen from both systems, register your primary and backup catalogs. To register the primary catalog on the backup system, issue a REGISTER CATALOG command on the primary system. To register the backup catalog on the primary system, issue a REGISTER CATALOG command on the backup system. The format of the REGISTER CATALOG command is: REGISTER CATALOG catalog ON node.
NonStop SQL/MX and RDF Creating the Fuzzy Copy on the Backup System Creating the Fuzzy Copy on the Backup System The advantage of this method is that it eliminates the use of temporary objects as well as tape handling because you create your backup objects directly on the backup system. The disadvantage is that it requires you to load the data from your primary objects to your backup objects over Expand lines, which might take longer than the alternate method given above if the data is great in size.
NonStop SQL/MX and RDF Offline Synchronization for a Single Partition Offline Synchronization for a Single Partition You must first determine the key ranges for each of your partitions. For the partition that you want to synchronize, find out whether a partition already exists on the backup system. If a partition exists, then there are two methods to synchronize the backup partition to the primary: directly and indirectly. Directly From the Primary to the Backup 1.
NonStop SQL/MX and RDF Backup Partition Does Not Already Exist 4. Now load only the rows from the primary partition that you want synchronized into the temporary partition: INSERT INTO backup-table SELECT * FROM primary-table WHERE key-column >= 'F' AND key-column < 'K'; 5. Use Backup to put the temporary table on tape. 6. Create a catalog on the backup system to correspond to the temporary catalog on the primary system. 7.
NonStop SQL/MX and RDF Online Synchronization for a Single Partition Online Synchronization for a Single Partition You must first determine the key ranges for each of your partitions. Follow the steps described in Online Database Synchronization With NonStop SQL/MX Objects, above. Note that in this case, however, you are only dealing with a single partition.
NonStop SQL/MX and RDF Primary and Backup ANSI Schema Names Not the Same Primary and Backup ANSI Schema Names Not the Same If you created the primary and backup schemas to have different ANSI schema names, RDF replication can proceed, but you must remember that the backup database has a different schema name in the event of a planned or unplanned outage that requires you resume transaction activity on the backup system.
NonStop SQL/MX and RDF Consideration for Creating Backup Tables Consideration for Creating Backup Tables Currently, you cannot use the CREATE LIKE statement to create backup or temporary tables because CREATE LIKE does not preserve the original Guardian file names that are essential for RDF. At some point in the future when ANSI names are supported, CREATE LIKE will be a viable means of creating backup or temporary tables, but until then the following discussion has the utmost significance.
NonStop SQL/MX and RDF Restoring to a Specific Location Restoring to a Specific Location See the RESTORE section of the Guardian Disk and Tape Utilities Reference Manual for the syntax of the RESTORE utility. The LOCATION option allows you to change the physical location of NonStop SQL/MX objects as they are restored. The LOCATION option is used to specify one or more mappings. If you specify LOCATION, you cannot specify PARTONLY ON.
NonStop SQL/MX and RDF Example 6. Table and Index information: Table or Index Name Guardian Names for partitions and indexes PCAT.MYSCHEMA.MYTABLE1 \P.$data01.ZSDAAAAA.HEBFRW00 \P.$data02.ZSDAAAAA.HEBFRX00 \P.$data03.ZSDAAAAA.HEBFRY00 \P.$data02.ZSDAAAAA.YREWPO00 PCAT.MYSCHEMA.MYINDEX1 PCAT.MYSCHEMA.MYTABLE2 PCAT.MYSCHEMA.MYINDEX2 PCAT.MYSCHEMAX.MYTABLE1 \P.$data01.ZSDAAAAA.GABCDE00 \P.$data02.ZSDAAAAA.GABCDF00 \P.$data03.ZSDAAAAA.GABCDG00 \P.$data02.ZSDAAAAA.YZZWPO00 PCAT.MYSCHEMAX.MYINDEX1 \P.
NonStop SQL/MX and RDF Comparing NonStop SQL/MX Tables As described under Step 4 of Creating a NonStop SQL/MX Backup Database From an Existing Primary Database, above, you can use the MXGNAMES utility to automatically generate the correct LOCATION clauses, substituting the backup node name as needed. However, you must remap any non-matching volume names in these locations manually.
NonStop SQL/MX and RDF Comparing NonStop SQL/MX Tables HP NonStop RDF System Management Manual—529826-003 15-20
16 Zero Lost Transactions (ZLT) Zero Lost Transactions (ZLT), functionality that is available only with the RDF/ZLT product, ensures that no transactions that commit on the primary system are lost on the RDF backup system if that primary system is downed by an unplanned outage. RDF achieves this though the use of remote mirroring for the relevant TMF audit-trail volume(s).
Zero Lost Transactions (ZLT) How It Works How It Works One mirror of each audit-trail disk volume is removed to a remote location from the local mirror. The distance is limited by the chosen disk technology and acceptable communications latency. Thus, each audit-trail volume is still mapped to a mirrored pair of disks, but one of the disks is physically removed. For the remote mirror, an alternate cable must be present so that this mirror can be attached to a standby system in the event of a takeover.
Zero Lost Transactions (ZLT) How It Works Figure 16-2 shows the configuration where a single system serves as both the standby and backup systems, and the remote mirror is located at an intermediate site. Figure 16-2.
Zero Lost Transactions (ZLT) How It Works Figure 16-3 shows the configuration where individual standby and backup systems are located at separate sites. Figure 16-3.
Zero Lost Transactions (ZLT) Using CommitHoldMode all of the audit records that were generated on the primary system prior to the system failure, and no committed data is lost. Note. You must connect the remote mirrors to the standby system before starting the RDF takeover operation; otherwise, the takeover aborts because RDF cannot find the disks you configured in RDF for remote mirroring. In such a case, you should connect the disks and then restart the RDF takeover operation.
Zero Lost Transactions (ZLT) Hardware Setup If ZLT protection is critical to your disaster recovery plan, specify ON TIMEOUT CRASH. Crashing TMF under these circumstances provides ZLT protection. If it is important to resume transaction processing on the primary system, specify ON TIMEOUT SUSPEND. Suspending commit-hold mode under these circumstances, however, deprives you of ZLT protection should you lose the primary system to some unplanned outage.
Zero Lost Transactions (ZLT) RDF Configuration Attributes RDF Configuration Attributes RDF Remote Mirror Configuration When declaring the attributes of the RDF configuration record, you use the following optional attribute to specify whether ZLT is enabled or disabled: SET RDF REMOTE MIRROR [ ON | OFF ] The default is off. If this attribute is off, normal RDF operations are unchanged, as is execution of the RDF TAKEOVER command.
Zero Lost Transactions (ZLT) Extractor Audit Trail Configuration Extractor Audit Trail Configuration When configuring RDF for ZLT, you must add the complete set of audit-trail volumes to which RDF-protected data volumes are configured. For example, if your RDF configuration only protects data volumes configured to the master audit trail (MAT), you must specify all audit-trail volumes that are configured in TMF for the MAT (active, overflow, and restore).
Zero Lost Transactions (ZLT) ZLT Takeover Operations ZLT Takeover Operations If ZLT is configured and enabled when a TAKEOVER command is issued on the backup system, the overall takeover operation executes in two phases. Note. Before issuing the TAKEOVER command, you must have connected the remote mirrors to the standby system. When the remote mirrors are connected to the standby system, the audit records on the remote mirrors have no relationship to the audit trail on the standby system.
Zero Lost Transactions (ZLT) Phase 2 (Takeover Processing) Phase 2 (Takeover Processing) The initial part of Phase 2 takeover processing is performed by the purger in building the undo lists. When an updater reaches the end-of-file of its image trail, it asks the purger for an undo list. (The purger cannot start building the undo lists until all receivers have finished their ZLT processing.
Zero Lost Transactions (ZLT) 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.
Zero Lost Transactions (ZLT) Recovering the Primary System After an RDF ZLT Takeover The file marked with the question mark must be fixed. Use the SNOOP FIXUPEOF command to reset the crashopen flag. Then use SNOOP READAUDIT to read the final record. Note that you cannot use the MERGE option when specifying the name of the audit-trail file. Because the TMF product is not started, attempting to use the MERGE option results in an error.
Zero Lost Transactions (ZLT) ZLT and RDF Networks 4. Start TMF. 5. Initiate TMF file recovery with the MAT position option, where the position you specify is the MAT position reported in the RDF 888 event on the backup system. Note that the RDF event 888 is logged when the takeover operation completes. 3. For information about how to return your application processing to the former primary system, see Carrying Out a Planned Switchover in section 5.
Zero Lost Transactions (ZLT) SQL Shared Access DDL Operations SQL Shared Access DDL Operations Normal support for SQL shared access DDL operations is provided during ZLT takeover operations: • • The updaters are guaranteed to stop at the correct locations. If some of the updaters terminated prematurely while a shared access operation is in the system, only those that had not completed the task are restarted during the next takeover operation.
A RDF Command Summary The syntax rules for the RDFCOM and RDFSCAN commands, explained in detail in Section 8, Entering RDFCOM Commands and Section 9, Entering RDFSCAN Commands respectively, are summarized in this appendix.
RDF Command Summary ADD The ADD command applies configuration parameter values for the specified process or other object to the RDF configuration file. Where Issued: Primary system only. Security: Super-user group member ADD {RDF {MONITOR {EXTRACTOR {RECEIVER {IMAGETRAIL $volume {PURGER {RDFNET {NETWORK {[VOLUME] $volume {TRIGGER trigger-type } } } } } } } } } } ALTER The ALTER command changes the setting of the specified parameter in the RDF configuration file to the supplied value.
RDF Command Summary COPYAUDIT The COPYAUDIT command copies missing audit information from the backup system that has the most to the backup system that has the least. This command is only for use with the triple contingency feature. Where Issued: Backup system only (the backup system with the least amount of audit information). Security: Super-user group member with remote password from the primary system to the backup.
RDF Command Summary FC The FC command enables you to selectively examine, edit, or repeat a previously issued RDFCOM command. Where Issued: Primary or backup system. Security: Any user. {FC} [text] {? } [text] {! } [text] HELP The HELP command displays explanatory text about RDFCOM commands and RDF messages. Where Issued: Primary or backup system. Security: Any user.
RDF Command Summary INFO The INFO command displays the current configuration parameter values from the configuration file for the specified process or other object. Where Issued: Primary or backup system. Security: Any user.
RDF Command Summary OPEN The OPEN command specifies the RDF control subvolume to which subsequent commands in this RDFCOM session apply. Where Issued: Primary or backup system. Security: Any user. OPEN control-subvolume OUT The OUT command redirects the output of the current RDFCOM session to the specified device or file. Where Issued: Primary or backup system. Security: Any user. OUT [\system.][$volume.][subvolume.
RDF Command Summary SET EXTRACTOR The SET EXTRACTOR command sets the designated configuration parameters for the extractor process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary SET MONITOR The SET MONITOR command sets the designated configuration parameters for the monitor process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary SET PURGER The SET PURGER command sets the designated configuration parameters for the purger process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary SET RDF The SET RDF command sets the designated RDF global configuration parameters to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary SET RECEIVER The SET RECEIVER command sets the designated configuration parameters for the receiver process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary SET VOLUME The SET VOLUME command sets the designated configuration parameters for an updater process to the supplied values within the RDF configuration memory table. The supplied values are not applied to the RDF configuration file, however, until you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary START RDF The START RDF command starts the RDF subsystem. Where Issued: Primary system only. Security: Super-user group member with remote password from the primary system to the backup. START RDF [,UPDATE {ON | OFF}] START UPDATE The START UPDATE command starts all updater processes on the backup system. Where Issued: Primary system only. Security: Super-user group member with remote password from the primary system to the backup.
RDF Command Summary STOP RDF The STOP RDF command shuts down the RDF subsystem. Where Issued: Primary or backup system (can be issued on the backup system only when all communications lines to the primary system are down). Security: Super-user group member with remote password from the primary system to the backup. STOP RDF { [, DRAIN ] } { [, REVERSE ] } STOP SYNCH The STOP SYNCH command is used as part of the online database synchronization protocol.
RDF Command Summary UNPINAUDIT The UNPINAUDIT command unpins TMF audit trail files on the primary system. Where Issued: Primary system only. Security: Super-user group member. UNPINAUDIT VALIDATE CONFIGURATION The VALIDATE CONFIGURATION command validates the parameters in the RDF configuration file. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary RDFSCAN Commands RDFSCAN Commands Command to Run RDFSCAN RDFSCAN runs under the Guardian user interface (normally the TACL command interpreter) to the NonStop™ Kernel operating system. The RDFSCAN command starts an RDFSCAN session that lets you enter RDFSCAN commands interactively, noninteractively, or through a command file. Where issued: primary or backup system. Security: Any user.
RDF Command Summary RDFSCAN Commands HELP The HELP command displays the syntax of RDFSCAN commands or introductory information about the RDFSCAN utility. HELP [ ALL ] [ INTRO ] [ command ] LIST The LIST command displays a specified number of log messages that contain the current match pattern. LIST number LOG The LOG command selects a file to which subsequent LIST commands copy their output in addition to the standard output device.
RDF Command Summary File Names and Process Identifiers File Names and Process Identifiers File names and process identifiers sometimes appear as parameters in RDFCOM and RDFSCAN commands. These names typically identify objects such as disk files, log devices, and processes. Reserved File Names Subvolume names that begin with the letter “Z” are reserved. You should not choose such names when configuring RDF objects. Disk File Names The syntax for a file name that identifies a disk file is: [\system.
B Additional Reference Information This appendix presents additional reference information about: • • • • Default values and parameter ranges for RDF configuration parameters Sample configuration file content, useful in OBEY commands for starting the RDF subsystem The RDFSNOOP utility that examines RDF exception files RDF system files: their type and purpose The following process names are also reserved: $X* , $Y* , and $Z*.
Additional Reference Information Default Configuration Parameters Default Configuration Parameters This table lists the default values and allowable ranges for RDF configuration parameters. Parameter Default Value(s) MIN MAX RDF BACKUPSYSTEM BACKUPSYSTEM value used on INITIALIZE RDF n.a. n.a. RDF LOGFILE $0 n.a. n.a. RDF NETWORK off n.a. n.a. RDF OWNER none n.a. n.a. RDF REPLICATEPURGE off n.a. n.a. RDF SOFTWARELOC $SYSTEM.RDF n.a. n.a.
Additional Reference Information Default Configuration Parameters Parameter Default Value(s) MIN MAX PURGER RETAINCOUNT 2 2 5000 VOLUME ATINDEX 0 0 15 VOLUME CPUS 0:1 0 15 VOLUME PRIORITY 160 10 199 VOLUME UPDATEVOLUME $SYSTEM n.a. n.a. VOLUME IMAGEVOLUME RECEIVER RDFVOLUME n.a. n.a.
Additional Reference Information Sample Configuration File Sample Configuration File The following is a sample OBEY command file for configuring the RDF subsystem for the first time. Comment lines begin with the | symbol and are ignored by RDFCOM. | | | | *** *** Remove all information from the current RDF configuration *** file. *** INITIALIZE RDF, BACKUPSYSTEM \LONDON, SUFFIX 1 ! | *** | *** Set the monitor parameters.
Additional Reference Information | | | | *** *** Set the receiver parameters. *** $REC is the name of the receiver process. *** SET SET SET SET SET | | | | Sample Configuration File RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER CPUS EXTENTS PRIORITY RDFVOLUME PROCESS 1:2 (1000,1000) 165 $GOLD $REC *** *** Add the receiver parameters to the *** RDF configuration file. *** ADD RECEIVER | | | | *** *** Set the purger parameters. *** $PRG is the name of the purger process.
Additional Reference Information | | | | | | | | | *** *** *** *** *** *** *** *** *** SET SET SET SET SET | | | | | Sample Configuration File Set the updater parameters for the second volume to be protected by the RDF product. $U02 is the name of this updater. Volume $DB2 on the backup node corresponds to the volume $DB02 on the primary node. This updater will use the secondary image trail SECIT2.
Additional Reference Information RDFSNOOP Utility RDFSNOOP Utility RDFSNOOP is a utility that is used to examine image file records pointed to by RDF exception files. RDFSNOOP does not have a set of commands, but it does prompt you for information about the exception files. To use RDFSNOOP, enter RDFSNOOP at the TACL prompt: > RDFSNOOP RDFSNOOP prompts you for the RDF control subvolume name. Input control subvolume name: Enter the subvolume name.
Additional Reference Information RDF System Files RDF System Files The following files are created by the RDF subsystem and used by RDF processes: • Configuration file This is a key-sequenced file with record length 4062. The configuration file contains an internal representation of the configuration parameters that are set through RDFCOM commands. The configuration file resides on both the primary and backup node; on both nodes, the configuration file is named: $SYSTEM.control-subvolume.
Additional Reference Information • RDF System Files RDFLOCK file The RDFLOCK file is an unstructured, semaphore lock file that exists only to protect RDFCOM from performing multiple critical operations at the same time. A semaphore lock is the software mechanism that prevents other processes from executing certain functions until the process that initiated the semaphore lock has finished its processing.
Additional Reference Information • RDF File Codes ZRCVnn files One file is created for each auxiliary receiver in your RDF configuration, and the nn is the two-digit ATINDEX of the receiver. These files store information about SQL Shared Access DDL operations involving files protected by RDF. The ZRCVnn files reside on the backup node and are named $SYSTEM.control-subvolume. ZRCVnn.
C Messages This appendix describes all messages generated by RDF.
Messages RDF Messages RDF Messages RDF messages, unlike RDFCOM and RDFSCAN messages, do not appear on your terminal or workstation screen. Instead, RDF sends these messages to the configured EMS event log (collector). You specify the EMS event log by using the SET RDF command described in Section 8, Entering RDFCOM Commands. You can change the EMS event log while RDF is running. The following example shows part of an EMS event log.
Messages RDF Messages Effect. Variable; depends upon which file-system error occurred. Recovery. If this message is issued by an updater process, filename is the name of the volume on the primary system for which the updater is responsible. In such a case consult Table 5-1 in the RDF manual to determine the appropriate recovery actions. 701 Error error communicating with processname error is the file-system error number that identifies the specific error. processname is the name of the affected process.
Messages RDF Messages 703 Still waiting on purger for undo pass Cause. The updater has sent a request for permission to read the undo list, but the purger has not yet given the updater permission. Effect. The updater waits until the purger has completed building the undo list. Recovery. This is an informational message. No recovery is required, unless the purger is reporting problems. 704 Updaters stopped before stop-update-to-time has completed Cause.
Messages RDF Messages The receiver retries OPEN calls for the image files if the error is 11 (file missing), 12 (file in use), or 59 (file is bad). Those errors might occur while the image file is being restored to disk. Recovery. If this message is issued by an updater process, consult Table 5-2 in the RDF manual to determine the appropriate recovery actions. 706 RDF monitor shutdown complete Cause.
Messages RDF Messages Recovery. This is an internal error. Contact your service provider. 709 Logfile opened or altered filename filename is the name of the new EMS event log (collector). Cause. An RDF process has successfully changed the logfile to the specified EMS Event Collector. Effect. Messages are now logged to the new collector. Recovery. This is an informational message; no recovery is required. 710 TMP is inaccessible Cause.
Messages RDF Messages 712 Process creation error nnn nnn, file filename nnn nnn are the upper and lower bytes, respectively, of the status code reported by the NEWPROCESS procedure. filename is the name of the program file that was to be executed. Cause. The monitor encountered an error while attempting to create an RDF process.
Messages RDF Messages Recovery. Consult the description of the NEWPROCESS procedure in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure. Once the underlying cause is corrected, the backup process can be created. 714 CHECKPOINT Failure - backup comm error error error is the file-system error number that identifies the specific error. Cause. A call to the checkpoint procedure failed, and the backup process of a NonStop process pair is still running.
Messages RDF Messages 717 Primary processor down Cause. The primary CPU of a NonStop process pair has stopped. Effect. The backup process takes over, but not in fault-tolerant mode. The primary process will be re-created after its CPU is reloaded. Recovery. Reload the downed processor. 718 Switched to original primary processor Cause.
Messages RDF Messages 720 Audit trail file single block missing Cause. The extractor detected an error in block sequence numbers in the TMF audit trail. The sequence numbers show that a single block is missing. Effect. This is only a warning. Normal processing continues. It is possible, however, that the backup database is no longer consistent with the primary database. Recovery. This is an informational message; no recovery is required. Tell your database administrator that this error occurred.
Messages RDF Messages 723 Irrecoverable error on audit-trail file filename at RBA rba filename is the name of the audit-trail file that contained the error. rba is the relative byte address where the error occurred in the audit-trail file. Cause. The extractor encountered an irrecoverable error at the designated relative byte address (rba) in the designated TMF audit-trail file. This message indicates an internal RDF or TMF error. Effect. This is a catastrophic error; the extractor abends, and RDF stops.
Messages RDF Messages Recovery. If UPDATE was OFF at the time of the RDF TAKEOVER, then a second RDF TAKEOVER operation is automatically started, and no recovery is required. Otherwise, you must restart the takeover operation with the RDFCOM TAKEOVER command. 726 Updater did not complete the TAKEOVER vol> vol => vol are the volume on the primary node that the updater is protecting and the corresponding volume to which it is writing on the backup node. Cause.
Messages RDF Messages 729 Attempt to alter process priority failed priority priority is the priority requested for the process. Cause. An attempt to alter the priority of an RDF process to the indicated priority has failed. Effect. The process continues to run at its current priority. Recovery. This is an informational message; no recovery is required. Reissue the ALTER command. 730 Process priority altered priority priority is the priority requested for the process. Cause.
Messages RDF Messages filename is the name of the exception file that the updater was trying to create. Cause. An updater process encountered an error while attempting to create an exception file. The message includes the file-system error number and the name of the exception file that the updater was trying to create. Effect. This is a catastrophic error; the updater abends, and RDF stops. Recovery. Determine the cause of the error, correct the condition, and then restart RDF.
Messages RDF Messages processname is the name of the process that sent the message. programfile is the name of the object file from where the process that sent the message was started. Cause. An RDF process received a message that does not apply to it. This message is a warning that indicates a possible problem in the configuration file, a programming problem within RDF, or that a process outside of RDF tried to communicate with an RDF process.
Messages RDF Messages 2. to use for File Recovery to a MAT position on the primary system Recovery. This is an informational message; no recovery is required. 736 Waiting to obtain FILEINFO on file filename, error error error is the file-system error number that identifies the specific error. filename is the name of the file that caused the error. Cause. The updater could not obtain information about the specified Guardian file.
Messages RDF Messages 738 RDF extractor synch established SNO sno RBA rba sno is the sequence number of the TMF Master Audit Trail (MAT) for which the synchronization point was established. rba is the relative byte address of the synchronization point. Cause. This message indicates that the receiver has sent the extractor a starting position in the TMF audit trail, and that the extractor has thereby become synchronized with the receiver. Effect. Extractor is synchronized with the receiver. Recovery.
Messages RDF Messages error is the file-system error number that identifies the specific error. Cause. This warning message is issued when a create operation for the primary partition of a partitioned file must map one or more of the file’s secondary partitions to a volume that does not match any of the volumes protected by RDF on the primary node.
Messages RDF Messages Effect. The extractor abends, thereby stopping the other RDF processes. Recovery. Save the SAVEABEND file, the audit-trail file, and consult your service provider. You must reinitialize RDF. 743 Catastophic error encountered Cause. A fatal error occurred in RDF. Effect. RDF stops. Recovery. Restart RDF and contact your service provider. 744 FILEINFO obtained on file filename filename is the name of the file that caused the error. Cause.
Messages RDF Messages Effect. RDF stops. Error 743 should follow this message. Recovery. Consult the EMS event log for any preceding errors that might indicate the source of the problem. If it is possible to correct the underlying problem, then RDF can be restarted. 747 Volume must be a TMF datavol volume volume is the name of the volume on the remote node that must be added to the TMF configuration as a data volume. Cause.
Messages RDF Messages 750 Failure to obtain TLE for SIGNALTIMEOUT Cause. All RDF processes rely upon the ability to post timers by calling SIGNALTIMEOUT and take action when those timers expire. This message indicates that a call to SIGNALTIMEOUT failed because there were insufficient time list elements (TLEs) available. Effect. The process continues to run, but recovery is required. Recovery. Issue a STOP RDF command immediately.
Messages RDF Messages rbn is the relative block number of the block where the error occurred in the audit-trail file. rba is the relative byte address where the error occurred in the audit-trail file. Cause. The extractor detected that the relative block number (RBN) of a block of audit data in the TMF audit trail is out of sequence. This message indicates an internal RDF or TMF error. The message includes the file name, relative block number, and relative byte address of the audit file in question.
Messages RDF Messages 754 Network restored - continuing service Cause. The primary system processes have determined that the communications lines have been restored. The extractor is now able to communicate with the receiver. Effect. Processing continues from the point at which the network failed. Recovery. This is an informational message; no recovery is required. 755 CHECKMONITOR failure - backup abended Cause.
Messages RDF Messages 758 Process abending Cause. The indicated process is abending. Effect. A SAVEABEND file is created, a stack trace is logged, and the process (and its backup process, if any) abends. RDF stops. Recovery. Restart the RDF product and report the error to your service provider. 759 Secondary partition on unknown node filename filename is the name of the affected file. Cause.
Messages RDF Messages 761 Backup stopped Cause. The backup process of a process pair has been stopped. This probably was the result of an operator inadvertently issuing a STOP command from TACL. Effect. A new backup will be created. Recovery. This is an informational message; no recovery is required. 762 Context file is old; must INITIALIZE RDF Cause. An RDF process has determined that the existing context file belongs to an older version of RDF. Effect. You cannot start the RDF subsystem. Recovery.
Messages RDF Messages 765 Invalid audit record encountered Cause. The updater process has sent an audit record to the disk process that is the wrong version. Effect. The updater abends. Recovery. This is an internal error. Contact your service provider. 766 Phase one part 1 database synchronization complete Cause. The first part of phase one of a database synchronization operation has completed. Effect. The extractor continues with processing the second part of phase one. Recovery.
Messages RDF Messages 769 Rolling over to filename filename is the name of the next image file in the sequence. Cause. The reporting process has filled the current image file and is ready to begin writing to the next file in sequence. This next file is named in filename . Effect. The reporting process rolls over into the specified image file. Recovery. This is an informational message; no recovery is required. 770 RDF RDFNET process started Cause.
Messages RDF Messages 773 Remote RDF updater started vol => vol vol => vol are the volume on the primary node that the updater is protecting and the corresponding volume to which it is writing on the backup node. Cause. The updater has successfully completed its initialization. The message includes the audited volume name and its corresponding update volume name. Effect. The updater is prepared to apply updates to the database on the backup node. Recovery.
Messages RDF Messages 777 Unexpected STOP SYNCH message received Cause. The extractor has received a STOP SYNCH message, but it is not involved in a database synchronization operation. Effect. The extractor abends. Recovery. This is an internal error. If no database synchronization operation was in progress, you must restart RDF. If a database synchronization operation was in progress, you must restart the entire operation from the beginning. 778 Remote RDF updater shutdown complete Cause.
Messages RDF Messages Effect. If all the records for a transaction are not received on the backup node, the transaction is treated as if it aborted. For every image record that is not applied to the backup database, an exception record is written to the designated exception file. Recovery. This is a normal occurrence during TAKEOVER processing. The system manager can use RDFSNOOP to list the image records that were not applied to the backup database.
Messages RDF Messages Recovery. If RDF was stopped on the remote node by a STOP RDF command while the communications lines were down, simply restart RDF by issuing a START RDF command. 784 Shutdown pending STOP UPDATE, TIMESTAMP timestamp timestamp is the specified timestamp. Cause. The process has received notice that an RDFCOM STOP UPDATE, TIMESTAMP command was executed. Effect. Each updater applies only audit data associated with transactions that committed prior to the specified timestamp. Recovery.
Messages RDF Messages 787 Image trail file position error error on filename. SNO sno RBA rba error is the error number that identifies the specific error. filename is the name of the image trail file that contained the error. sno is the sequence number where the error occurred. rba is the relative byte address where the error occurred. Cause. The receiver or an updater has encountered the indicated error while attempting to position into an image file. Effect. The process abends. Recovery.
Messages RDF Messages 789 CHECKALLOCATESEGMENT failed with error error error is the error number that identifies the specific error. Cause. The primary process of an RDF process pair received an error from the CHECKALLOCATESEGMENT system procedure. Effect. This error is not fatal; processing continues. The backup process is stopped and then re-created later. Recovery.
Messages RDF Messages Effect. This is a catastrophic error; the process abends and RDF stops. Recovery. Correct the underlying condition, then restart RDF. 797 Warning - Image file purge error error on filename error is the file-system error number that identifies the specific error. filename is the name of the image file associated with the error. Cause. The specified process could not purge an image file that is no longer needed.
Messages RDF Messages Effect. The process abends, and RDF stops. The exception to this is an error 12 (file in use) issued when either the receiver or purger attempts to open the file. In this case, the process posts a short delay and then retries the operation, and it repeats these two steps until successful. Recovery. For an error 12 associated with an image file, perform a FUP LISTOPENS on the file to determine which process currently has the designated file open.
Messages RDF Messages Effect. The message includes the error number returned by the WRITE system procedure followed by the file name. For error 43 (unable to obtain disk space for extent), the receiver retries the write operation. All other errors are fatal; the receiver abends, and RDF stops. Recovery. The only recovery from an error 43 condition is to free some disk space.
Messages RDF Messages filename is the name of the affected file. Cause. The RDFNET process has encountered the specified error on the specified file. Effect. The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction. Recovery. You should determine the cause of the error and take appropriate corrective action. 804 READUPDATELOCK error error on filename error is the file-system error number that identifies the specific error.
Messages RDF Messages 806 RDF RDFNET process Shutdown Complete Cause. The RDFNET process has terminated normal processing as the result of a STOP TMF or STOP RDF command." Effect. Normal RDF shutdown processing continues. Recovery. This is an informational message; no recovery is required. 807 Update mode has been set ON Cause. The operator issued a START UPDATE command. Effect. RDF starts updating the backup database. Recovery. This is an informational message; no recovery is required.
Messages RDF Messages Cause. The operator issued a TMFCOM STOP TMF command at the primary node. timestamp is the time of that shutdown. Effect. The RDF process stops normally. Recovery. This is an informational message; no recovery is required. 811 RDF TAKEOVER initiated Cause. The operator issued a TAKEOVER command. Effect. RDF starts a TAKEOVER operation. Recovery. This is an informational message; no recovery is required.
Messages RDF Messages Recovery. This is an informational message. If the condition persists, however, your database administrator should consider moving some of the files protected by TMF on the primary node volume to another volume, and adding another updater to back up the new volume. If you do that, you must synchronize the affected volumes on the primary and backup nodes. 814 Backup process takeover in processor cpu cpu is the number of the processor in which the backup process is now running.
Messages RDF Messages Effect. The process abends. Recovery. Correct the problem that led to the error and restart RDF. 817 Shutting down in response to STOP UPDATE Cause. The operator issued a STOP UPDATE command, and the updater is stopping normally. This message is issued only by updater processes. Effect. The updater stops. Recovery. This is an informational message; no recovery is required. 818 SQL DDL operation aborting database synchronization Cause.
Messages RDF Messages 820 RDF receiver stopped unexpectedly, receiver receiver is the name of the receiver process that stopped. Cause. The receiver has stopped unexpectedly. The message includes the name of the stopped process. Effect. This message is issued by the RDF monitor. The monitor sends an abort request to all remaining RDF processes to stop RDF. Recovery.
Messages RDF Messages 823 Network transaction to be kept: %num num num num %num num num num identifies a network transaction. Cause. This network transaction was committed in the audit trail on the primary system after the first network transaction marked for undo. It can be kept because it committed prior to the first network transaction marked for undo on a different node in the RDF network.
Messages RDF Messages Recovery. Use the SET and ADD commands to create one or more updater configuration records. 827 RDF version incompatible with TMF Cause. The RDF process is not compatible with the audit format being generated by TMF. Effect. RDF stops. Recovery. Restart RDF under the correct version of the operating system and/or TMF. 828 Killing backup process ... Cause. The primary process of a process pair has detected a problem in communicating with the backup process.
Messages RDF Messages Cause. The RDF monitor is attempting to stop a process on the backup node but cannot do so because the communications lines are down. Effect. If a STOP RDF command was being processed, the RDF monitor continues with the shutdown, and all processes on the primary system will stop. The backup processes will remain running. Recovery. To stop the RDF processes on the backup system, you must run RDFCOM on the backup system and issue a second STOP RDF command.
Messages RDF Messages 833 Filtered audit of unknown type, type text specifies the type of audit. Cause. The extractor encountered an audit record it did not recognize. Effect. This is a fatal error; RDF shuts down. Recovery. This message probably is the result of running on a primary system that has had an audit trail created for a version of TMF that RDF does not support.
Messages RDF Messages command-text is the text of the command that was issued. userid if present, is the Guardian userid (group.user) of the user who issued the command. Cause. RDFCOM logs this message whenever you issue any of the following commands: ALTER, INITIALIZE RDF, START RDF, START UPDATE, STOP RDF, STOP UPDATE, or TAKEOVER. command-text is the command text.
Messages RDF Messages Cause. This informational message is logged by an updater when it begins a restart operation. The image file sequence number and the relative byte address within that image file are included in the message. Effect. An updater restart is performed under a variety of circumstances, such as a failure in the primary CPU of the updater, a failure in the primary CPU of the corresponding disk process, or various file errors.
Messages RDF Messages 840 Error - Process name is in use, procname procname is the name of the process that is in use. Cause. A user-specified process name is already in use when the monitor tries to start the indicated process. Effect. The monitor shuts down RDF in an orderly manner. Recovery. If you can stop the process and give it another name, you can then simply restart RDF; otherwise, you will have to alter the name of the RDF process so that the name does not conflict with other process names.
Messages RDF Messages Recovery. The backup database is consistent and ready for use as a backup contingency database. Perform the rest of your installation-specific operations for switching to the backup node (for example, reroute your communications and start your applications). If you performed the TAKEOVER operation inadvertently, you will need to issue an INITIALIZE RDF command and resynchronize the databases. 843 Incorrect version of audit received Cause.
Messages RDF Messages Effect. The database might not be in a consistent state. Recovery. There is no recovery. If you lose your primary system during an online database synchronization, the backup database has not yet been synchronized, and its data therefore might not be consistent. 847 RDF TAKEOVER during initialization synchronization Cause. When the updater completed its RDF Takeover operation, it had not yet completed its role in an INITIALIZE RDF...INITTIME operation. Effect.
Messages RDF Messages 850 TMF Shutdown during phase one of database synchronization Cause. TMF was stopped during an RDF online database synchronization operation, after the extractor had completed its phase one, part 1 processing. Effect. The extractor completes phases one and two of its database synchronization processing and then shuts down in response to the TMF shutdown audit record. Recovery. This is an informational message; no recovery is required.
Messages RDF Messages 854 ZTXUNDO file cannot be opened Cause. While attempting to write the list of transactions that need to be undone to the ZTXUNDO file, that file could not be opened. Effect. RDF aborts. Recovery. If the operation involves an RDF takeover, take corrective action to enable the file to be opened and then reissue the TAKEOVER command. If the operation involves a stop-update-to-time operation, take corrective action to enable the file to be opened and then restart RDF.
Messages RDF Messages Effect. The process aborts the current transaction, restarts and continues processing. Recovery. This is an informational message; no recovery is required. 858 A safe File Recovery position does not exist Cause. A network takeover operation has completed, but, for this particular node in the RDF network, there is no safe MAT position with which you can issue a File Recovery operation on your primary system should that node become available again. Effect. There is no effect.
Messages RDF Messages 861 Extractor processname RTD (rtd) exceeds RTD warning threshold (threshold#) processname is an extractor process name. rtd is an RTD value. threshold# is an RTDWARNING warning threshold value. Cause. The extractor has fallen behind the configured RTDWARNING threshold specified in the RDF configuration. Effect. The extractor continues normal processing. Recovery. This is an informational message.
Messages RDF Messages 863 Missing RDFNET CONFIG record Cause. The RDF monitor process was unable to find the RDFNET configuration record when performing a START RDF command. Effect. The START RDF operation fails and RDF shuts down. Recovery. Restart RDF. If the record is still missing, then you may have to reinitialize RDF. 864 SQL Shared Access DDL record found during undo pass Cause.
Messages RDF Messages 867 Remote RDF purger shutdown complete Cause. The purger process has stopped. Effect. RDF continues to shut down. Recovery. This is an informational message; no recovery is required. 868 Commencing the undo pass Cause. The updater has terminated its redo pass and is now starting an undo pass to back out changes for audit data that has been applied and must now be undone.
Messages RDF Messages 873 Remote RDF purger started Cause. The purger has started as the result of a START RDF command. Effect. The purger commences normal processing. Recovery. This is an informational message; no recovery is required. 874 SEGMENT_ALLOCATE_ returned error error, error-detail# error is an error number. error-detail# is the detailed error number. Cause. The specified error occurred while attempting to allocate an extended segment. Effect. The affected process abends and RDF aborts.
Messages RDF Messages Effect. The process abends and RDF aborts. Recovery. The file must be altered or recreated with the correct file format and then RDF can be restarted. 876 Imagetrail safe position: SNO sno RBA rba sno is the sequence number. rba is the relative byte address. Cause. This is an imagetrail safe position. Effect. This is an internal event. There is no effect. Recovery. This is an informational message for historical purposes about a pending undo pass. No recovery action is required.
Messages RDF Messages Cause. The purger process has found a file in an image trail subvolume where the file name either, does not contain a valid file-sequence number, or the filecode is not 720. Effect. The purger process will not process any more files in that particular subvolume. The operation will be attempted again after PURGETIME minutes. Recovery. The file being reported was not created by RDF and is not part of the RDF environment.
Messages RDF Messages 882 RDF process transaction unilaterally aborted Cause. The named RDF process' current transaction has been aborted by TMF and the disk process. Effect. The process restarts. Recovery. This is an informational message. You must examine the event log to determine why the process is restarting and if any recovery action is required. 883 Physical volumes in pool exceed the limit of 15 Cause. The updater is configured to a virtual SMF disk that consists of more than 15 physical disks.
Messages RDF Messages 886 Updater phase three takeover processing complete Cause. The updater has reached the end of network undo takeover processing for an RDF network environment. Effect. The updater is ready to complete takeover processing. Recovery. This is an informational message; no recovery is required. 888 MAT position for File Recovery: SNO RBA Cause. A successful takeover has completed.
Messages RDF Messages Effect. The purger starts an attempt to build the list. Recovery. This is an informational message; no recovery is required. 891 First network transaction to be undone: %identifier identifier is the transaction identifier. Cause. This is the first transaction that requires network undo with respect to business consistency across all backup nodes.
Messages RDF Messages Effect. The command is aborted. Recovery. Wait until all RDF updaters have been started and have caught up, then retry the operation. If you get this event message again, stop the RDF product, then restart it. After RDF starts you may issue another STOP UPDATE, TIMESTAMP command. 894 SQL NSA operation detected at SNO sno RBA rba sno is the sequence number. rba is the relative byte address. Cause.
Messages RDF Messages Effect. The updater is ready to complete takeover processing. Recovery. This is an informational message; no recovery is required. 898 SQL NSA operation detected in network undo operation Cause. An SQL SHARED ACCESS DDL operation was detected during the network undo phase of the RDF takeover operation. Effect. The updater abends, and the takeover operation aborts. Recovery. Recovery may not be possible. Contact your service provider. 899 Too many transactions for undo processing.
Messages RDF Messages Effect. The extractor reads and sends all remaining audit from the remote mirror(s) connected to the ZLT standby system to the receiver on the backup system. Recovery. This is an informational message; no recovery is required. 902 The remote mirror for volume is missing volume is a volume name. Cause. The extractor has determined that the specified remote mirror is not connected to the ZLT standby system or that an expected audit-trail file is missing. Effect. The extractor abends.
Messages RDF Messages Recovery. If the master receiver has been waiting for more than 30 seconds, you should check the status of all auxiliary extractors and receivers with the RDFCOM STATUS PROCESS command. If you see this event when attempting to issue an RDF TAKEOVER operation, you should manually stop all RDF processes on the backup system and then reissue the RDFCOM TAKEOVER command. 905 SQL DDL operation must not be performed Cause.
Messages RDF Messages 907 Backup process creation error nnn nnn, file filename nnn nnn are the error number and error detail returned by the PROCESS_CREATE_ system procedure. filename is the name of the program file that was to be executed. Cause. The primary process of an RDF NonStop process pair encountered an error while attempting to create its backup process.
Messages RDF Messages 909 Trigger CPUs for trigger-type trigger are unavailable trigger-type is the trigger type, REVERSE or TAKEOVER. Cause. Neither the primary nor alternate CPUs for the configured trigger are available. Effect. The trigger is started in an alternate CPU. Recovery. This is an informational message; no recovery is required. 910 Update stopped as a result of a STOP UPDATE command Cause. The purger logs this event whenever all updaters have stopped following a STOP UPDATE command.
Messages RDF Messages 912 Starting trigger-type trigger using object-file trigger-type is the trigger type, REVERSE or TAKEOVER. object-file is the name of the Guardian object file to be executed. Cause. The purger is about to start the user-configured trigger process. Effect. The trigger process is started. Recovery. This is an informational message; no recovery is required. 914 Trigger process completed. [ Completion Code: num ] [ Termination Text: text ] [ The process abended.
Messages RDF Messages 915 Drain operation complete but a primary volume is down Cause. A STOP RDF, DRAIN or STOP RDF, REVERSE command has completed but RDF has detected that a volume on the primary node is down. Effect. Any transactions that touched the affected volume that were active when the volume went down are unresolved (on both the primary and backup systems). If this event is the result of a STOP RDF, REVERSE, the REVERSE trigger is not executed. Recovery.
Messages RDF Messages 918 STOP TMF record encountered while DRAIN or REVERSE is pending Cause. A STOP RDF, DRAIN (or REVERSE) operation is being processed and the RDF extractor encountered a STOP TMF record in the TMF audit trail. Effect. These two operations cannot be processed concurrently, which causes RDF to abort. Recovery. Restart RDF and the STOP TMF record will be processed as normal.
Messages RDFCOM Messages RDFCOM Messages The following pages list all messages generated by RDFCOM. These messages appear on your terminal screen during an RDFCOM session. Alternatively, they can be directed to another output device or file through the OUT command, issued during an RDFCOM session or the OUT parameter entered in the RDFCOM command that begins the session. The messages appear in alphabetic order by message text. Ambiguous timestamp for operation Cause.
Messages RDFCOM Messages A required attribute for a non network master is missing Cause. You must specify the PrimarySystem, BackupSystem, and RemoteControlSubvolume for the network master of your RDF network. Effect. The configuration command fails. Recovery. Set the missing fields and add the record. A TAKEOVER operation has not completed on the local system Cause. You tried to execute the COPYAUDIT command, but the RDF TAKEOVER operation has not completed on the local system. Effect.
Messages RDFCOM Messages ALTER Failed: error# error# is the file-system error number that identifies the specific error. Cause. An ALTER command failed. Effect. The ALTER operation was not completed. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error.
Messages RDFCOM Messages Effect. The backup database becomes the database of record. Recovery. This is an informational message; no recovery is required. Audit is missing. Consult your HP analyst. Cause. The COPYAUDIT command could not find audit that should exist in the local image trail. Effect. The COPYAUDIT command aborts. Recovery. There may be no recovery for this problem. To verify that required audit is missing from your local image trail, consult your local HP analyst.
Messages RDFCOM Messages Effect. RDF does not start. Recovery. Add one or more network records to the configuration describing the non network master subsystem(s). Backup node in network master record is incorrect Cause. The network master network record does not have the have the specified backup system name for the local RDF subsystem. Effect. Validation fails. Recovery. You must reconfigure your network master. BACKUPSYSTEM is Not Defined Cause.
Messages RDFCOM Messages Cause. An ALTER command failed for the specified components. Effect. The command fails. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager.
Messages RDFCOM Messages Effect. START RDF processing is aborted. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager.
Messages RDFCOM Messages Cause. An open error occurred during START RDF or STOP RDF command processing. Effect. The START RDF or STOP RDF operation is aborted. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager.
Messages RDFCOM Messages Cause. A START RDF command failed because the specified CPUs do not exist (they were not configured during SYSGEN). Effect. The command fails. Recovery. Reconfigure RDF to use other CPUs or, if you must use the specified CPUs, see your system manager. Creation error error# on IMAGETRAIL volume-name error# is the file-system error number that identifies the specific error. volume-name is the image trail volume on which the error occurred. Cause.
Messages RDFCOM Messages Data from auxiliary audit trails is not allowed with lockstep Cause. You tried to add an auxiliary extractor or receiver to an RDF environment that had previously been configured for lockstep operations. Effect. The ADD EXTRACTOR or ADD RECEIVER command fails. Recovery. You cannot have both lockstep operation and protection for data configured to an auxiliary audit trail in the same RDF subsystem.
Messages RDFCOM Messages Do you wish to proceed? [Y/N] Cause. You entered an INITIALIZE RDF command that attempted to initialize RDF at a specific TMF shutdown timestamp, and received this message as a prompt for confirmation. Effect. If you respond YES or Y, RDFCOM searches the MAT file for a TMF shutdown timestamp equal to the one specified. If you respond NO or N, RDF is not initialized. Recovery. This is an informational message; no recovery is required.
Messages RDFCOM Messages Error error# obtaining pool information for SMF volume volume error# is the file-system error number that identifies the specific error. volume is the SMF volume. Cause. RDFCOM experienced an error while attempting to obtain the physical disk information for the specified SMF disk volume. The error number indicates the cause. Effect. The RDFCOM command being executed fails. Recovery. Correct the underlying problem with the SMF pool and reissue the RDFCOM command.
Messages RDFCOM Messages Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the COPYAUDIT command. Otherwise, see your system manager. Error error# on process info attempt error# is the file-system error number that identifies the specific error. Cause.
Messages RDFCOM Messages Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. Take appropriate corrective action, and then reissue the COPYAUDIT command. Error error# on setmode for large transfers error# is the file-system error number that identifies the specific error. Cause.
Messages RDFCOM Messages Effect. The requested operation does not take place. Recovery. Reenter your request, this time specifying either YES, Y, NO, or N to the prompt. Expecting 'Yes' or 'No' response. Search stopped Cause. While attempting to initialize RDF to a TMF shutdown timestamp, you have entered an unexpected response to the RDFCOM prompt that asks if you want RDFCOM to trigger the restoration of an audit-trail file that has been dumped. Effect.
Messages RDFCOM Messages Effect. The START RDF or TAKEOVER operation is aborted. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager. EXTRACTOR record exists, use ALTER EXTRACTOR Cause.
Messages RDFCOM Messages Global record not found for subsystem ctrl-subvol ctrl-subvol is the name of an RDF subsystem control subvolume. Cause. The global record of the RDF subsystem with the specified control subvolume could not be found. Effect. Validation fails. Recovery. Before you can validate your local RDF subsystem, you must configure all RDF subsystems in your network. Illegal File Format: error error# is the NEWPROCESS error number that identifies the specific error. Cause.
Messages RDFCOM Messages Image files needed for Triple Contingency must have been purged because the receiver’s retaincount must have been set too low. Cause. Audit required for the COPYAUDIT command on the remote system has been purged, probably because the receiver’s RETAINCOUNT value was set too low. Effect. The COPYAUDIT command aborts. Recovery. There may be no recovery for this problem. You must perform the database synchronization without the help of RDFCOM.
Messages RDFCOM Messages Effect. The ADD command fails. Recovery. Review and revise your RDF configuration. IMAGETRAIL is already in use by Receiver Cause. You tried to add a secondary image trail, but the volume you specified for that trail is already being used for receiver’s RDFVOLUME. Effect. The command fails. Recovery. Select a different volume for the secondary image trail. IMAGETRAIL volume-name has already been added volume-name is the name of the volume you specified for the image trail.
Messages RDFCOM Messages Effect. The command fails. Recovery. Select a different secondary image trail to delete, or select another command. IMAGETRAIL VOLUME volume-name does NOT exist volume-name is the name of the volume. Cause. While validating your configuration, RDFCOM determined that the volume for this image trail does not exist on the backup node. Effect. The validation operation aborts. Recovery. Delete this image trail volume and all updaters that use it.
Messages RDFCOM Messages Inconsistent network options are not allowed Cause. You have attempted to add the RDF configuration record with the RDF NetworkMaster attribute on but the Network attribute off. Effect. The configuration command fails. Recovery. You must determine whether you are in an RDF network or not. Internal consistency error on Network records Cause. RDFCOM has detected an internal error that indicates inconsistency. Effect. The configuration command fails. Recovery.
Messages RDFCOM Messages Initialization with database synchronization is only available with the NonStop(TM) RDF/IMP(X) product. Cause. You tried to initialize RDF with the SYNCHDBTIME option, but RDF/IMP or IMPX is not installed. Effect. The INITIALIZE RDF command fails. Recovery. If you want to perform online database synchronization, RDF/IMP or IMPX must be installed on both the primary and backup systems. INITIALIZE RDF aborted Cause.
Messages RDFCOM Messages The correct format for the timestamp is: day month year hour : min where: day is a number from 1 to 31. month is the first three letters of the month, such as JAN, FEB, MAR. year is a two-digit or four-digit number, such as 91 or 1991. Any year greater than 1999 must be specified in four digits. hour is a number from 0 to 23. min is a number from 00 to 59. min must be preceded by a colon (:). Library Conflict Cause.
Messages RDFCOM Messages Local image file filename is missing filename is the name of the image trail file. Cause. The COPYAUDIT command could not find the specific image file on the local image trail, although this file should exist on disk. Effect. The COPYAUDIT command aborts. Recovery. There is no recovery for this problem. You must perform the database synchronization without the help of RDFCOM. Master EXTRACTOR Record already exists Cause.
Messages RDFCOM Messages MONITOR Record exists, use ALTER MONITOR Cause. An ADD MONITOR command was issued when the configuration file already contained a monitor record. Effect. The command fails. Recovery. No recovery is required if you want to use the existing monitor process as configured. If you want to change any of the monitor’s configuration options, however, enter an ALTER MONITOR command that specifies those changes. MONITOR record NOT found Cause.
Messages RDFCOM Messages Network synch file ZRDFNETX must not be EXCLUDED Cause. An EXCLUDE pattern has been specified which will case audit associated with the NetSynch data file to be filtered out. Effect. RDF can not be started. Recovery. Correct the VOLUME EXCLUDE associated with the PNETTXVOLUME so that the EXCLUDE pattern does not exclude the file $..ZRDFNETX. Network synch file ZRDFNETX file must be INCLUDED Cause.
Messages RDFCOM Messages Effect. The validation fails. Recovery. Add a receiver with the same ATINDEX value or delete the particular extractor. No VOLUMES are configured for ATINDEX atindex Cause. You added an extractor and receiver with the specified ATINDEX, but there are no updaters with that value. Effect. The validation fails. Recovery. Add at least one updater with the same ATINDEX value or delete the particular extractor-receiver pair.
Messages RDFCOM Messages No PCB available Cause. A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect. The command fails. Recovery. Check system resource utilization. When resources become available, reenter the command. No RECEIVER is Configured Cause. The RDF configuration file is invalid. Effect. The configuration validation fails. Recovery. Check the receiver parameter entries in the configuration file for invalid values and correct any errors found.
Messages RDFCOM Messages Only one Network record is allowed for a non-network master Cause. Your current RDF configuration does not have the NetworkMaster attribute set and you have tried to add more than one network record. Effect. The configuration command fails. Recovery. If the network record you have previously added pertains to the RDF network master subsystem, then do not add any further network records.
Messages RDFCOM Messages Operation can only be performed on the BACKUPSYSTEM \backup backup is the name of the backup node that can perform the operation. Cause. The command can be issued only at the backup system. Effect. The command fails. Recovery. Enter another command. Operation can only be performed on the PRIMARYSYSTEM \primary primary is the name of the primary node that can perform the operation. Cause. The command can be issued only at the primary node. Effect. The command fails. Recovery.
Messages RDFCOM Messages Please wait while RDF searches for the specified shutdown timestamp Cause. You entered an INITIALIZE RDF command that attempted to initialize RDF at a specific TMF shutdown timestamp, and responded YES or Y to the subsequent confirmation prompt, directing the subsystem to proceed with the initialization. Effect. RDFCOM reads backward through the MAT in search of a TMF shutdown record with the same timestamp you specified. Recovery.
Messages RDFCOM Messages Position error error# on file remote-config-file error# is the file-system error number that identifies the specific error. remote-config-file is the name of the remote configuration file. Cause. The COPYAUDIT command encountered the specified error while attempting to position into the remote configuration file. Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code.
Messages RDFCOM Messages Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the COPYAUDIT command. Otherwise, contact your service provider. Position error error# on remote image file error# is the file-system error number that identifies the specific error.
Messages RDFCOM Messages Process Name Error: error# error# is the error number that identifies the specific error. Cause. A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect. The START RDF or TAKEOVER operation is aborted. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual.
Messages RDFCOM Messages RDF already in TAKEOVER processing Cause. The operator issued a TAKEOVER command at the backup node while RDF was performing a TAKEOVER operation. Effect. The last TAKEOVER command is ignored. Recovery. This is an informational message; no recovery is required. RDF configuration file is not open, use OPEN command Cause. The configuration file must be open before any RDFCOM commands other than OPEN or OBEY can be executed. Effect. The attempted operation is aborted. Recovery.
Messages RDFCOM Messages Effect. The command fails. Recovery. Reissue the command after RDF is started. RDF LOGFILE filename NOT a legal filename on system \node filename is the name of the non-existent EMS collector (RDF log file). node is the name of the system where the collector name is invalid. Cause. The RDF configuration file is invalid: a non-existent EMS collector was specified. Effect. The ADD RDF command fails. Recovery.
Messages RDFCOM Messages RDF START Failure, Scan LOGFILE for reason Cause. A START RDF command failed. RDF writes a description of the problem in the LOGFILE. Effect. The START RDF command fails. Recovery. Check the EMS event log for the message covering this error. If possible, correct the cause of the error and reissue the START RDF command. Otherwise, contact your system manager.
Messages RDFCOM Messages RDFCOM internal error in handling prompt Cause. RDFCOM detected an internal error in handling your response to the RDFCOM prompt. Effect. The attempted command is aborted. Recovery. Contact the Global Customer Support Center (GCSC) or your service provider. RDFCOM is asking the TMP to restore the file. If the file was previously dumped to tape, watch for the TMP to tell you to mount the appropriate tape. Cause.
Messages RDFCOM Messages RDFVOLUME in network master record is invalid. Cause. The RDFVOLUME of the current RDF configuration is invalid in the network record of the network master. Effect. Validation fails. Recovery. You must reconfigure your network master and possibly your local configuration. RDFVOLUME is not allowed for an aux receiver. Auxiliary receivers do not have an RDFVOLUME. Cause. You tried to add an auxiliary receiver for which you had specified an RDFVOLUME. Effect.
Messages RDFCOM Messages Cause. The COPYAUDIT command encountered the specified error while attempting to read data from a remote image file on the remote image trail. Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the underlying error and reenter the COPYAUDIT command.
Messages RDFCOM Messages As one of its validation checks during START RDF processing, RDFCOM tries to create a temporary image file on the receiver’s RDFVOLUME and then to allocate all 16 extents.
Messages RDFCOM Messages RECEIVER RDFVOLUME volume-name does NOT exist volume-name is the name of the non-existent RDFVOLUME file. Cause. The RDF configuration file is invalid. Effect. The validation of the receiver fails. Recovery. Specify a valid disk volume. RECEIVER Record does not exist Cause. You tried to add a secondary image trail before adding the receiver’s configuration record. Effect. The command fails. Recovery. Add the receiver’s record. Then, add the secondary image trail.
Messages RDFCOM Messages Cause. RDFCOM was unable to read the receiver record for the RDF subsystem with the specified control subvolume. Effect. Validation fails. Recovery. Determine why the receiver record for the subsystem cannot be obtained. RECEIVER Record with ATINDEX atindex does not exist. Cause. You tried to add an imagetrail with the specified ATINDEX, but there is no receiver with that value. Effect. The ADD command fails. Recovery.
Messages RDFCOM Messages Restore failed with error error# Search is stopped. error# is the file-system error number that identifies the specific error. Cause. Restoration of an audit-trail file has failed for the reason indicated by error#. Effect. RDFCOM immediately terminates its search for a TMF shutdown timestamp and then its attempt to initialize RDF. Recovery. Refer to the Operator Messages Manual for a description of the error code.
Messages RDFCOM Messages SHUTDOWN Failure: error# on RECEIVER error# is the error number that identifies the specific error. Cause. RDFCOM could not stop the receiver because of error#. Effect. The shutdown operation is aborted. Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting errors, see the Guardian Procedure Errors and Messages Manual.
Messages RDFCOM Messages Effect. The configuration command fails. Recovery. Determine why the communications path to this system is down and take the appropriate recovery steps to bring it back up. Specified network primary system is not defined. Cause. The specified primary system does not exist. Effect. The configuration command fails. Recovery. You must specify a valid primary system name. Specified network primary system is unavailable. Cause.
Messages RDFCOM Messages START RDF Aborted Cause. A START RDF command aborted. Effect. The command fails. Recovery. Scan the EMS event log to determine why the command aborted, correct the error if possible, and reenter the START RDF command. START UPDATE in progress, Please Wait... Cause. A START UPDATE command is being executed. Effect. The start operation continues for the updater process. Recovery. This is an informational message; no recovery is required. Starting RDF, Please Wait... Cause.
Messages RDFCOM Messages Effect. The RDFCOM STOP SYNCH command aborts. Recovery. Correct the situation and then reissue the command. STOP SYNCH command is aborted because database synchronization is not in progress. Cause. You are attempting to execute an RDFCOM STOP SYNCH command, but online database synchronization is not in progress. Effect. The RDFCOM STOP SYNCH command aborts. Recovery.
Messages RDFCOM Messages Recovery. All remaining updaters must be manually stopped from the TACL interface (for example, with a TACL STOP $UPD1 command). Examine the EMS event log for the error message 841; this message contains the Guardian error number that the monitor received when attempting to stop the updater. Storing missing audit in the imagetrail. Cause.
Messages RDFCOM Messages Synch point for synchdbtime has been found synchdbtime is a SYNCHDBTIME timestamp specified previously by an operator in an RDFCOM INITIALIZE RDF command. Cause. In conjunction with a complete database synchronization, a record whose timestamp is less than synchdbtime has been located successfully. Effect. The RDFCOM INITIALIZE RDF command continues. Recovery. This is an informational message; no recovery is required.
Messages RDFCOM Messages The control subvolume name is not presently 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. name is the name of the control subvolume explicitly specified or the primary system name assigned by default. Cause. The control subvolume either specified or selected by default does not exist. Effect.
Messages RDFCOM Messages The last record in the local imagetrail on volumename.subvolume-name could not be found in the remote trail volume-name is the name of the image trail’s volume subvolume-name is the name of the image trail’s subvolume. Cause. The COPYAUDIT command could not find the last record in the local image trail on the remote image trail.
Messages RDFCOM Messages The MONITOR must be a named process Cause. You must specify a process name for the monitor process before issuing an ADD command. Effect. The start command fails. Recovery. You must reconfigure RDF with a named monitor process. The number of physical UPDATEVOLUMES exceeds 255. RDF/IMPX is required for this many volumes. Cause. RDF has detected that the user is running RDF/IMP and the total number of physical volumes for all UPDATEVOLUMEs exceeds 255.
Messages RDFCOM Messages The RDFNET must be a named process Cause. You must specify a process name for the RDFNET process before issuing an ADD command. Effect. The start command fails. Recovery. You must reconfigure RDF with a named RDFNET process. The [remote] control subvolume name [on bksys] is not empty. The files on the control subvolume must be purged. Please note, these files may belong to another RDF configuration. name is the name of the remote RDF control subvolume.
Messages RDFCOM Messages Effect. The STOP UPDATE command aborts. Recovery. Reissue the STOP UPDATE, TIMESTAMP command, specifying a timestamp that is at least five minutes ahead of the current time. The Triple Contingency COPYAUDIT command has completed successfully. You must now issue a new RDFCOM Takeover command. Cause. The COPYAUDIT command has finished copying the missing audit from the remote system to the local system and has updated all context records on the local system. Effect.
Messages RDFCOM Messages Effect. The ADD command fails. Recovery. Review and revise your RDF configuration. This command is not allowed in an OBEY file. Cause. An illegal command was encountered within an OBEY command file. Effect. The command fails. Recovery. Remove the command from the OBEY command file, and reenter the command directly from your terminal. This RDF subsystem is not configured in the network master subsystem Cause.
Messages RDFCOM Messages TMF is not started yet. Cause. TMF has not been started. Effect. The requested RDFCOM operation fails. Recovery. Check the contents of the RDF configuration file, issue a VALIDATE RDF command to verify the configuration, and reissue your request for the RDFCOM operation you originally wanted to perform. TMF NAT table is full. Cause. There is a problem with TMF. Effect. The configuration validation fails. Recovery. Check the status of TMF.
Messages RDFCOM Messages To issue this command, the RTD time of the extractor must be 0:00. Have you confirmed that the RTD is 0:00? Cause. You are attempting to execute an RDFCOM STOP SYNCH command. To ensure that the extractor does not miss any audit information, the extractor RTD must be 0:00 before executing this command. Effect. You are prompted for a “yes” or “no” response. Recovery. Enter YES (or Y) to execute the command or NO (or N) to cancel it.
Messages RDFCOM Messages Unable to allocate Map Cause. A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect. The NEWPROCESS procedure fails. Recovery. Make sufficient space available on the swap volume for the requested operation. Unable to communicate with CPU cpu cpu is the CPU that is not responding. Cause. A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect. The NEWPROCESS procedure fails. Recovery.
Messages RDFCOM Messages Effect. The ADD command fails. Recovery. Exit RDFCOM and then try again. If the problem persists, contact the Global Customer Support Center (GCSC) or your service provider. Unable to purge old image file due to error error# DELETE ABORTED error# is the file-system error number that identifies the specific error. Cause. A START RDF command failed because the reported error prevented RDFCOM from purging the old image file. Effect. The command fails. Recovery.
Messages RDFCOM Messages Unidentifiable newprocess error: newproc0:7:newproc8:15 newproc# identifies the new process error. Cause. A NEWPROCESS error occurred during START RDF or TAKEOVER processing. Effect. The command fails. Recovery. Refer to the Operator Messages Manual for a description of the error. For additional details about understanding and correcting process errors, see the Guardian Procedure Errors and Messages Manual.
Messages RDFCOM Messages Effect. The command fails. Recovery. Scan the EMS event log to determine why the command could not be performed. Correct the error condition, if possible, and request the update operation again. VOLUME device is NOT a disk volume device is the non-disk device assigned to the updater. Cause. The RDF configuration file is invalid. Effect. RDF will not start. Recovery. Change the RDF configuration to reflect a valid disk volume.
Messages RDFCOM Messages Cause. The updater is configured to a virtual SMF disk that consists of more than 15 physical disks. This configuration is not supported by the RDF product. Effect. RDF will not start. Recovery. Reset your RDF configurations and/or your SMF configuration so that the updaters are either assigned to physical volumes, or your SMF virtual disks map to 15 or fewer physical volumes.
Messages RDFCOM Messages VOLUME volume UPDATEVOLUME does NOT exist volume is the volume on the primary node for which the updater is responsible. Cause. The RDF configuration file is invalid. Effect. RDF will not start. Recovery. Bring the volume up, or delete it from the RDF configuration. VOLUME volume record NOT found volume is the volume on the primary node for which the updater is responsible. Cause. The INFO command could not find an updater record for volume in the configuration file. Effect.
Messages RDFCOM Messages WARNING - BACKUPSWAP parameter has no effect, KMSF swap volume takes precedence Cause. The user attempted to SET or ALTER the RDF BACKUPSWAP parameter. Effect. This parameter no longer has any effect. The KMSF subsystem controls the placement of the RDF processes’ swap files. Recovery. This is an informational message; no recovery is required.
Messages RDFCOM Messages Effect. This parameter no longer has any effect. The KMSF subsystem controls the placement of the RDF processes’ swap files. Recovery. This is an informational message; no recovery is required. * * * WARNING * * * RDF will start at the first record in the TMF master audit trail beyond the specified shutdown timestamp. RDF will ignore all audit generated before this timestamp. Cause.
Messages RDFCOM Messages Write error error# on attempt to reach the extractor, STOP SYNCH command aborted. error# is the file-system error number that identifies the specific error. Cause. You are attempting to execute an RDFCOM STOP SYNCH command, but RDFCOM encountered the specified error while sending the message to the extractor. Effect. The STOP SYNCH command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code.
Messages RDFCOM Messages Write error error# on new image file filename error# is the file-system error number that identifies the specific error. filename is the name of the image trail file associated with the error. Cause. The COPYAUDIT command encountered the specified error while attempting to write data into the specified image file on the local image trail volume. Effect. The COPYAUDIT command aborts. Recovery. Refer to the Operator Messages Manual for a description of the error code.
Messages RDFCOM Messages Effect. RDFCOM suspends until you respond to the prompt. Recovery. Respond “yes” or “no” to the prompt. You are attempting a TAKEOVER operation immediately after the receiver has crashed. Please contact your HP analyst before proceeding with the TAKEOVER operation. Cause. RDFCOM has detected that the receiver stopped prematurely the last time it was running.
Messages RDFCOM Messages You cannot start updaters before the extractor has completed Phase 2 of its online database synchronization operation. Cause. You tried to start updaters by either a START RDF or START UPDATE command before the extractor completed Phase 2 of its database synchronization operation. Effect. The START RDF or START UPDATE command fails. Recovery. You must wait until the extractor has logged message 782 before starting the updaters.
Messages RDFSCAN Messages RDFSCAN Messages The following RDFSCAN messages (listed alphabetically by text) can appear on your terminal screen during an RDFSCAN session. Beyond eof! Cause. The AT position specified is beyond the end-of-file mark in the current log file. Effect. The AT command fails. Recovery. Reenter the AT command, this time with a record-number parameter that indicates a position before the end-of-file mark.
Messages RDFSCAN Messages Recovery. Refer to the Operator Messages Manual for a description of the error code. For additional details about understanding and correcting file-system errors, see the Guardian Procedure Errors and Messages Manual. If possible, correct the error and reenter the command that encountered the error. Otherwise, see your system manager. File error: error# trying to read RDFlog file error# is the file-system error number that identifies the specific error. Cause.
Messages RDFSCAN Messages HELP for command not found command is the RDFSCAN command for which online help was requested. Cause. The command for which HELP text was requested is not a valid RDFSCAN command. Effect. The HELP command fails. Recovery. Enter another RDFSCAN command, or select another command for which to request help. Invalid request Cause. The request was not a valid RDFSCAN command. Effect. The command fails. Recovery. Enter another RDFSCAN command.
Messages RDFSCAN Messages HP NonStop RDF System Management Manual—529826-003 C-146
D Operational Limits Table D-1.
Operational Limits HP NonStop RDF System Management Manual—529826-003 D- 2
E Using ASAP ASAP (HP NonStop Availability Stats and Performance) allows many subsystem entities to be monitored across a network of HP NonStop servers. The status and statistics for the entities are collected on a single system, and are then monitored either through the ASAP command interface or through the ASAP graphical user interface (GUI) PC client.
Using ASAP Installation Figure E-1. The RDF/ASAP Environment \PRI \BAK RDF SGP RDF SGP Updaters Purger Monitor Extractor Receiver Image Trail Installation The RDF SGP is packaged with the RDF/IMP and IMPX products and, by default, is installed on $SYSTEM.RDF. You may, however, place this object file wherever you want. If you install the SGP object file somewhere other than $SYSTEM.
Using ASAP Monitoring Specific RDF Environments Monitoring Specific RDF Environments If you only want to monitor specific RDF environments, you can override the autodetection by explicitly specifying the RDF environments for which you want the SGPs to collect stats. The ASAP CI command is: MONITOR RDF -> Where is the RDF control subvolume of the RDF environment and is the backup system name (note that there are no ‘\’ characters in either field).
Using ASAP RDF Metrics Reported by ASAP RDF Metrics Reported by ASAP For each RDF entity, the RDF SGP passes the information shown in Table E-1 back to ASAP. Information Passed to ASAP Monitor Extractor Receiver Imagetrail Purger RDFNET Updater Table E-1.
Index Numbers 900, File code 2-8 A Abbreviations 8-27, A-4 ADD command 8-9, A-2 ADD EXTRACTOR command 3-26, 3-30 ADD MONITOR command 3-30 ADD RECEIVER command 3-32, 3-33 ALTER command 8-14, A-2 ALTER command, FUP 3-8 Altering TMF configuration 3-14 ASAP, Using with RDF 1-34, E-1 Asterisk wildcard character 9-14 AT command 9-3, 9-17, A-16 ATINDEX parameter 8-20, 8-31, 8-56, 8-59, 8-74 Audit compression 3-2 Audit dumping, STATUS RDF command 4-23 Audit trail file purging 2-6, 2-7 AUDITCOMPRESS file attribute
Index C RDFCOM ADD 8-9, A-2 ALTER 8-14, A-2 COPYAUDIT 8-17, A-3 DELETE 8-20, A-3 examples A-1 EXIT 8-23, A-3 FC 8-24, A-4 HELP 8-27, A-4 HISTORY 8-30, A-4 INFO 8-31, A-5 INITIALIZE RDF 8-40, A-5 OBEY 8-47, A-5 OPEN 8-49, A-6 OUT 8-51, A-6 RESET 8-53, A-6 SET EXTRACTOR 8-56, 8-59, A-7, A-8, A-9, A-10 SET MONITOR 8-60, 8-62, 8-72, 8-78, A-8 SET RDF 8-67, A-10 SET RECEIVER 8-64, 8-74, A-11 SET TRIGGER A-11 SET VOLUME 8-81, A-12 SHOW 8-85, A-12 START RDF 8-90, A-13 START UPDATE 8-92, A-13 STATUS RDF 4-19, 8-9
Index D CPUS parameter 8-56, 8-59, 8-60, 8-62, 8-72, 8-78, 8-81, A-7, A-8 extractor process 3-26, 3-30 monitor process 3-30 receiver process 3-32, 3-33 CPUs, displaying 8-98 Crash on the Backup System 5-11 Crash on the Primary System 5-10 Create operation error recovery 5-5 file system errors 5-5 RDF errors 5-5 D Database operations, replicating 2-10 Database synchronization 3-4 File Utility Program (FUP) 3-8 OBEY command files 3-5 Databases backing up altered structures 6-4 Enscribe file-label modificat
Index F preparing for RDF protection 3-2 purge operations 2-11 Enscribe file-label modifications 6-8 Error messages file system C-2 Error recovery create operation 5-5 modify operation 5-2 open operation 5-2 RDF error 700, modify operation 5-2 RDF error 705, open operation 5-2 RDF error 739, create operation 5-5 Event log scanning messages in EMS 1-11, 4-25 Exception files description B-8 examining B-7 records 1-11 EXCLUDE clauses 11-2 EXIT command 8-23, 9-6, A-3, A-16 Expand estimating required resources
Index G File system errors C-2 File system errors create operation 5-5 modify operation 5-2 open operation 5-2 File Utility Program (FUP) ALTER command 3-8 synchronizing ENSCRIBE databases 3-8 Files backup system 3-9 partitioned, synchronizing 3-8 preparing for RDF protection 3-2 File, log 9-1 File-ids 8-6 File-label modifications 6-8 G Gateway process, RDF 14-6 Guardian 90 see Operating system H Hardware requirements 2-1 Help RDFCOM online 4-12 RDFSCAN online 4-17 HELP command 8-27, 9-9, A-4, A-17 HIST
Index M $0 C-2 LOGDEVICE parameter 8-67 LOGFILE parameter 8-67 M Managing the RDF subsystem 4-1 Mapping, SQL/MX Name 15-14 Mapping, volume-to-volume 2-2 Master audit trail, calculating amount of data 2-3 Master image trail 1-19 MATCH command 9-14, A-17 Match pattern for log messages 9-10, 9-14, 9-17, A-17 Messages displaying HELP text for 4-12 file system errors C-2 in log file 4-24 logged in log file 1-11 RDF C-2 RDFCOM C-73 RDFSCAN C-143 scanning in EMS event log 1-11, 4-25 scanning in log file 1-12 mi
Index O DEFINEs for, example 3-6 partition key changes 6-8 partitioned 2-9, 2-11 placement of partitions 2-11 preparing for RDF protection 3-2 purges 6-8 versions, RDF requirements 2-5 views, backup system 2-9 NonStop SQL/MP DDL operations 5-30 NonStop SQL/MX and RDF 15-1 NonStop SQL/MX Operations, RDF and 5-32 Non-shared access DDL operations 5-30 O OBEY command 8-47, A-5 OBEY command file B-4 OBEY command files 4-6 backup system 3-4, 3-9 synchronizing databases with 3-5 OBEYFORM option 8-31 OBEYFORM op
Index Q OBEY command files 3-5 Primary system backing up files 2-7 configuration 2-1 preparing for RDF installation 3-1 processes 1-15 RDF requirements 2-1 Primary System Crash 5-10 Primary system crash, stopping the backup system before restarting the primary system 5-13 PRIMARYSWAP parameter 8-67 PRIMARYSYSTEM network attribute 13-4 PRIORITY parameter 8-56, 8-59, 8-60, 8-62, 8-72, 8-78, 8-81, A-7, A-8 extractor process 3-26, 3-30 monitor process 3-30 receiver process 3-32, 3-33 Process file names A-18 P
Index R IMAGETRAIL 8-20 IMAGEVOLUME 8-81 LOGDEVICE 8-67 LOGFILE 8-67 monitor process 3-30 PRIMARYSWAP 8-67 PRIORITY 8-56, 8-59, 8-60, 8-62, 8-64, 8-72, 8-74, 8-78, 8-81, A-7, A-8 PROCESS 8-56, 8-59, 8-60, 8-62, 8-64, 8-72, 8-74, 8-78, 8-81, A-7, A-8 RDFVOLUME 8-64, 8-74 receiver process 3-32, 3-33 REMOTECONTROLSUBVOL 8-17 remotesys 8-17 RESET PROCESS 8-56, 8-59, 8-60, 8-62, 8-64, 8-72, 8-74, 8-78, 8-81, A-7, A-8 RETAINCOUNT 8-64, 8-74 SUFFIX 8-40 TIMESTAMP 8-40, 8-105 UPDATERDELAY 8-67 UPDATEVOLUME 8-81 V
Index R STATUS RDF 4-19, 8-93, A-13 STOP RDF 8-100, A-14 STOP SYNCH 8-104, A-14 STOP UPDATE 8-105, A-14 TAKEOVER 8-108, A-14 UNPINAUDIT A-15 VALIDATE CONFIGURATION 8-113, A-15 description 4-1 keywords 4-7 online help 4-12 prompt (]) 4-1 running 4-1 security requirements 3-12 using from a command file 4-6 using interactively 4-3 using noninteractively 4-5 RDFCOM command syntax 4-4 RDFEXTO extractor object file 3-9 security requirements 3-12 RDFINST installation macro 3-9 RDFLOCK file description B-9 RDFLOG
Index S object code file 3-9 parameters 3-32, 3-33 adding to configuration file 8-9, A-2 altering 8-14 displaying configuration values 8-31, A-5 displaying option values 8-85, A-12 resetting option values 8-53, A-6 SET RECEIVER example 8-66, 8-77 setting option values 8-64, 8-74, A-11 SHOW RECEIVER example 8-87, 8-88 Recompiling programs 3-9 Reload of Backup Database 2-8 REMOTECONTROLSUBVOL network attribute 13-4 REMOTECONTROLSUBVOL parameter 8-17 REMOTESYS parameter 8-17 Replicating database operations 2
Index T not replicated by RDF 2-10 SQL/MX and RDF 15-1 SQL/MX LOCATION option 15-17 SQL/MX Name Mapping 15-14 SQL/MX offline synchronization for a single partition 15-12 SQL/MX tables, comparing 15-19 SQL/MX tables, restoring 15-17 START RDF command 3-37, 8-90, A-13 START TMF command, TMFCOM 3-37 START TRANSACTION command, TMFCOM 3-8, 3-14 START UPDATE command 3-38, 8-92, A-13 Starting the RDF subsystem 3-37 the TMF subsystem 3-37 STATUS RDF command 4-19, 8-93, A-13 STOP RDF command 8-100, A-14 STOP RDF,
Index U configuration for RDF 2-6 configuring 3-14 DEFER AUDITDUMP command 3-14 initializing 3-14 RDF recovery from crash 5-10, 5-11 RDF requirements 2-6 starting 3-37 transactions designing for RDF protection 2-9 volume crash 5-10 with dump process 2-6 without dump process 2-7 TMFCOM START TRANSACTION command 3-8, 3-14 Transactions designing for RDF protection 2-9 lockstep 14-4 network 13-1 Triple contingency feature 1-29, 10-1 adding to configuration file 8-9, A-2 altering 8-14 displaying configuration
Index W W Wildcard characters in match patterns 9-14 Y You 3-8 Z Zero lost transactions 16-1 ZLT 16-1 ZLT Takeover Operations 16-9 Special Characters * wildcard character 9-14 ? wildcard character 9-14 HP NonStop RDF System Management Manual—529826-003 Index-14
