HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual Abstract This manual describes how to install, configure, operate, and manage version 1, update 6 of the HP NonStop™ RDF/IMP, IMPX, and ZLT Remote Database Facility (RDF) products. 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/IMP 1.6 (T0346) NonStop RDF/IMPX 1.
Document History Part Number Product Version Published 522204-001 NonStop RDF/IMP 1.3 (T0346) NonStop RDF/IMPX 1.3 (T0346 and T0347) October 2001 524388-001 NonStop RDF/IMP 1.4 (T0346) NonStop RDF/IMPX 1.4 (T0346 and T0347) March 2003 There is no version 1, update 5 (1.5). 524388-002 NonStop RDF/IMP 1.6 (T0346) NonStop RDF/IMPX 1.6 (T0346 and T0347) NonStop RDF/ZLT 1.
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual Index Figures What’s New in This Manual xiii Manual Information xiii New and Changed Information Tables xiv About This Manual xv Who Should Read This Manual xv Where to Find Information You Need Related Reading xvii Notation Conventions xix xvi 1.
2.
3. Installing and Configuring RDF Contents 3.
5. Managing RDF Contents Running RDFSCAN 4-13 Command Syntax for Starting an RDFSCAN Session 4-13 Using RDFSCAN 4-14 Using RDFSCAN Commands 4-15 Requesting Online Help 4-15 Performing Routine Operational Tasks 4-17 Displaying Current Configuration Parameters and Operating Statistics Changing Configuration Parameters 4-22 Reading Log Messages 4-23 5.
6. Maintaining the Databases Contents RDF and NonStop SQL/MP DDL Operations 5-27 Performing Non-Shared Access DDL Operations 5-27 Performing Shared Access DDL Operations 5-28 Backing Up Image Trail Files 5-29 Making Online Dumps With Updaters Running 5-30 Doing FUP RELOAD Operations With Updaters Running 5-31 Exception File Optimization 5-32 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-6 Disk File Names 8-6 Nondisk Device Names 8-7 Process File Names 8-8 Command Overview 8-8 9.
10. Triple Contingency Contents 10. Triple Contingency What Is It? 10-1 What’s Required? 10-1 How Does It Work? 10-2 Hardware Requirements 10-2 Software Requirements 10-3 The RETAINCOUNT Configuration Parameter The COPYAUDIT Command 10-5 COPYAUDIT Restartability 10-7 Summary 10-7 10-4 11.
13. Network Transactions Contents 13.
15. NonStop SQL/MX and RDF Contents The Lockstep Transaction 14-4 RDF Lockstep File 14-4 Multiple Concurrent Lockstep Operations 14-5 The Lockstep Gateway Process 14-5 NAME 14-6 PROGRAM 14-6 STARTUPMSG 14-6 AUTORESTART 14-6 Disabling Lockstep 14-6 Reenabling Lockstep 14-7 Lockstep Performance Ramifications 14-7 Lockstep and Auxiliary Audit Trails 14-7 Lockstep and Network Transactions 14-8 Lockstep Operation Event Messages 14-8 15.
16. Zero Lost Transactions (ZLT) Contents 16.
C. Messages Contents C. Messages About the Message Descriptions RDF Messages C-2 RDFCOM Messages C-69 RDFSCAN Messages C-139 C-1 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.
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/IMP, IMPX, and ZLT System Management Manual Abstract This manual describes how to install, configure, operate, and manage version 1, update 6 of the HP NonStop™ RDF/IMP, IMPX, and ZLT Remote Database Facility (RDF) products. 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/IMP 1.
What’s New in This Manual New and Changed Information New and Changed Information This is the fifth edition of the HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual. It replaces the HP NonStop RDF/IMP and IMPX System Management Manual (part number 524388-001), making that manual obsolete. Change bars in the margin identify all differences between this manual and the one it replaces.
About This Manual 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. RDF accomplishes this by sending audit trail information, generated at the primary system by the HP NonStop Transaction Management Facility (TMF) product, over the network to the backup 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).
About This Manual • • • • • • • • • • Related Reading 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.
About This Manual Related Reading 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.
About This Manual Notation Conventions 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.
About This Manual Notation for Messages 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.
About This Manual Notation for Messages HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 xxii
1 Introducing RDF This manual describes the Remote Database Facility (RDF) subsystem as implemented in the HP NonStop RDF/IMP, IMPX, and ZLT independent products.
Introducing RDF RDF Subsystem Overview 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 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.
Introducing RDF Unplanned Outages 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. Updater processes $UP1 through $UP10 read audit information from the secondary image trail and apply it to volumes $D1 through $D10, respectively, on the backup system.
Unplanned Outages Introducing RDF Table 1-1. Audit Information At the Time of a Primary System Failure Primary database updates (Sequence in master audit trail file) Updates sent to the backup (Sequence in image trail file) TRANS100—Update 1 TRANS100—Update 1 TRANS100—Update 2 TRANS100—Update 2 . . . . . .
Introducing RDF Planned Outages If your database is NonStop SQL/MP and if your applications form the typical requestor-server environment where the requestors send requests into your primary system from other locations, then you could start your servers on your primary and backup systems. You must take care that you only route requestor work to your primary system. This leaves your servers running essentially in standby mode on your backup system.
Introducing RDF Features Features In providing backup protection for online databases, RDF offers many advantages: • Continuous Availability RDF maintains an online copy of your production database on one or more backup systems. If the primary system should go down, the backup database(s) will be consistent and you can resume your business processing on a backup system with minimal interruption and data loss. • Fault tolerance You can restart RDF after a system crash.
Features Introducing RDF Figure 1-2.
Introducing RDF Features RDF does not require an identical one-to-one volume relationship between volumes on the primary system and those on the backup system. Backup volume names do not have to match primary volume names. The subsystem can direct audit information from more than one audited volume on the primary system to a single volume on the backup system, provided that no more than one partition of a file exists on any backup volume.
Introducing RDF • User Interfaces Access to Consistent Backup Databases There are two ways to quiesce the backup database in a logically consistent state with regard to transaction boundaries: stop TMF on the primary system or use the TIMESTAMP parameter in a STOP UPDATE command (referred to as a stopupdate-to-time operation). The latter allows you to do so without stopping TMF, your applications, or the RDF extractor. User Interfaces To use RDF, you run two online utilities: RDFCOM and RDFSCAN.
Introducing RDF Tasks You can peruse messages in the EMS log on your terminal screen by using Viewpoint or whatever other tool you normally use for monitoring $0. Note that when doing that, however, you are dealing with the entire EMS log (not just RDF messages). To isolate RDF messages from the rest of the EMS log, you can use the supplied EMS filter RDFFLTO with an EMS printing distributor to produce an intermediate entrysequenced file that you then can scan using the RDFSCAN utility.
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 DDL operations using the WITH SHARED ACCESS option on protected volumes, and monitors the other RDF processes.
Introducing RDF Monitor Process When updating is disabled, the extractor process still transmits the TMF audit records from the audit trails to the backup system, but no changes are applied to the backup database. The receiver continues to collect audit records from the extractor and writes these records to the image trails. However, the updater processes do not run while updating is disabled. Updating can be explicitly enabled or disabled through RDFCOM commands, as described later in this manual.
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 Audit-Fixup Process 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. Audit-Fixup Process The audit-fixup process only ever runs on the remote standby system in an RDF ZLT environment.
Introducing RDF Receiver Process Figure 1-6.
Introducing RDF Sorted Image Trails Sorted Image Trails RDF maintains its image data on disk volumes specified during RDF configuration. On each of these volumes, the collection of files that contains image data is known as an image trail; that is, there is one image trail per individual image trail volume. The standard image trail used by RDF is called the master image trail. This image trail is stored on the disk volume selected by the master receiver’s RDFVOLUME configuration option.
Introducing RDF Updater Processes Updater Processes An updater process is a process pair that runs on the backup system when updating is enabled or during takeover processing. Every volume on the primary system that is protected by RDF has its own updater process on the backup system.
Introducing RDF Updater Processes An updater cannot always respond immediately to the STOP UPDATE and STOP RDF commands. If an updater has audit information queued for the disk process, the updater must wait until all of that information is processed before it can shut down. You specify the primary and backup CPUs for each updater. If the original backup process has to take over because the primary CPU failed, this backup process runs by itself.
Introducing RDF Updater Processes UNDO Pass Updaters perform an UNDO pass over the image trail during final processing of RDF takeover and stop-update-to-time operations. This is because data already applied to the backup database must be undone if the associated transaction(s) did not commit prior to the start of the takeover operation or prior to the specified timestamp.
Introducing RDF Purger Process File System Errors Involving Data Files File system errors can occur when: • • • A file is created. A file is opened. A modify operation is performed on the file. Modify operations are those that the updater might perform on an open file, such as updating the file (logical REDO/UNDO) or altering the owner or security after the replication of a file creation. Errors encountered are reported in the EMS event log.
Introducing RDF Purger Process performance rate would be seriously degraded. Therefore, the receiver keeps general information about all transactions it has seen across all trails. Second, because considerable checking must be done across all trails to determine what files can be purged based on what transactions might be represented in the various files on the various image trails, the purger process performs this task.
Introducing RDF Reciprocal and Chain Replication Reciprocal and Chain Replication Figure 1-7. Reciprocal Replication System \A System \B RDF Subsystem 1 Primary DB 1 ----------------------------------> Backup DB 1 RDF Subsystem 2 Backup DB 2 <---------------------------------- Primary DB 2 Thus, you have a primary database for RDF subsystem 1 on system \A (primary DB 1) and a primary database for RDF subsystem 2 on system \B (primary DB 2). Figure 1-8.
Introducing RDF Reciprocal and Chain Replication If an updater transaction aborts, the TMF Backout process executes undo for the aborted transaction, and Backout has no information about what process generated the original audit for the transaction before it aborted. This can corrupt your primary and backup databases unless you take appropriate steps (see further below). Consider the following extension to the example above.
Introducing RDF Available Types of Replication to Multiple Backup Systems Available Types of Replication to Multiple Backup Systems RDF allows you to replicate database changes from a single primary system to multiple backup systems. This makes possible simultaneous read-only access to all of the backup systems, a capability particularly desirable for query-intensive applications where a central volatile database can be distributed to several remote systems for local access by queries.
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 $IMAGE..ZRDFNMTX (master image trail only) $IMAGE..ZRDFNMT2 (master image trail only) $IMAGE..ZRDFNMT3 (master image trail only) Triple Contingency If you are replicating your database to multiple backup systems, you can perform an RDF takeover to any of the backup systems upon loss of the primary system and continue application processing on the new system within minutes.
Introducing RDF Loopback Configuration (Single System) 2. On the backup system that received the least audit, use RDFCOM to execute the COPYAUDIT command. This command copies all the missing audit from the system that received the most audit to your present local system—the one that received the least audit. 3. Still on your same local backup system, use RDFCOM to execute a TAKEOVER command.
Introducing RDF Online Product Initialization Online Product Initialization You can initialize RDF/IMP, IMPX, or ZLT while your applications continue to run. This is particularly useful for installing new versions of RDF into existing production environments where you cannot afford to stop your applications even briefly to generate a TMF shutdown timestamp. It is also useful if you encounter a problem for which you would like to reinitialize RDF without stopping your applications.
Introducing RDF EMS Support EMS Support RDF/IMP, IMPX, and ZLT all support the Event Management System (EMS). They direct their command, event, warning, and error messages to an EMS collector in the form of fully-tokenized messages. You can view messages in the EMS log online using Viewpoint or any other tool you normally use for monitoring $0. Note that when you do so you are perusing the entire EMS log.
Introducing RDF Support for Network Transactions Support for Network Transactions The RDF/IMPX and ZLT products support network transactions: transactions that update data residing on more than one RDF primary system.
Introducing RDF • • • • Monitoring RDF Entities With ASAP RDFNET (optional) Receiver Purger Updater For information about using ASAP to monitor RDF entities, see Appendix E, Using ASAP.
Introducing RDF Monitoring RDF Entities With ASAP HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 1- 36
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 trails each time it rolls over to a new one. The purge operation is successful only if the audit trail is not pinned on behalf of RDF. If audit dumping is disabled and TMF were to purge an audit trail before it has been pinned, you must reinitialize RDF and resynchronize the databases.
Preparing the RDF Environment Preparing Databases for RDF Protection 2. TMF includes the functional capability of audit overflow volumes. You should always configure them with at least one overflow audit volume. Caution. Although RDF no longer requires you to configure TMF with a dump process that dumps to tape, you should nevertheless configure TMF for dumping to tape if you want to achieve full TMF protection for your primary database.
Preparing the RDF Environment Specifying System Generation Parameters for an RDF Environment Reload of Backup Database. If you need to reload the the backup database, you must change the UPDATEROPEN parameter from Protected (the default value) to Shared. When you are done with the reload, you should then change the UPDATEROPEN parameter back to Protected.
Preparing the RDF Environment • Designing Transactions for RDF Protection Database operations not replicated by RDF The subsections that follow explain these restrictions.
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 Management Manual for further information about the factors SMF uses to decide on the file placement. 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.
Preparing the RDF Environment Configuring an SMF Environment on the Backup RDF System HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 2- 14
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 creation default for NonStop SQL/MP tables and indexes. Although not required by RDF, audit compression will enhance RDF performance. Stopping the Software After you stop all applications protected by TMF, stop TMF itself by issuing a STOP TMF command through the TMFCOM interactive interface.
Installing and Configuring RDF Preparing the Backup System 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. In the backup copies, you need to change any occurrences of the primary system name to the backup system name.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases 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 from objects not protected by RDF. Either all the tables in a catalog should be protected or none of the tables should be protected. Every NonStop SQL/MP object maintained on the backup system must be registered in a catalog, even if the object is not protected by RDF.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases Re-Creating an Empty Database With an OBEY Command If a database on the primary system does not contain any data yet, use either an OBEY command file or a TACL macro to re-create the database on the backup system. To create logically identical database structures on the primary and backup systems, first do the following at the primary system: 1.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases 2. Set up DEFINEs on the primary system to simplify referring to NonStop SQL/MP tables in subsequent SQLCI commands for the primary system: SET DEFMODE ON; ADD DEFINE =EMPLOYEE, CLASS MAP, FILE \PRIM.$DATA1.DB.EMPLOYEE; ADD DEFINE =EMPLPAR2, CLASS MAP, FILE \PRIM.$DATA2.DB.EMPLOYEE; ADD DEFINE =EMPLNAME, CLASS MAP, FILE \PRIM.$DATA2.DB.EMPLNAME; 3.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases Now direct your attention to the backup system (\BACK). As you perform the necessary tasks on this system, note the following considerations: • • • DEFINEs cannot be used if you specify MAP NAMES option in the DUP command. The DUP operation moves the entire database, including all partitions and indexes, by default. The catalog \BACK.$DATA1.DBCAT is used for all partitions and all indexes. 8.
Installing and Configuring RDF Synchronizing the Primary and Backup Databases The next examples of BACKUP and RESTORE commands show how to copy all files from the primary system volumes $DATA01, $DATA02, $DATA03, and $DATA04 to the magnetic tape device named $TAPE and how to restore these files to volumes of the same name on the backup system. Note that you must include the AUDITED option in both the BACKUP and RESTORE commands. BACKUP $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*, $DATA04.*.
Installing and Configuring RDF Backing Up Application Programs and Files Backing Up Application Programs and Files To enable the backup system to take over in the event of a primary system failure, you need to put usable copies of all program files, OBEY command files, and other files your applications use on the backup system. You can do this by using the Autosync product.
Installing and Configuring RDF RDF/IMPX (T0347) Product Components RDFPRGO The RDF purger object code file RDFSCAN The RDFSCAN object code file RDFSCANH The RDFSCAN HELP file (an EDIT file) RDFSNOOP The RDFSNOOP object code file RDFUPDO The RDF updater object code file READLIST A diagnostic tool for analysts that reads undo lists and dumps data into entry-sequenced files RDIMAGE A diagnostic tool for HP analysts T0346ann The software documentation file (an EDIT file) RDFFLTO A filter to u
Installing and Configuring RDF Security Guidelines RDFINST licenses the following programs: RDFAFXO RDFCHEK RDFCOM RDFEXTO RDFMONO RDFPRGO RDFRCVO RDFSNOOP RDFUPDO RDIMAGE Security Guidelines The information that follows will help you establish appropriate HP NonStop Kernel operating system and Safeguard security for your RDF environment. Table 3-1 identifies the special security-related attributes for each type of program in an RDF environment. Table 3-1.
Installing and Configuring RDF Security Guidelines The following summarizes the reasons for the various security requirements of each RDF program: • • RDFAFXO. The RDFAFXO process uses privileged TMF procedures to fix the audit trail files and reset the CRASHOPEN flag in the audit trail file label and must be licensed with FUP or by running the RDFINST macro. RDFAFXO can be owned by any user ID. RDFCHEK.
Installing and Configuring RDF • • Initializing and Configuring TMF RDFUPDO. RDF updater programs open image files in privileged mode and must be licensed with FUP or by running the RDFINST macro. RDFUPDO also must be able to open database files for protected write access. When querying the backup database files, users should always open the files for shared read access. RDIMAGE. The RDIMAGE program opens the image files in privileged mode and must be licensed with FUP or by running the RDFINST macro.
Installing and Configuring RDF TMF Subsystem Running Previously TMF Subsystem Running Previously If TMF was running on the primary system and you have shut the TMF subsystem down, and if you have started TMF on the backup system and added the RDF updater volumes to the TMF configuration, you need not take any other steps with respect to TMF. Proceed to the next task, described in Initializing RDF.
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 Online Installation and Initialization Without Stopping TMF Online Installation and Initialization 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.
Installing and Configuring RDF Online Installation and Initialization Without Stopping TMF and you must purge the existing file. The updater will continue to report the error until you have purged the file. Stop-RDF-Updater Records Stop-RDF-Updater records in the MAT are associated with committed NonStop SQL/MP DDL operations performed on the primary system with the SHARED ACCESS option.
Installing and Configuring RDF Online Installation and Initialization Without Stopping RDF Online Installation and Initialization Without Stopping RDF For the procedure described under Online Installation and Initialization 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 5. Issue the STOP UPDATE command. Note, this command stops the updaters but allows the extractor and receiver to continue to shipping and storing audit, respectively. 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.
Installing and Configuring RDF Configuring RDF What about disaster points? If the primary system fails between steps 1 and 10, you perform the takeover operation using your previous RDF subsystem. If the primary system fails at or after step 11, you perform the takeover operation using the new subsystem (RDF04A). 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.
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 SOFTWARELOC Parameter The SOFTWARELOC parameter specifies where the RDF software is installed on both the primary and backup systems. The default is $SYSTEM.RDF. UPDATERDELAY Parameter The UPDATERDELAY parameter specifies how many seconds (from 1 to 10) the updater processes should delay upon reaching the logical EOF in the image trail before attempting a new read operation. The default is 10 seconds.
Installing and Configuring RDF Configuring RDF Setting Individual Process Parameters Having set the global parameters, you are now ready to set the parameters that apply to individual RDF processes: the monitor, extractor, receiver, purger, and updater processes.
Installing and Configuring RDF Configuring RDF Extractor Process Use SET EXTRACTOR and ADD EXTRACTOR commands to configure the following extractor parameters: • • • • • ATINDEX CPUS primary-CPU : backup-CPU PRIORITY PROCESS RTDWARNING The CPUS option value specifies the processors in the primary system in which the extractor will run. The PRIORITY option value specifies the priority at which the extractor will run.
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 CPUS option value specifies the processors in the backup system in which the receiver is to run. The EXTENTS option value only applies to the master receiver.
Installing and Configuring RDF Configuring RDF RDF image trail file (with a primary extent size of 3000 pages and a secondary extent size of 3000 pages) reside on the volume $IMAGE, issue the following commands: ]SET ]SET ]SET ]SET ]SET ]SET ]ADD RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER PROCESS $RECV CPUS 0:2 PRIORITY 185 RDFVOLUME $IMAGE EXTENTS (3000,3000) ATINDEX 0 You cannot start RDF until you have configured a master receiver process.
Installing and Configuring RDF Configuring RDF Purger Process Use SET PURGER and ADD PURGER commands to configure the following purger parameters: • • • • • CPUS primary-CPU : backup-CPU PRIORITY PROCESS RETAINCOUNT PURGETIME The CPUS option value specifies the processors in the backup system in which the purger is to run. The PRIORITY option value specifies the priority at which the purger will run.
Installing and Configuring RDF Configuring RDF Updater Processes Use SET VOLUME and ADD VOLUME commands to configure the following updater parameters: • • • • • • • • ATINDEX CPUS primary-CPU : backup-CPU EXCLUDE IMAGEVOLUME INCLUDE PRIORITY PROCESS UPDATEVOLUME You must configure an updater process for each primary system volume to be protected by RDF. The CPUS option value specifies the processors in the backup system in which the updater will run.
Installing and Configuring RDF Configuring RDF The following guidelines are strongly recommended: • • There should be an identical one-to-one volume relationship between volumes on the primary system and those on the backup system. Each backup volume should have the same name as the associated primary volume.
Installing and Configuring RDF Creating a Configuration Command File The PRIORITY option value specifies the priority at which the RDFNET process will run. You should set the RDFNET process’ priority slightly lower than that of the RDF monitor process. The PROCESS option value supplies a name for the RDFNET process. You should specify a meaningful mnemonic such as $RNET. The process name can be any unique valid process name up to 5 characters, including the $ symbol.
Installing and Configuring RDF Starting RDF ENABLE BEGINTRANS. For details about these TMFCOM commands, see the HP NonStop Transaction Management Facility (TMF) Reference Manual. Starting RDF There are two ways to start RDF: with updating enabled and with updating disabled. If updating is enabled, the updaters begin updating the backup database immediately. If updating is disabled, they do not (but the extractor and receiver continue to work normally). The default is to start RDF with updating enabled.
Installing and Configuring RDF Restarting the Applications If you want to start RDF with the updater processes disabled, you should specify the UPDATE OFF option in the START RDF command on the primary system as follows: ]START RDF, UPDATE OFF If you later want to start the updater processes, you merely issue a START UPDATE command. Restarting the Applications As the final step in establishing an RDF environment, if you shut down your applications previously you must restart them.
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 - T0346A06 - 14MAR04 (C)1988 Tandem (C)2004 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 INFO { { { { { { { { { { INITIALIZE * IMAGETRAIL RDF MONITOR EXTRACTOR RECEIVER RDFNET NETWORK PURGER VOLUME Function } } } } } } } } } } Displays current option values from the RDF configuration file for the specified process or for all processes (*). Initializes RDF.
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 Requesting Online Help Table 4-3. RDFCOM Utility Commands Command Object Function OBEY filename Causes RDFCOM to read commands from the specified command file. OPEN control-subvolume Sets the RDF control subvolume to $SYSTEM.control-subvolume, thereby setting up RDF for access to that configuration. OUT filename Redirects subsequent session output to the specified device or file.
Operating and Monitoring RDF Requesting Online Help Help for Command Syntax To obtain syntax information for an individual command, enter HELP followed by the command name. For example, to display the ADD command syntax, enter: ]HELP ADD RDFCOM displays the following: { { { { ADD { { { { { { RDF MONITOR EXTRACTOR RECEIVER IMAGETRAIL $volume PURGER RDFNET NETWORK VOLUME $volume $volume } } } } } } } } } } Cannot be performed with RDF running. Only a user in the SUPER group can execute this command.
Operating and Monitoring RDF Requesting Online Help Utility Commands: EXIT FC HELP HISTORY OBEY OPEN OUT RDF Concepts: Abbreviations RDF error messages: E.g.
Operating and Monitoring RDF Running RDFSCAN 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 Using RDFSCAN Using RDFSCAN When you use RDFSCAN, you conduct an interactive dialog with it through prompts, commands, output displays, and messages. RDFSCAN has two operational restrictions: • • RDFSCAN does not use command files; you must enter all RDFSCAN commands from the terminal. RDFSCAN accepts only one command per prompt.
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 Help for Command Syntax To obtain syntax information for an individual command, enter HELP followed by the command name. As an example, to display information for the LIST command, enter HELP LIST after the prompt: Enter the RDFscan function you want: HELP LIST In response, RDFSCAN displays the following: LIST List will display records from the current-record pointer (set with AT.
Operating and Monitoring RDF Performing Routine Operational Tasks Introductory Usage Information To display a brief introduction to the purpose, features, and use of RDFSCAN, enter HELP INTRO, as follows: Enter the next RDFscan function you want: HELP INTRO In response, RDFSCAN displays: RDFSCAN is a utility for quickly scanning the RDFLOG file. When you run RDFSCAN it calculates the last-record-number and displays it for you. You can then selectively list (display) various portions of the file.
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 (*****), the updater has experienced a critical error. If the updater is doing an undo pass, the word undo appears in the Error column. If RDFCOM cannot reach a particular process, the Error column for that process contains the applicable file system error number. The occurrence of a critical error could mean that the backup database is no longer synchronized with the primary database because of data loss.
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 The STATUS RDF display shows the priority at which each RDF process is running. Suppose this display indicates that the monitor currently runs at a priority of 165. To change its priority to 170, use the ALTER command as follows: ]ALTER MONITOR PRIORITY 170 EMS Logs (Collectors) In an RDF configuration, two EMS logs (collectors) exist: one at the primary system and the other at the backup system.
Operating and Monitoring RDF Reading Log Messages To isolate RDF messages from the rest of the EMS log, you can use the standard EMS filter RDFFLTO to produce an intermediate entry-sequenced file which you then can scan using the RDFSCAN utility. As noted earlier in this section, when you access RDFSCAN, this utility displays current information about the RDF message file, including the number of the last record.
Operating and Monitoring RDF Reading Log Messages The following sample RDFSCAN session shows another example of how you might use RDFSCAN to examine messages in an RDF message file. The actual line length for RDFSCAN is 132 columns (not 58 as shown in this example). On the terminal screen, lines over 80 columns long wrap to the next line. User input appears in boldface type. Notice also that record numbers, which do not appear in the previous display, have been enabled for this one.
Operating and Monitoring RDF Reading Log Messages HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 4- 26
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 The event is reported in the EMS event log, with the error causing the process that received it to restart from a previously set restart point. The event is reported in the EMS event log, and the requested operation is skipped. For information about restart points, see Updater Processes in section 1. To analyze an error, consult the appropriate table in this discussion, reading about any corrective action specific to RDF.
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 59 Check file integrity. 60 through 66 Repair the device or clear the condition. 71 Check the file integrity. This could mean either loss of data or duplicated audit information. If data was lost, resynchronize the file. If audit information was duplicated, then no harm occurred. The updater process skips the modify operation.
Managing RDF Recovering From File System Errors Table 5-2. Recovery From File Open Failures (RDF Event 705) (page 2 of 2) File System Error Recovery Action 130 through 139 Repair the device or clear the condition. 157 Check file integrity. 190 Repair the device or clear the condition. 199 Alter the security (probably Safeguard). 200 through 231 Repair the device or clear the condition.
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 • • Communications 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
Managing RDF Processor Failures If any RDF process pair stops unexpectedly, the monitor sends an abort message to all other RDF processes. Note. If the monitor process pair unexpectedly stops (for example, as in a double CPU failure), you must stop the other RDF processes manually and then restart the subsystem. The easiest way to do this is to issue a series of commands of the following form: STATUS *,PROG RDFsoftware-loc.procname, STOP.
Managing RDF Processor Failures Updater Failure If an updater process fails, RDF aborts. A subsequent START RDF command restarts this process without requiring database resynchronization. To support restartability, however, the updaters use a different mechanism than the extractor or receiver: the updaters rely entirely on context saving rather than checkpointing.
Managing RDF TMF Audited Volume Crash If a state transition failure occurs during execution of a STOP UPDATE command and the operation appears to be stalled, manually stop all of the RDF updaters by issuing the following command on the backup system: STATUS *, PROG RDF-software-loc.RDFUPDO, STOP Caution. Issuing this command in this situation is only safe, however, if this is the backup system for a single RDF environment.
Managing RDF TMF Subsystem Crash 5. Restart RDF through RDFCOM by entering: ]START RDF Note. Normally you start RDF before starting your applications. If the TMF subsystem has crashed on the primary system, however, characteristics of the TMF audit trail after the TMF subsystem is restarted require that you restart your applications before restarting RDF. This allows audit information to be generated in the MAT and any auxiliary audit trails involved in your RDF environment. At that point you restart RDF.
Managing RDF TMF File Recovery Operations TMF File Recovery Operations Primary System A file recovery operation occurs whenever a TMFCOM RECOVER FILES command is issued at the primary system. A simple file recovery does not affect RDF and does not require database resynchronization. A file recovery to a timestamp, first purge, or TOMATPOSITION, however, does require you to stop RDF and resynchronize the affected files. Caution.
Managing RDF Stopping RDF by Stopping TMF the updater processes stopped at the shutdown record (if an updater experiences a double CPU failure, the databases will not be identical). The disadvantage of this approach is that all applications on the primary system that use TMF must be stopped also. Stopping TMF also automatically unpins all audit trail files that were pinned on behalf of RDF. When you issue a TMFCOM STOP TMF command, the following events occur: 1. TMF writes a shutdown record to the MAT.
Managing RDF Stopping RDF From the Primary System command. In this case, RDF stops processing without reading to the TMF shutdown record in the MAT. Note. For this scenario to work, you must issue the STOP RDF command on both systems before the communications lines come back up. When you restart TMF, you must then restart RDF. RDF begins processing at the point where it stopped. When RDF reads the TMF shutdown record associated with the preceding TMF shutdown, RDF shuts down.
Managing RDF Stopping RDF From the Backup System When you issue a STOP RDF command from the primary system, the following events occur: 1. RDFCOM sends a STOP message to the monitor. 2. The monitor sends stop messages to the extractor(s), the receiver(s), the purger, the updater(s), and, if there is an RDF network, the RDFNET process. 3. The monitor stops after all RDF processes have stopped.
Managing RDF Restarting RDF An alternative way to stop RDF on the backup system is to enter the following command through TACL: >STATUS *, PROG RDF-software-loc.*, STOP Caution. Issuing this command in this situation is only safe, however, if this is the backup system for a single RDF environment. 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.
Managing RDF Reciprocal Configurations At this point, the RDF subsystem is stopped, the business applications from system \A are running on system \B, and all audit information is being queued in TMF audit trails on system \B. 5. When system \A is ready to resume its normal operations, restart TMF on \A. 6. On system \B, issue an INITIALIZE RDF command using the INITTIME option and specifying the local system time you noted in step 3.
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 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 You then configure the RDF subsystem to run from the backup to the primary system to bring the primary database back up to date with updates that took place while the primary was down. When the primary database is fully current, you then perform a planned switchover from the backup to the primary system, and restart your applications on the primary system.
Managing RDF Restoring the Primary System Before application processing starts on the backup system following a successful takeover operation, you might need to update statistics for NonStop SQL/MP database tables and recompile NonStop SQL/MP program files. Note. If you are using the triple contingency feature, you must issue a COPYAUDIT command after the takeover operations are complete to copy missing audit from the backup system that has the most to the one that has the least.
Managing RDF Reading the Backup Database Offline Method of Resynchronizing the Primary Database When the failed primary system is restored to operable condition, you can take the following steps to restore the original RDF configuration and make the old primary database the current primary database again (where \A is the old primary system and \B is the old backup system): 1. Stop the applications and TMF on \B. 2. Save the database on \B to tape. 3. Restart the applications and TMF on \B. 4.
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 Backing Up Image Trail Files 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 2. When the purger tries to purge AA000007 and fails, it writes a message denoting this error to the EMS event log. This message implies that all updaters have moved from AA000007 to AA000008 (or beyond), and will never need AA000007 again; it is your only way to know for certain that AA000007 will never be needed again. When this message is written, you can start the backup process to dump AA000007 to tape. 3.
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.
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 Databases Catalog Changes RDF views NonStop SQL/MP DDL operations as updates to catalogs. NonStop SQL/MP catalogs themselves are audited tables, even on the backup system. NonStop SQL/MP DDL operations are not replicated by RDF; therefore, RDF does not apply updates to catalogs.
Maintaining the Databases NonStop SQL/MP 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 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 Databases return fewer rows for the index than indicated by the FUP INFO command. The row count continues to grow in the base table, but remains the same for the index. You can avoid this problem by always using the KEYTAG clause in the CREATE INDEX command to define a meaningful key specifier for each index you create. If you encounter the problem described above, use SQLCI to DROP and re-CREATE the offending indexes, doing so in the proper creation order.
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 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. Finally, resume application processing.
Maintaining the Databases • • Resynchronizing Entire Databases Offline An additional volume is configured into an existing RDF configuration while TMF is running, in which case database tables and files on the updater’s primary volume might not be synchronized with the corresponding tables and files on the backup volume. In this case, you must only resynchronize that single volume. TMF is deleted and reconfigured, or RDF is reinitialized, after a STOP RDF command is issued at the primary system.
Maintaining the Databases Resynchronizing Individual Tables or Files Offline 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. Resynchronizing Individual Tables or Files Offline If you are sure that only certain database tables or files might not be synchronized, all you need to do is synchronize those tables or files. To resynchronize an individual table or file, do as follows: 1.
Maintaining the Databases Resynchronizing Individual Tables or Files Offline HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 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. 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. issue a START RDF, UPDATE OFF command.
Online Database Synchronization Synchronizing Entire Databases Online Synchronizing Entire Databases Online To synchronize an entire RDF backup database to the primary database online, do as follows. 1. If RDF is currently running, issue a STOP RDF command on the primary system. 2.
Online Database Synchronization Synchronizing Entire Databases Online detailed information, see “Phases of Online Database Synchronization” later in this section. 7. If the duplicate tables and files were created on the primary system in step 4, use BACKUP/RESTORE or FUP DUP operations to copy them to the backup system.
Online Database Synchronization Considerations When Synchronizing Entire Databases Considerations When Synchronizing Entire Databases The considerations for online synchronization fall into the following categories: • • • • • • Duration of loads and getting the database prepared on the backup system SYNCHDBTIME issues CREATE/LOAD issues for NonStop SQL/MP tables and Enscribe files Enscribe queue file issues Different versions of NonStop SQL/MP on the primary and backup systems Moving the duplicated tabl
Online Database Synchronization Considerations When Synchronizing Entire Databases SYNCHDBTIME Issues With the SYNCHDBTIME option in the INITIALIZE RDF command, there are three special cases you might need to consider: • • • Enscribe create operations NonStop SQL/MP Shared Access DDL operations TMF shutdown operations Enscribe Create Records If you created the same Enscribe file on the primary and backup systems prior to execution of the INITIALIZE RDF command, and if the extractor’s restart position i
Online Database Synchronization Considerations When Synchronizing Entire Databases As a precaution, if RDFCOM encounters a Stop-RDF-Updater record during its backward search of the MAT, it issues a warning message to that effect asking if you want to proceed with initialization. If the extractor encounters such a record while operating in database synchronization mode, it abends.
Online Database Synchronization Considerations When Synchronizing Entire Databases General Considerations for NonStop SQL/MP Tables • • • • • • Key-sequenced Tables without SYSKEY. To improve the performance of the load operations significantly, specify the SORTED option. Key-sequenced Tables with SYSKEY. Because the SQLCI LOAD operation generates new SYSKEY values, key-sequenced tables containing SYSKEYs cannot be synchronized online. Relative Tables.
Online Database Synchronization Considerations When Synchronizing Entire Databases Different NonStop SQL/MP Product Versions If you have different versions of the NonStop SQL/MP product on your primary and backup systems, refer to the HP NonStop SQL/MP Version Management Guide for information about what you can do and how to do it.
Online Database Synchronization • Example of Synchronizing An Entire Database Online If you move duplicate Enscribe alternate key files, you must alter the system name in the file label of the duplicate file or table to specify the backup system. For example, if you moved a duplicate Enscribe alternate key file named ALTF0100 associated with the file PART0100, you must change the system name in the file label of the duplicate alternate key file to that of the backup system as follows: FUP ALTER $DATA1.
Online Database Synchronization Example of Synchronizing An Entire Database Online set type k, keyoff 2, keylen 4, no audit set buffered, ext(10,10) set rec 300, block 4096 set maxextents 16 set code 4700 set part (1, $data3, 2, 2, [0,0,0,195] ) set altkey (1, file 0, keyoff 6, keylen 2 ) set altkey (2, file 0, keyoff 6, keylen 2 ) set altkey (3, file 0, keyoff 6, keylen 2, no update ) set altkey (4, file 0, keyoff 6, keylen 2, no update ) set altkey (5, file 0, keyoff 6, keylen 2 ) set altfile (0, $data2
Online Database Synchronization Example of Synchronizing An Entire Database Online volume $data1.test load load load load part0200, part0201, altf0200, altf0201, $data3.test.part0200, $data3.test.part0201, $data3.test.altf0200, $data3.test.altf0201, share, share, share, share, sorted, no compact sorted, no compact sorted sorted 5. After the load operations in step 5 are done, issue the following RDFCOM command: STOP SYNCH 6. Use FUP DUP commands to move the duplicate files to the backup system.
Online Database Synchronization Synchronizing Selected Database Portions Online Synchronizing Selected Database Portions Online There are a number of reasons why you might want to synchronize only selected portions of your database. For example: • • • If you have a large database, it might be easier to break the total number of volumes into subsets, and then synchronize one subset at a time. If a file or table has become corrupt, you might want to synchronize just that one file.
Online Database Synchronization Partial Database Synchronization Issues Example #2 – Synchronization of an Individual Volume Suppose you just need either to synchronize a new volume to an existing RDF configuration, or you need to re-synchronize an existing volume in your configuration. You would first stop your current RDF subsystem. You then delete your current RDF control subvolume and initialize a new RDF subsystem, using the SYNCHDBTIME option.
Online Database Synchronization Partial Database Synchronization Issues There are a variety of considerations when synchronizing portions of a database. Read the following carefully. Enscribe Files Without Partitions Key-sequenced and Relative Files First create a non-audited duplicate file on the primary system and then load it. Then use BACKUP and RESTORE (or FUP DUP) to move the duplicate file to the backup system.
Online Database Synchronization Partial Database Synchronization Issues To load the secondary partition only, issue the following command: FUP LOAD $DATA2.TEST.PART0100, $DATA2.TEMP.PART0100, PARTONLY,SHARE When the load operations are finished, use BACKUP and RESTORE (or FUP DUP) with the PARTONLY option to copy the partition you need to the backup system. Relative Files First create a non-audited duplicate file on the primary system. Note that you must create the entire file with all its partitions.
Online Database Synchronization Partial Database Synchronization Issues There are no special considerations for key-sequenced tables with indexes, but see below for issues regarding the synchronization of indexes. NonStop SQL/MP Tables With Partitions The utilities associated with and related to the NonStop SQL/MP product have limitations that make synchronization of individual partitions complicated and difficult. The following represent methods that enable you to circumvent these limitations. 1.
Online Database Synchronization Partial Database Synchronization Issues Thus, you now have on tape empty partitions for the entire table. Should you ever lose a volume to a complete media failure, you can install a new disk and then use the RESTORE utility with the PARTONLY option to recover the missing partition.
Online Database Synchronization Partial Database Synchronization Issues 5. Use the SQLCI LOAD command with the PARTONLY and SHARED options to load only the primary partition of the duplicate table. Note that you cannot use PARTONLY with the LOAD command if your duplicate table has indexes. Therefore, if you created your duplicate table with indexes, you must drop the indexes. 6. When the load has completed, issue the RDFCOM STOP SYNCH command. 7.
Online Database Synchronization Partial Database Synchronization Issues 16. When the extractor has logged the message indicating it has completed its role in the online synchronization operation, issue the RDFCOM START UPDATE command on your primary system. Note that the above method preserves indexes you may have on the backup system.
Online Database Synchronization Partial Database Synchronization Issues If the table whose primary partition needs to be synchronized has indexes, do not create indexes for the duplicate table. 5. Use the SQLCI LOAD command with the SHARED option to load the entire table. Again, with relative tables, you must load the entire table. 6. When the load has completed, issue the RDFCOM STOP SYNCH command. 7.
Online Database Synchronization Phases of Online Database Synchronization 16. When the extractor has logged the message indicating it has completed its role in the online synchronization operation, issue the RDFCOM START UPDATE command on your primary system. NonStop SQL/MP Indexes (With or Without Partitions) To synchronize indexes with or without partitions, do the following: 1. Drop the indexes on the backup system. 2. Create new indexes on the backup system.
Online Database Synchronization Updater Phase 2 image record (which is stored in all image trails by the receiver). All transactions that might have been started during the create/load or backup operations are now finished. Note. TMP control points are generated as the result of transaction activity. For high rates of transaction activity, the TMP control points might be only 1 or 2 minutes apart. For lower rates, they might be 5 to 10 minutes apart.
Online Database Synchronization • When Is Online Database Synchronization Complete? If the restart condition occurs after phase 1 has begun, the extractor may choose to resume at an earlier position than the receiver tells it to. It does this to ensure that it has handled all committed and aborted transactions correctly. If the extractor does resume at an earlier position, it logs message 775.
Online Database Synchronization Updater Messages HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 7- 24
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. Security Restrictions While several RDFCOM commands are available to all users, others impact the overall RDF environment and are restricted to members of the super-user group.
Entering RDFCOM Commands Usage Guidelines RDFNET NETWORK P P P P P P P P P P P P P P 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 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.
OTHER OBJECTS NETWORK RDFNET VOLUME UPDATE PURGER RECEIVER RDF MONITOR IMAGETRAIL Output Displayed EXTRACTOR Entering RDFCOM Commands TAKEOVER O UNPINAUDIT S VALIDATE S Legend A = All users S = Super-user group only O = owner of RDF subsystem * = Must also have remote passwords for both nodes X = Depends on which commands are in the file ** = RTDWARNING *** = SYNCH Output Displayed For the RDFCOM commands that display output at your terminal (for example, the INFO, SHOW, and STATUS serie
Entering RDFCOM Commands Reserved File Names The system does not distinguish between uppercase and lowercase alphabetic characters in a file name. If all the optional left-hand parts of a file name are present, it is called a fully qualified file name; if any of the optional left-hand parts are missing, it is called a partially qualified file name. For more information about file names and process identifiers and the rules that govern them, see the Guardian Procedure Calls Reference Manual. Note.
Entering RDFCOM Commands Nondisk Device Names temp-filename specifies the name of a temporary disk file. A temporary-file name consists of a pound-sign (#) followed by four to seven numeric characters. The operating system assigns names to temporary files. The following is an example of a fully qualified disk file name: \hdq.$mkt.reports.finance Nondisk Device Names The syntax for a file name that identifies a nondisk device is: [system.]device-name[.qualifier] or [system.
Entering RDFCOM Commands Process File Names ldev-number specifies a logical device number. A logical device number is represented by a dollar sign ($) followed by a maximum of five digits. The logical device number 0 (represented “$0”) is reserved for the Event Management Service (EMS) collector process. Note. Wherever possible, use the device-name form of a nondisk device identifier instead of the ldev-number form.
Entering RDFCOM Commands Command Overview configuration record with the DELETE command, or clear the entire table with the INITIALIZE RDF command. In the configuration file, unlike the configuration memory table, the parameter settings remain unchanged until you explicitly alter them. The settings in the file are not affected by the end of a session—when you start a new session, the values that existed at the end of the last session survive into the new session.
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 } } } } } } } } } RDF applies RDF global configuration parameters. MONITOR applies configuration parameters for the monitor. EXTRACTOR applies configuration parameters for an extractor.
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. Where Issued Primary system only. Security Restrictions You can issue the ADD command only if you are a member of the super-user group.
Entering RDFCOM Commands Command Overview The master image trail identified by the RDFVOLUME parameter in the SET RECEIVER command is reserved for use by the MAT receiver process. All updaters must be configured to secondary image trails. Each image trail is stored on a separate volume on the backup system. To add a secondary image trail, you specify the disk volume intended for its use through the ADD IMAGETRAIL command.
Entering RDFCOM Commands Command Overview UPDATERTXTIME: 60 UPDATERRTDWARNING: 60 NETWORK: OFF NETWORKMASTER: OFF REPLICATEPURGE: OFF LOCKSTEPVOL: (omitted) Suppose you want to protect the volume $DATA01 on the primary system by configuring an updater process for the volume $DATA1 and secondary image trail $SECIT1 on the backup system (assuming that $SECIT1 was previously added to the RDF configuration by way of an ADD IMAGETRAIL command).
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 reinitialize RDF and use another SET RECEIVER RDFVOLUME command followed by an ADD RECEIVER command. If you need to change an updater’s image trail volume, it is recommended that you stop TMF; wait for RDF to stop; delete the volume; re-add the volume back into the configuration, associating it to a different image trail volume; and then restart the TMF and RDF subsystems.
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 or updater process from the RDF configuration file. DELETE {IMAGETRAIL $volume} [ATINDEX audittrail-index-number] {[VOLUME] $volume } {$volume } 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 The extractor process stops sending image data for the volume specified in the DELETE VOLUME command. The updater process associated with this volume will not be started. Use the DELETE VOLUME command if an update volume on the backup system becomes unusable and you want RDF to continue maintaining the other volumes. In such a case, you must stop RDF at the primary system, issue the DELETE VOLUME command, and then restart RDF.
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 LOGDEVICE RDF LOGFILE RDF PRIMARYSYSTEM RDF UPDATERDELAY RDF UPDATERTXTIME RDF UPDATERRTDWARNING RDF UPDATEROPEN RDF NETWORK RDF NETWORKMASTER RDF UPDATEREXCEPTION RDF REPLICATEPURGE $SYSTEM.
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 RDFCOM displays the following: Keywords can be abbreviated by the capitalized portion of the word as shown in the table below.
Entering RDFCOM Commands Command Overview To list all available RDFCOM commands, enter: ]HELP ALL RDFCOM displays the following: Help is available for the following: Configuration Commands: ADD ALTER { RDF | MONITOR | EXTRACTOR | RECEIVER | PURGER | RDFNET | VOLUME } DELETE INFO INITIALIZE RESET SHOW SET { RDF | MONITOR | EXTRACTOR | RECEIVER | IMAGETRAIL | PURGER | RDFNET | VOLUME } Operational Commands: COPYAUDIT START STATUS STOP TAKEOVER UNPINAUDIT VALIDATE Utility Commands: EXIT FC HELP HISTORY OBEY
Entering RDFCOM Commands Command Overview To display information about RDF message #715, enter: ]HELP 715 RDFCOM displays the following description: ------------------------------------------------------------| 715 Primary Stopped | ------------------------------------------------------------Cause: The primary process of a NonStop process pair has stopped. This probably was the result of an operator inadvertently issuing a STOP command from TACL.
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. INFO {* {IMAGETRAIL {RDF {MONITOR {EXTRACTOR {RECEIVER {RDFNET {NETWORK {PURGER {VOLUME * {[VOLUME] $volume } } } } } } } } } } } [ATINDEX audittrail-index-num] [,OBEYFORM] * displays the current configuration parameter values for the RDF global options, for all updater volumes, and for all RDF processes.
Entering RDFCOM Commands Command Overview The subsystem saves the text in the command file, also embedding the appropriate SET and ADD commands. Any time you want, you can execute the text by specifying the command file name in an OBEY command or in the IN option of the RDFCOM command that begins a session, producing a new RDF configuration based on the one captured by the INFO command.
Entering RDFCOM Commands Command Overview Where Issued Primary or backup system. Security Restrictions None; anyone can enter the INFO command. RDF State Requirements You can enter the INFO command any time after RDF has been initialized. Usage Guidelines This command retrieves its information from the RDF configuration file.
Entering RDFCOM Commands Command Overview 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 RECEIVER RECEIVER RECEIVER ATINDEX 0 CPUS 1:2 EXTENTS (1000,1000) PRIORITY 165 RDFVOLUME $DATA2 SLOWMODE OFF PROCESS $RECV IMAGETRAIL ATINDEX 0 IMAGETRAIL $SEC
Entering RDFCOM Commands Command Overview 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 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 to 170 (using an ALTER command).
Entering RDFCOM Commands Command Overview RDF displays the following: VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME $DATA01 ATINDEX 0 CPUS 0:1 IMAGEVOLUME $SECIT1 PRIORITY 170 PROCESS $UP1 UPDATEVOLUME $DATA1 Now, suppose you configured three updater processes (named $UP01, $UP02, and $UP03) and that those processes are backing up the primary system volumes $DATA01, $DATA02, and $DATA03, respectively, onto the volumes $DATA1, $DATA2, and $DATA3 on the backup system.
Entering RDFCOM Commands Command Overview 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: PURGER PURGER PURGER PURGER PURGER CPUS 3:2 PRIORITY 165 PROCESS $PURG RETAINCOUNT 50 PURGETIME 60 INFO RDFNET Comma
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 : is a timestamp used for online product initialization. It has the same format as the timestamp parameter described above.
Entering RDFCOM Commands Command Overview For a description of the online synchronization feature, see Section 7, Online Database Synchronization. ! causes the command to be executed without further confirmation. If you omit the exclamation point, RDFCOM prompts you for additional responses as follows: • If you omit the TIMESTAMP, INITTIME, SYNCHDBTIME, and ! options, RDFCOM displays: Are you sure you want to initialize? [Y/N] Enter Y or YES to proceed; enter N or NO to cancel the command.
Entering RDFCOM Commands • Command Overview If you include the SYNCHDBTIME 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. Synch point for 12JAN2004 14:30 has been found. RDF will start at RBA: 376275 MAT file: $AUDIT.ZTMFAT.
Entering RDFCOM Commands Command Overview ADD commands or by executing a command file containing those commands. Only then can you issue the START RDF command to start RDF. The INITIALIZE RDF command also establishes the name of the RDF control subvolume, which you subsequently specify when initiating RDFCOM sessions or in OPEN commands.
Entering RDFCOM Commands Command Overview If you initialize RDF to the timestamp corresponding to Step b, you should restore on the backup system a copy of the primary system database taken at Step b. • • Initialize RDF at the most recent TMF shutdown point. If you initialize RDF at an earlier shutdown point, RDF operations will start at that point but will shut down when the next TMF shutdown point is reached.
Entering RDFCOM Commands Command Overview The following INITIALIZE RDF command, issued on the primary system \LON after TMF was stopped, deleted, and reconfigured, initializes RDF at once, without prompting you to confirm your request: ]INITIALIZE RDF, BACKUPSYSTEM \CHI, SUFFIX 2 ! Note that in the first example above the RDF control subvolume is implicitly named LON while in the second example it is explicitly named LON2.
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 } } } } } } } } } RDF resets the values for the RDF global options.
Entering RDFCOM Commands Command Overview NETWORK resets the values for the network configuration 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 REDFNETWORK, SET RECEIVER, and SET VOLUME command descriptions. Where Issued Primary system only. Security Restrictions You can issue the RESET command only if you are a member of the super-user group.
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 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 RDF State Requirement You can only enter the SET RDF command for global configuration parameters if you have not already used the ADD RDF command to apply the parameter values to the RDF configuration file. For further information, see the ADD command description. Usage Guidelines The SET RDF command enters the global parameter values specified in this command into the RDF configuration table in memory.
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 You can issue the SET RECEIVER command only if you are a member of the superuser group. RDF State Requirement There is no point in issuing SET RECEIVER commands after RDF is started. For further information, see the ADD command description.
Entering RDFCOM Commands Command Overview By default, in this example the receiver process is associated with the MAT and will run at a priority of 165. To configure an auxiliary receiver process named $RCV1 associated with the auxiliary audit trail AUX01 to run in CPUs 2 and 3, issue the following commands: ]SET ]SET ]SET ]ADD RECEIVER PROCESS $RCV1 RECEIVER ATINDEX 1 RECEIVER CPUS 2:3 RECEIVER By default, in this example the auxiliary receiver process will run at a priority of 165.
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. SHOW {RDF {MONITOR {EXTRACTOR {RECEIVER {IMAGETRAIL {VOLUME {PURGER {RDFNET {NETWORK } } } } } } } } } RDF displays the current configuration parameter values for the RDF global options.
Entering RDFCOM Commands Command Overview 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 RDF RDF RDF RDF RDF RDF UPDATERRTDWARNING UPDATEROPEN NETWORK NETWORKMASTER UPDATEREXCEPTION REPLICATEPURGE Command Overview 60 PROTECTED OFF OFF ON OFF 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 RDFCOM includes the line containing PROCESS process-name in the display only if the process name was specified in a SET command. SHOW VOLUME Command Suppose that a series of SET VOLUME commands specified the following configuration parameter values: • • • The updater process named $UP07 is to run in CPUs 2 and 1 of the backup system at a priority of 160.
Entering RDFCOM Commands Command Overview SHOW NETWORK Command Suppose that a series of SET NETWORK commands specifies \RDF04 as the network master’s primary system, \RDF06 as the network master’s backup system, RDF04 as the network master’s remote control subvolume, and $DATA07 as the network master’s PNETTXVOLUME volume.
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 only if you are a member of the superuser group and have remote passwords on both the primary and backup systems. 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 - T0346A06 - 14MAR04 (C)1988 Tandem (C)2004 Hewlett Packard Development Company, L.P. Status of \RDF04 -> \RDF05 RDF 2004/04/14 14:08:19.072 Control Subvol: $SYSTEM.
Entering RDFCOM Commands Command Overview 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. In the above example, the extractor $RE01 and receiver $RR01 are associated with the MAT, while the extractor $RE02 and receiver $RR02 are associated with auxiliary audit trail AUX01.
Entering RDFCOM Commands Command Overview receiver is the difference between the “last modified time” of the TMF MAT and the timestamp that identifies the associated restart point. 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.
Entering RDFCOM Commands Command Overview Rel Byte Addr 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 Addr 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 If RDFCOM cannot connect to a particular process, RDFCOM displays dots (...) in the RTD Time, Sequence, and Rel Byte Addr fields and an appropriate File System error number in the Error field. 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 Where Issued Primary or backup system. Security Restrictions You can issue the STOP RDF command only if you are a member of the super-user group that initialized RDF and have remote passwords on both the primary and backup systems. RDF State Requirement You can issue the STOP RDF command only when RDF is running.
Entering RDFCOM Commands • Command Overview Issue a STOP RDF command at the primary system. If the decision has been made to stop RDF without stopping TMF, issue a STOP RDF command at the primary system. RDF stops immediately after all RDF processes save context information in the context file. • Issue a STOP RDF command at the backup system. You should use this method of stopping RDF only if either of the following is true: • • The RDF monitor process is not running on the primary system.
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 only if you are a member of the super-user group and have remote passwords on both the primary and backup systems. 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. STOP UPDATE [ , TIMESTAMP : ] If you use the stop-update-to-time version of this command, the TIMESTAMP parameter suspends updating at the specified time. A stop-update-to-time operation is cancelled by a STOP RDF, NonStop SQL/MP Shared Access DDL, or takeover operation. Note.
Entering RDFCOM Commands Command Overview RDF State Requirement You can issue the STOP UPDATE command only when RDF is running. Usage Guidelines When you disable updating with the STOP UPDATE command, the TMF audit images and commit/abort records from the MAT are still transmitted to the backup system as they are generated by transactions. This functional characteristic ensures that, if an RDF TAKEOVER operation becomes necessary, the backup system database can be made current by the TAKEOVER command.
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 Where Issued Backup system only. Security Restrictions You can issue the TAKEOVER command only if you are the member of the super-user group that initialized RDF.
Entering RDFCOM Commands • Command Overview If the communications lines are down, RDF proceeds as if the monitor process is not running and executes the TAKEOVER command. If RDF is running with updating on, RDFCOM sends a takeover message to each RDF process. If RDF is running with updating off, RDFCOM stops the receiver process and starts the monitor in takeover mode. The monitor then starts a receiver process and all updater processes.
Entering RDFCOM Commands Command Overview If the failed primary system is eventually restored to operation, and you want it to function again as the primary system, do the following: 1. Stop the applications and TMF on the old backup system. 2. Back up the database on the old backup system and restore it to the old primary system. 3. Configure TMF on the old primary system. 4. Initialize RDF on the old primary system. 5. Restart TMF on the old backup system. 6.
Entering RDFCOM Commands Command Overview 4. Having initiated the RDF TAKEOVER operation, you can then use a STATUS RDF command to determine the status of the TAKEOVER operation. If the TAKEOVER operation is still in progress when you enter the STATUS RDF command, the subsystem displays the current state as “TAKEOVER IN PROGRESS.
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 only 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 only 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 (specified by the RDFVOLUME option of a SET RECEIVER command and any ADD IMAGETRAIL commands) are valid and exist on the backup system. 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.
Entering RDFCOM Commands Command Overview HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 8-106
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 continue 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. What Is It? The triple contingency feature is made possible by the ability to replicate to multiple backup systems.
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 RDFCOM turns off the receiver’s takeover completed flag and issues a message telling you that the COPYAUDIT operation has completed successfully and you must initiate another takeover on \C. Issue a TAKEOVER command on \C. If the takeover completes successfully (the receiver logs an RDF message 724 followed by a 735 message containing the same detail as in the 735 message associated with the takeover on \B), the two databases are logically identical.
Triple Contingency Summary 2. When the takeovers have completed successfully, examine the EMS event log on both backup systems for a 735 message to determine which system is missing audit information. 3. On the system with the least amount of audit information, issue a COPYAUDIT command specifying the name of the other backup system and its RDF control subvolume. 4. When the COPYAUDIT command has completed successfully, issue a second TAKEOVER command on that same system. 5.
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.
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 Error Checking for a given volume, the clauses are processed hierarchically, with the INCLUDE clauses processed first and EXCLUDE clauses processed second. Note. When you are adding multiple volumes using INCLUDE and EXCLUDE lists, you must be sure to issue a RESET VOLUME command after each ADD VOLUME command or the previous INCLUDE/EXCLUDE lists will carry forward to the next volume being added.
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 • • • Usage of Master and Auxiliary Audit Trails In addition to the MAT, you have configured RDF to protect one or more auxiliary audit trails. When the primary system fails, an auxiliary extractor is running behind the master extractor. For example, the master receiver has received the commit record associated with a particular transaction, but the auxiliary receiver is missing audit data for that same transaction.
Auxiliary Audit Trails Using Expand Multi-CPU Paths processor 5 on both systems, and all messages between the AUX02 extractor and receiver will go through the path in processor 7 on both systems. For more information about Expand multi-CPU paths, see the Expand Configuration and Management Manual.
Auxiliary Audit Trails Using Expand Multi-CPU Paths HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 12- 6
13 Network Transactions The RDF/IMPX and 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 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 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 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 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. You do that by issuing an RDFCOM TAKEOVER command on each individual backup system. When a takeover occurs within an RDF network, each subsystem’s takeover operation consists of three phases of operation: 1.
Network Transactions Takeover Phase 3 Performance systems, but the tenth primary system went down before its extractor was able to do so. Phase three determines that the particular transaction involved all 10 databases, that one of the backup databases is missing audit data for that transaction, and identifies the transaction as one that must be undone on the other nine systems (it is undone during phase 1 on the tenth system).
Network Transactions Communication Failures During Phase 3 Takeover Processing Communication Failures During Phase 3 Takeover Processing If one RDF subsystem is unable to reach the backup system of another RDF subsytem during phase 3 processing, phase 3 processing stalls until the communication line comes back up. This can lengthen the overall duration of takeover operations on all backup systems.
Network Transactions The Effects of Undoing Network Transactions executed the RDF takeover operation on your backup system, and you have resumed business transactions on your backup system. Assume further that the former primary system has been repaired, it is back online, and you want to switch your business transactions from the active backup database back to the former primary database. To do so, you merely execute a planned RDF switchover from the backup to the newly restored primary.
Network Transactions The Effects of Undoing Network Transactions 6. T12 commit 7. T13 (network transaction started on \B) 8. T13 commit 9. T14 (non-network transaction) 10. T15 (network transaction started on \A) 11. T14 commit 12. T15 commit At approximately the same time system \B executes the following: 1. T10 (network transaction started on \A) 2. T20 (non-network transaction) 3. T12 (network transaction started on \A) 4. T13 (network transaction started on \B) 5. T21 (non-network transaction) 6.
Network Transactions The Effects of Undoing Network Transactions Besides transaction T12, transactions T14 and T15 must also be undone on \X because they followed the commit of T12 on \A and their database changes could have been based on the committed outcome of T12. If T14 and T15 are not also undone, database consistency could be compromised because their effects on the database might have been based upon data that was backed out. Note that T14 is a local transaction, not a network transaction.
Network Transactions Takeover and the RETAINCOUNT Value elsewhere, the purger logs an RDF 823 event message identifying the particular transaction. Note.
Network Transactions Network Validation and Considerations 5. When all other RDF subsystems in the RDF network list 0:00 extractor RTD times, issue the RDFCOM START RDF command on the system where you had stopped RDF. 6. Perform your shared access NonStop SQL/MP DDL operation on your primary system. 7. Follow the normal method for replicating shared access NonStop SQL/MP DDL operations on your backup system.
Network Transactions Non Network Master Subsystem Initialization Non Network Master Subsystem Initialization If you reconfigure the RDF subsystem of a non network master: 1. The network configuration record must point to the network master of the RDF network. 2. You must ensure that the updater responsible for the PNETTXVOLUME is also configured to the same image trail as that listed in the network master’s network configuration record.
Network Transactions RDF Networks and Stop-Update-to-Time Operations RDF Networks and Stop-Update-to-Time Operations Stop-update-to-time operations affect only the backup database of the particular system on which they are initiated.
Network Transactions Sample Network Master Configuration SET RDF UPDATEREXCEPTION OFF ADD RDF SET SET SET ADD MONITOR CPUS 1:2 MONITOR PRIORITY 185 MONITOR PROCESS $MMON MONITOR SET SET SET SET SET ADD EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR EXTRACTOR SET SET SET SET SET SET SET ADD RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER SET SET SET SET SET ADD PURGER PURGER PURGER PURGER PURGER PURGER ATINDEX 0 CPUS 1:2 PRIORITY 185 PROCESS $MEX1 RTDWARNING 60 ATINDEX 0
Network Transactions Sample Non Network Master Configuration SET SET SET ADD RDFNET CPUS 0:2 RDFNET PRIORITY 165 RDFNET PROCESS $MNET RDFNET SET SET SET SET SET SET ADD VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME VOLUME ATINDEX 0 CPUS 1:2 IMAGEVOLUME $DATA06 PRIORITY 185 PROCESS $RU43 UPDATEVOLUME $DATA07 $DATA07 RESET VOLUME 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
Network Transactions Sample Non Network Master Configuration SET SET SET SET SET SET SET ADD RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER RECEIVER SET SET SET SET SET ADD PURGER PURGER PURGER PURGER PURGER PURGER ATINDEX 0 CPUS 3:2 EXTENTS (100,100) PRIORITY 185 RDFVOLUME $DATA11 SLOWMODE OFF PROCESS $MR51 CPUS 3:2 PRIORITY 185 PROCESS $RP50 RETAINCOUNT 5 PURGETIME 60 SET IMAGETRAIL ATINDEX 0 ADD IMAGETRAIL $DATA06 SET SET SET ADD NETWORK PRIMARYSYSTEM \RDF04 NETWORK BACKUPSYSTEM
Network Transactions RDFCOM STATUS Display RDFCOM STATUS Display The following illustrates the RDFCOM STATUS display for a network master (note that it includes the RDFNET process). RDFCOM - T0346A06 - 14MAR04 - NET (C)1988 Tandem (C)2004 Hewlett Packard Development Company, L.P. Status of \RDF04 -> \RDF06 RDF 2004/04/14 16:13:37.003 Control Subvol: $SYSTEM.
Network Transactions RDFCOM STATUS Display HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 13-20
14 Process-Lockstep Operation The RDF/IMPX and 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. A lockstep operation consists of the following steps. 1. A process starts a business transaction and does database updates. 2.
Process-Lockstep Operation Starting a Lockstep Operation Starting a Lockstep Operation Transactions protected by a lockstep operation are begun, performed, and terminated just as any other transaction: call BeginTransaction, do the necessary database updates, and then call EndTransaction. What defines a lockstep operation is the invocation of the new DoLockstep procedure. You issue the DoLockstep call immediately after the associated EndTransaction call.
Process-Lockstep Operation DoLockStep Execution After recompiling your program, you must then decide whether you want to bind the object explicitly into your program or treat the object as a user library. Typically you should explicitly bind the object into your program. The object file (LSLIBTO) is very small, and there are no benefits to treating it as a user library. To bind LSLIBTO into your program, issue the following statement: Select Search <$vol.subvol>.LSLIBTO where <$vol.
Process-Lockstep Operation The Lockstep Transaction LockStepDisabled (value is 31429) Only returned when you have disabled lockstep processing. When this condition code is returned to your application, what your application does next is up to you.
Process-Lockstep Operation Multiple Concurrent Lockstep Operations The RDF lockstep protocol supports virtual disks, so you can store your database on virtual disks managed by the Storage Management Facility (SMF). The RDF LOCKSTEPVOL, however, must be a physical disk, and it must be configured to the Master Audit Trail (MAT).
Process-Lockstep Operation NAME NAME This attribute must be $ZLSGW. If you specify anything else, the lockstep gateway stops and you cannot perform lockstep operations. Note that this means you can only have a single lockstep gateway process running on your primary system. PROGRAM This attribute specifies where the RDF gateway object code resides. Typically, that location is the same volume and subvolume where all of the other RDF software resides.
Process-Lockstep Operation Reenabling Lockstep want to disable lockstep processing to allow your applications to resume their work without lockstep operations. When lockstep is disabled, remember that your original transaction has already committed on the primary system.
Process-Lockstep Operation Lockstep and Network Transactions Lockstep and Network Transactions You cannot use lockstep to protect data associated with network transactions because the lockstep protocol only pertains to operations on a single system. If lockstep is used with network transactions, consistency between lockstep operations and the distributed application database files cannot be guaranteed after an RDF takeover. Lockstep Operation Event Messages 1 I/O completed on an unknown file number.
Process-Lockstep Operation Lockstep Operation Event Messages 4 The lockstep gateway has received error errnum when attempting to communicate with the RDF extractor procname. errnum is a file-system error number. procname is the name of an extractor process. Cause. The RDF extractor is no longer responding, and it may be stopped. Effect. The lockstep gateway stops. Recovery. Determine why the RDF subsystem stopped, correct the problem, and then restart the subsystem.
Process-Lockstep Operation Lockstep Operation Event Messages 6 Create error errnum on the RDF lockstep file filename. errnum is a file-system error number. filename is the name of a lockstep file. Cause. When the gateway attempted to create the specified lockstep file, it received the specified error. Effect. The lockstep gateway stops. Recovery. Correct the error condition and restart the lockstep gateway. 7 Open error errnum on filename. errnum is a file-system error number.
Process-Lockstep Operation Lockstep Operation Event Messages 8 Error errnum received when attempting to obtain info on file 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 call FILE_GETINFOLIST_ on the specified file. Effect. The lockstep gateway stops. Recovery. Correct the error condition and restart the lockstep gateway. 9 Error errnum returned when attempting to update file filename.
Process-Lockstep Operation Lockstep Operation Event Messages 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. Either the file was not created by the lockstep process, or the file code was incorrectly altered. Purge the file and restart the lockstep gateway. 11 Lockstep file filename is not audited. filename is the name of a lockstep file. Cause.
Process-Lockstep Operation Lockstep Operation Event Messages 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. If the problem persists, contact the Global Customer Support Center (GCSC) or your service provider. 14 BEGINTRANSACTION error errnum when attempting a lockstep transaction.
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/IMP, IMPX, and ZLT System Management Manual—524388-002 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 Creating NonStop SQL/MX Primary and Backup Databases from Scratch 2. Create the catalog on the backup system. The catalog name must be different from that of the primary catalog. For example, if issued on the backup system the command CREATE CATALOG BCAT LOCATION $DATA01; creates a catalog named BCAT on volume $DATA01 on the backup system. 3. If you want each catalog to be seen from both systems, register your primary and backup catalogs.
NonStop SQL/MX and RDF Creating NonStop SQL/MX Primary and Backup Databases from Scratch If you omit the LOCATION clause, then, after creating the schema, you must use the following query to obtain the subvolume of the schema (where you fill in the correct node-name, schema-name, and catalog-name): SELECT S.schema_subvolume FROM NONSTOP_SQLMX_node-name.system_schema.schemata S, NONSTOP_SQLMX_node-name.system_schema.catsys C WHERE S.schema_name = 'schema-name' AND C.cat_name = 'catalog-name' AND S.
NonStop SQL/MX and RDF Creating NonStop SQL/MX Primary and Backup Databases from Scratch For example, the following command creates a table called TAB1 in schema PCAT.SCH, with three partitions, located on volumes $DATA02, $DATA03, $DATA04, respectively. CREATE TABLE PCAT.SCH.
NonStop SQL/MX and RDF Creating a NonStop SQL/MX Backup Database From an Existing Primary Database 7. Create each object on the backup system. The ANSI name of the object must be constructed as follows: catalog name: use the name of the backup catalog you created in Step 2. schema name: use the name you used in Steps 4 and 5. table or index name: must match on the primary and backup systems. The following command creates a table called TAB1 in the schema BCAT.
NonStop SQL/MX and RDF Creating a NonStop SQL/MX Backup Database From an Existing Primary Database For example, if issued on the backup system, the command CREATE CATALOG BCAT LOCATION $DATA01; creates a catalog named BCAT on volume $DATA01 on the backup system. For the rest of this procedure assume that the name of the primary system is \PNODE and the name of the backup system is \BNODE. 2.
NonStop SQL/MX and RDF Creating a NonStop SQL/MX Backup Database From an Existing Primary Database input list must be a Guardian EDIT file consisting of one fully-qualified ANSI SQL table name per line, such as: CAT.SCH.T1 CAT.SCH.T123 CAT.SCH.
NonStop SQL/MX and RDF Online Database Synchronization With NonStop SQL/MX Objects Online Database Synchronization With NonStop SQL/MX Objects The principles of protocol for online database synchronization with NonStop SQL/MX objects are the same as for Enscribe and NonStop SQL/MP objects. That is, you follow the guidelines for the RDF online database-synchronization protocol. The only difference is how the fuzzy copy is obtained.
NonStop SQL/MX and RDF Creating the Fuzzy Copy on the Primary System For example, suppose you have a primary table that has two partitions, for which you want make a fuzzy copy, and the fully qualified Guardian names are: $DATA01.ZSDABCDE.HWEFGH00 $DATA02.ZSDABCDE.HWEFHJ00 When you create the temporary table, you might list the following Guardian names in the LOCATION clause: $DATAXX.ZSDABCDE.HWEFGH00 $DATAYY.ZSDABCDE.HWEFHJ00 4. Populate the temporary tables.
NonStop SQL/MX and RDF Creating the Fuzzy Copy on the Backup System 9. Use RESTORE to place the temporary objects on the backup system, but specifying the backup catalog as the target. See Step 5 of the procedure Creating a NonStop SQL/MX Backup Database From an Existing Primary Database, above, for details. Note the following: • • The subvolume.filename of the primary and temporary objects are identical. The schema and object names of the primary and temporary objects are identical.
NonStop SQL/MX and RDF Offline Synchronization for a Single Partition 7. Populate the backup objects by running an INSERT statement on whichever system you prefer. INSERT INTO backup-table SELECT * FROM primary-table; where backup-table and primary-table are the 3-part ANSI names of the two tables. The backup database is now ready for RDF replication. Offline Synchronization for a Single Partition You must first determine the key ranges for each of your partitions.
NonStop SQL/MX and RDF Backup Partition Does Not Already Exist 3. Create a temporary table in your temporary schema, including all partitions. Note that the partition ranges must be identical to those of your primary table. Follow the guidelines outlined in Creating a NonStop SQL/MX Backup Database From an Existing Primary Database, above, except that you must create the temporary table on the primary system and on different volumes from those used for your primary objects. 4.
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.
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). That is, one mirror of an audit-trail volume remains local to the primary system, but the other mirror is located at a remote site.
Zero Lost Transactions (ZLT) How It Works Figure 16-1 shows the configuration where a single system serves as both the standby and backup systems, and the remote mirror is located at the standby/backup site. 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-3 shows the configuration where individual standby and backup systems are located at separate sites. Figure 16-1.
Zero Lost Transactions (ZLT) How It Works Figure 16-3.
Zero Lost Transactions (ZLT) Hardware Setup If you lose the primary system to a disaster and that disaster does not affect the standby and backup systems, no committed transactions are lost because RDF on the backup system can fetch all missing audit records from the remote mirrors.
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) Error Conditions Error Conditions If the standby system is different from the backup system and the monitor cannot reach the standby system to start the extractor(s), the takeover operation aborts. If that happens, you must bring the standby system up (and make sure it is available to the backup system by way of the Expand network) and then reissue the TAKEOVER command.
Zero Lost Transactions (ZLT) Recovering the Primary System After an RDF ZLT Takeover Recovering the Primary System After an RDF ZLT Takeover When the primary system is once again available for use, perform the following steps to recover it after having performed an RDF ZLT takeover: 1. Disconnect all local audit-trail mirrors from the primary system, and then connect all remote audit-trail mirrors to the primary system. 2. Start the primary system. 3. Start TMF on the primary system.
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 } } } } } } } } } ALTER The ALTER command changes the setting of the specified parameter in the RDF configuration file to the supplied value. Where Issued: Primary system only.
RDF Command Summary DELETE The DELETE command deletes the entire configuration record for the specified secondary image trail or updater process from the RDF configuration file. Where Issued: Primary system only. Security: Super-user group member. DELETE {IMAGETRAIL $volume} [ATINDEX audittrail-index-number] {[VOLUME] $volume } {$volume } EXIT The EXIT command ends your current RDFCOM session. Where Issued: Primary or backup system. Security: Any user.
RDF Command Summary Security: Any user. HELP [ABBREVIATIONS [ALL [command [RDF-msg-number ] ] ] ] HISTORY The HISTORY command displays the ten most recently issued RDFCOM commands (including the HISTORY command itself). Where Issued: Primary or backup system. Security: Any user. HISTORY 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 Security: Super-user group member. INITIALIZE RDF [ , [ , [ , [ , , BACKUPSYSTEM backup-system-name SUFFIX suffix-character TIMESTAMP : INITTIME : SYNCHDBTIME : ] ] ] ][!] OBEY The OBEY command executes a series of commands entered in an OBEY command file. Where Issued: Primary or backup system. Security: Any user. OBEY [\system.][$volume.][subvolume.
RDF Command Summary RESET The RESET command resets all configuration parameters for the specified process to their default values within the RDF configuration memory table. The corresponding parameters within the configuration file do not change, however, unless you issue an ADD command. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary 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. Where Issued: Primary system only. Security: Super-user group member.
RDF Command Summary 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. 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. SET RDF global-option where global-option is: {LOGFILE [[volume.]subvol.
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 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. Where Issued: Primary or backup system. Security: Any user.
RDF Command Summary STATUS The STATUS command displays current configuration information and operational statistics for the RDF environment. Where Issued: Primary or backup system. Security: Any user. STATUS {MONITOR {RDF {EXTRACTOR {RECEIVER {PURGER {PROCESS procname {VOLUME {RTDWARNING {RDFNET } [, PERIOD seconds[, COUNT repeat]] } } } } } } } } STOP RDF The STOP RDF command shuts down the RDF subsystem.
RDF Command Summary STOP UPDATE The STOP UPDATE command suspends updating of the backup database and stops all updater processes. Where Issued: Primary system only. Security: Super-user group member, and remote passwords on both the primary and backup systems. STOP UPDATE [, TIMESTAMP timestamp ] TAKEOVER The TAKEOVER command causes the backup database to become the database of record. Where Issued: Backup 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 Values MIN MAX RDF BACKUPSYSTEM BACKUPSYSTEM value used on INITIALIZE RDF n.a. n.a. RDF LOGDEVICE $0 n.a. n.a. RDF LOGFILE $0 n.a. n.a. RDF NETWORK off 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 Values MIN MAX 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 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. Cause.
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. Informational message only; no corrective action is needed unless the purger is reporting problems. 704 Updaters stopped before stop-update-to-time has completed. Cause.
Messages RDF Messages operation indefinitely, and will respond to RDFCOM commands while the retries are taking place. Note. If the extractor detects that the OPEN operation failed because the audit trail had been purged, it logs RDF Error 839 (Audit trail file is missing) rather than Error 705, prompting you to restore the audit trail file. • The receiver retries OPEN calls for the image files if file-system error 11 (file missing), 12 (file in use), or 59 (file is bad) occurs.
Messages RDF Messages was then stopped before the extractor was started. If the extractor detects that TMF is not started, the extractor aborts itself, and the monitor aborts the receiver and itself. Recovery. Start TMF before trying to start RDF. 708 Internal error detected Cause. An internal error has been detected in RDFCOM. Effect. RDFCOM aborts. Recovery. This is an internal error. Contact your service provider.
Messages RDF Messages Cause. The updater failed to obtain process information about itself. This is a fatal error. Effect. The updater process abends. Recovery. This is an internal error. Contact your service provider. 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.
Messages RDF Messages Effect. The backup process is not started. The primary continues to run, but will be vulnerable to a CPU failure. The primary will try to create its backup repeatedly until it succeeds. Recovery. Consult the description of the NEWPROCESS procedure errors 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.
Messages RDF Messages Effect. The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created. Recovery. Scan the EMS event log to determine why the process abended. An INSPECT SAVEABEND file should have been created in the volume and subvolume where you placed the RDF software. You should save that file for problem resolution by your service provider. 717 Primary processor down Cause. The primary CPU of a process pair has stopped. Effect.
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. Informational message only; no corrective action is needed.
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 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. The purger has determined that the updater process indicated in this message did not complete its RDF takeover processing. That updater may have stopped prematurely because of a double CPU failure or a STOP command entered manually from TACL. Effect.
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 failed. Effect. The process continues to run at its current priority. Recovery. Informational message only; no corrective action is needed. Reissue the ALTER command. 730 Process priority altered priority priority is the priority requested for the process. Cause.
Messages RDF Messages 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 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. Whenever possible, this message includes the offending process name or process id as well as the program file name.
Messages RDF Messages 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 file. Before an updater can apply audit records to a file, it must obtain information about the file. The probable reason why information could not be obtained is that the file has not been created yet. Effect.
Messages RDF Messages rba is the relative byte address of the synchronization point. Cause. This message indicates that te receiver has sent the extractor a starting position in the TMF audit trail, and the extractor has thereby become synchronized with the receiver. Effect. The extractor is synchronized with the receiver. Recovery. Informational message only; no corrective action is needed. 739 File creation failed.
Messages RDF Messages Recovery. For partitioned files and files with alternate keys, if any partition or alternate key file is on a volume protected by RDF, then all partitions and alternate key files must be on volumes protected by RDF. Either the file must be redefined on the primary node, or the other volume must be made protected by RDF. In the latter case, the backup file must then be resynchronized with the primary file. 741 RDF extractor message out of order Cause.
Messages RDF Messages 744 FILEINFO obtained on file filename filename is the name of the file that caused the error. Cause. The updater was previously delayed in obtaining information about the specified file (see RDF error 736). The information has now been obtained. Effect. The updater continues processing. Recovery. Informational message only; no corrective action is needed. 745 Audit record conversion error error error is the error number. Cause.
Messages RDF Messages Cause. Either TMF has not been started on the remote node, or the volume associated with this updater on the remote node has not been added as a datavol in the TMF configuration. TMF must be started on the remote node, and the volume associated with this updater on the remote node must be added as a datavol to this remote TMF configuration. Effect. The updater will not start. Recovery.
Messages RDF Messages 751 CHECKOPEN Error error On filename error is the file-system error number that identifies the specific error. filename is the name of the file associated with the error. Cause. A call to the CHECKOPEN procedure failed, and the backup process of a process pair is still running. The message includes the file-system error number encountered when the primary process tried to communicate with the backup process and the name of the file associated with the error. Effect.
Messages RDF Messages 753 Audit trail file stutter. File filename RBN rbn RBA rba filename is the name of the audit trail file that contained the error. 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 a block of audit data that is repeated in the TMF audit trail. Effect. The block is ignored and processing continues.
Messages RDF Messages 756 Format-2 audit filtered for filename filename is the name of a format 2 database file to which the encountered audit record applies. Cause. The extractor encountered an audit record associated with a format 2 file specified in the event and the backup system is not format-2 aware. Effect. The extractor skips the audit record and does not send it to the receiver. Recovery.
Messages RDF Messages Cause. An updater has encountered an audit record associated with an Enscribe CREATE operation, an increase of MAXEXTENTS for an Enscribe file, or a PURGEDATA operation for an Enscribe file, and the file on the primary system has secondary partitions that are located on different systems in the network. Effect. The updater skips this record. Note that if the record is associated with an Enscribe CREATE operation, no partitions of the file are created on the backup system.
Messages RDF Messages Effect. You cannot start the RDF subsystem. Recovery. Purge all existing context and configuration files on the primary and backup systems. Then initialize the RDF subsystem. 763 Process incompatible with local system Cause. The process reporting the error has determined that it has been installed with the wrong operating system. Effect. The process abends. Recovery. Install the version of the RDF product that is compatible with the installed release of the operating system.
Messages RDF Messages Effect. The extractor continues with the second part of phase one. Recovery. Informational message only; no corrective action is needed. 767 Phase one part 2 database synchronization complete Cause. The second part of phase one of an online database synchronization operation is complete. Effect. The extractor continues with the third part of phase one. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages Effect. The process starts its task of performing synchronized transactions on each of the primary nodes in the RDF network of RDF primary systems. Recovery. Informational message only; no corrective action is needed. 771 Remote RDF receiver started Cause. The receiver has successfully completed its initialization. Effect. The receiver is prepared to receive data from the extractor. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages Effect. The extractor will begin reading TMF audit data and transmitting it to the receiver. Recovery. Informational message only; no corrective action is needed. 775 Restart position adjusted for database synchronization Cause. The extractor has encountered a restart condition during an online database synchronization operation, and the current audit trail restart position sent by the receiver may lead to loss of data. Effect.
Messages RDF Messages Effect. Normal RDF shutdown processing continues. If this message is issued as the result of a STOP UPDATE command, RDF will continue processing with updating disabled. Recovery. Informational message only; no corrective action is needed. 779 Local RDF extractor shutdown complete Cause. The extractor has terminated normal processing as the result of a STOP TMF or STOP RDF command. Effect. Normal RDF shutdown processing continues. Recovery.
Messages RDF Messages Effect. The extractor abends. Recovery. You must initialize RDF to a new database synchronization timestamp and then restart the entire operation from the beginning. 782 Phase two database synchronization complete Cause. Phase two of a database synchronization operation involving the process that generated this message is complete. Effect.
Messages RDF Messages 785 Redo pass ending on reaching timestamp timestamp timestamp is the timestamp specified previously by an operator in an RDFCOM STOP UPDATE, TIMESTAMP timestamp command. Cause. A STOP UPDATE, TIMESTAMP timestamp command has been issued and the updater has completed its redo pass. Effect. The updater is ready to commence its undo pass. Recovery. Informational message only; no corrective action is needed. 786 STOP SYNCH message received Cause.
Messages RDF Messages Cause. The receiver or an updater has encountered the indicated error while attempting to position within an image file. Effect. The process abends. Recovery. Correct the problem that caused the error and then restart RDF. 788 ALLOCATESEGMENT failure. Returned status status status is a status code reflecting information about the error. Cause. An RDF process received an error from the ALLOCATESEGMENT system procedure. Effect.
Messages RDF Messages 790 Backup process created in processor cpu cpu is the CPU in which the backup process was created. Cause. The backup process of a process pair was created in the specified processor. Effect. The primary process will now run in fault-tolerant mode. Recovery. Informational message only; no corrective action is needed. 796 Image file creation error error on filename error is the file-system error number that identifies the specific error.
Messages RDF Messages Effect. This is only a warning. The purger will retry the purge operation. Recovery. Correct the underlying condition, and the purger will purge the image file in the next purge pass. Note. Under some circumstances, after the configured backup receiver process re-creates its primary and switches to that primary, it continues to hold an image file open.
Messages RDF Messages rba is the relative byte address where the error occurred. Cause. An RDF process encountered an error while attempting to read an image file. Effect. This is a catastrophic error; the process abends, and RDF stops. The message includes the error number returned by the READ system procedure, followed by the name of the file that contained the error. Recovery. Restart RDF. If the problem persists, you might need to reinitialize RDF.
Messages RDF Messages 802 Image trail file has bad RDF header record filename filename is the name of the image file associated with the error. Cause. An RDF process has encountered a bad header in an image file. Effect. A bad header indicates that the image file has been corrupted. This is a catastrophic error; the process abends, and RDF stops. Recovery. Restart RDF. If the problem persists, reinitialize RDF and report the error to your service provider.
Messages RDF Messages Effect. The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction. Recovery. Determine the cause of the error and then take appropriate corrective action. 805 WRITEUPDATELOCK error error on filename error is the file-system error number that identifies the specific error. Cause. The RDFNET process has encountered the specified error on the specified file. Effect.
Messages RDF Messages Effect. RDF stops updating the backup database. Recovery. Informational message only; no corrective action is needed. 809 Shutting down in response to STOP RDF Cause. The operator issued a STOP RDF command. Effect. The RDF process stops normally. Recovery. Informational message only; no corrective action is needed. 810 Shutting down in response to STOP TMF, timestamp timestamp timestamp is the time of the shutdown. Cause.
Messages RDF Messages Cause. The updater encountered a file-system error while attempting to communicate with the receiver or purger. The file-system error number and the name of the receiver or purger are included in the message. Effect. This is a catastrophic error; the updater abends, and RDF stops. Recovery. Determine the cause of the error. If the receiver or purger did not abend, correct the condition, then restart RDF. 813 Concurrent file opens exceed capacity Cause.
Messages RDF Messages 815 Primary process takeover in processor cpu# cpu# is the number of the processor in which the primary process is now running. Cause. A new primary process has been created by the backup process, and the backup process has switched control to that primary process. Effect. The primary process of the process pair (in the designated cpu) has taken over. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages 818 SQL DDL operation aborting database synchronization Cause. While working on an online database synchronization operation, the extractor encountered an RDF-Stop-Updaters audit record. This indicates that an SQL DDL operation with SHARED ACCESS altered the database on the primary system, Effect. The SQL DDL operation has altered the primary database from what was being duplicated to the backup system, thereby invalidating the online synchronization operation. The extractor abends.
Messages RDF Messages 821 RDF updater stopped unexpectedly, updater updater is the name of the updater process that stopped. Cause. An updater has stopped unexpectedly. Effect. This message is issued by the RDF monitor. The monitor sends an abort request to all remaining RDF processes to stop RDF. Recovery. A subsequent warm start of RDF will probably be successful, but the success of the restart depends on the nature of the failure that caused the original updater process to stop.
Messages RDF Messages 824 Missing RDF extractor config record Cause. The RDF monitor was unable to find an extractor configuration record when performing a START RDF command. Effect. The START operation fails and RDF shuts down. Recovery. Use the SET and ADD commands to create an extractor configuration record and then retry the START RDF command. 825 Missing RDF receiver config record Cause. The RDF monitor was unable to find a receiver configuration record when executing a START RDF command. Effect.
Messages RDF Messages 828 Killing backup process ... Cause. The primary process of a process pair has detected a problem in communicating with the backup process. An earlier message will have indicated the communications problem. Effect. Because of the severity of the problem, the primary process attempts to stop the backup process. If the backup process stops, the primary process then attempts to create a new backup process. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages 831 RDF fatal error information text text is the stack trace. Cause. An RDF process is terminating abnormally. Effect. The equivalent of an INSPECT TRACE is written and the process abends. Recovery. This message gives your service provider information about the state of a process that is terminating abnormally. You might be able to correct the underlying problem and restart RDF. Otherwise you must reinitialize RDF.
Messages RDF Messages message could also mean that the audit trail file was corrupted by some program other than TMF, or that an irrecoverable system error has occurred. In any event, you will have to reinitialize the TMF and RDF subsystems. Save the audit trail, and report this error to your service provider. 834 Purge pass terminated prematurely. Reason: reason reason is a reason code. Cause.
Messages RDF Messages 836 volume is not enabled for transaction processing volume is the name of the affected volume. Cause. TMF reports that the specified data volume is not enabled. This may be the result of an earlier failure and the volume is still recovering, or the user has disabled the volume in TMFCOM. Effect. The updater is unable to apply updates to this volume until the volume is enabled. The updater retries the operation every minute until the volume is enabled. Recovery.
Messages RDF Messages Effect. This message is issued by the RDF monitor. The monitor sends an abort message to all remaining RDF processes to stop RDF. Recovery. Determine the reason why the RDFNET process stopped, correct the problem, and then restart RDF. If the problem persists, contact your service provider. 839 Error - Audit trail file is missing. File filename filename is the name of the audit trail file that could not be found. Cause.
Messages RDF Messages 841 Error - Unable to complete STOP UPDATE. Error error error is a file-system error number. Cause. The monitor was unable to send shutdown messages to an updater because of the indicated file-system error. Effect. The monitor terminates the attempt to send STOP UPDATE messages to any other updaters. It then sends an ABORT RDF message to all the other RDF processes and waits for them to stop. Recovery.
Messages RDF Messages 844 Phase one database synchronization complete Cause. The updater that generated this message has completed phase one of the online synchronization operation for its volume on the backup system. Effect. The updater starts phase two of the online synchronization operation. Recovery. Informational message only; no corrective action is needed. 845 Initialization synchronization completed Cause.
Messages RDF Messages 848 RDF extractor waiting for network reply Cause. The extractor has sent the maximum number of messages to the receiver and has not received any replies for at least five minutes. Effect. The extractor cannot proceed any further. Recovery. This is not an RDF problem. You should investigate your Expand network and take corrective action. If necessary, you can issue a STOP RDF command on both the primary and backup systems to stop the RDF processes in an orderly fashion.
Messages RDF Messages Recovery. Recovery is not possible. Contact your service provider. 853 Purger TST filled Cause. In determining what transactions need to be undone, the internal table of transactions has become filled. Effect. RDF aborts. Recovery. Contact your service provider for assistance with recovering from this situation. 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.
Messages RDF Messages Effect. The purger process purges any image trail files that are no longer required by RDF. Recovery. Informational message only; no corrective action is needed. 857 Error error on ENDTRANSACTION encountered error is an error number. Cause. The named RDF process has encountered an error when attempting to ends its current transaction. Effect. The process aborts the current transaction, restarts and continues processing. Recovery.
Messages RDF Messages 860 Fatal error error on BEGINTRANSACTION encountered error is an error number. Cause. The named RDF process has encountered the specified error while attempting to begin a new transaction. Effect. The process abends and RDF aborts. Recovery. Consult the description of BEGINTRANSACTION errors in the HP NonStop TMF Application Programmer’s Guide and take appropriate corrective action.
Messages RDF Messages rtd is an RTD value. threshold# is an RTDWARNING warning threshold value. Cause. The specified updater has fallen behind the configured updater RTDWARNING threshold. Effect. The updater continues normal processing. Recovery. Informational message only; no corrective action is needed. You should, however, try to determine why the updater has fallen behind and take corrective action if necessary. 863 Missing RDFNET CONFIG record. Cause.
Messages RDF Messages Effect. The reporting process abends and RDF aborts. Recovery. Restart RDF. If the problem persists, contact your service provider. 866 RDF purger stopped unexpectedly. Cause. The purger process has terminated unexpectedly. Effect. RDF aborts. Recovery. Determine why the purger stopped, and then restart RDF. If the problem persists, contact your service provider. 867 Remote RDF purger shutdown complete Cause. The purger process has stopped. Effect. RDF continues to shut down.
Messages RDF Messages Effect. The updater commences an additional undo pass. Recovery. Informational message only; no corrective action is needed. 870 No image files present on image trail Cause. The purger could not find any image files in the image trail subvolume. Effect. The purger abends, causing RDF to shut down. Recovery. This is an internal error. Report this to your service provider. 872 Warning; Lockstep operation is denied. Cause.
Messages RDF Messages Cause. The specified error occurred while attempting to allocate an extended segment. Effect. The affected process abends and RDF aborts. Recovery. Try to determine why the segment could not be allocated. Take appropriate corrective action and restart RDF. 875 Incompatible file format filename format fileformat, audit format auditformat filename is the file name. fileformat specifies the format of the file. auditformat specifies the format of the audit trail. Cause.
Messages RDF Messages 877 First local network transaction to be undone: %num num num num %num num num num identifies a network transaction. Cause. This is the first transaction that requires network undo with respect to local processing. Please note, however, that some transactions preceding it might also require undo for business consistency across all backup nodes. The transid is listed in internal format. Effect. None. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages 880 Takeover issued during a stop-update-to-time operation. Cause. A takeover command was issued while a stop-update-to-time operation was in progress. Effect. The process abends and RDF aborts. Recovery. You must reissue the Takeover command. That ensures the stop-updateto-time operation is aborted and the RDF subsystem is prepared to execute the takeover operation. 881 Aborting current RDF process transaction. Cause.
Messages RDF Messages 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. 884 The RDFNET process is restarting. Cause. The RDFNET process encountered a condition that caused it to restart. Effect. The process restarts and resumes normal processing. Recovery. Examine preceding events for this process to try to determine why the process is restarting.
Messages RDF Messages 888 MAT position for File Recovery: SNO RBA Cause. A successful takeover has completed. If you need to bring your primary database back into synchronization with your backup database, use TMF File Recovery on your primary system with the specified MAT position. Effect. None. Recovery. Informational message only; no corrective action is needed. Consult TMF documentation for information about TMF File Recovery to an audit-trail position (TOMATPOSITION).
Messages RDF Messages 891 First network transaction to be undone: %number number is the transaction number. Cause. This is the first transaction that requires network undo with respect to business consistency across all backup nodes. All transactions that committed after this transaction are undone on this node except those transactions that can be safely kept because they actually committed before this transaction on one or more different primary nodes in the RDF network.
Messages RDF Messages 894 SQL NSA operation detected at SNO sno RBA rba sno is the sequence number. rba is the relative byte address. Cause. The auxiliary receiver has detected information about an SQL Shared Access DDL operation associated with the specified SNO and RBA in the master audit trail on your primary system. Effect. The auxiliary receiver coordinates stopping its updsaters at the correct location. Recovery. Informational message only; no corrective action is needed.
Messages RDF Messages 897 Commencing additional file undo pass. Cause. The list of transactions whose audit must be undone due to file incomplete records exceeds the total number of transactions that can be undone in a single undo pass. Effect. The updater commences an additional undo pass. Recovery. Informational message only; no corrective action is needed. 898 SQL NSA operation detected in network undo operation Cause.
Messages RDF Messages Recovery. Informational message only; no corrective action is needed. 901 Extractor is started for ZLT processing Cause. The extractor is started on the ZLT standby system for ZLT processing. 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. Informational message only; no corrective action is needed.
Messages RDF Messages Effect. The master receiver continues to wait until all auxiliary receivers have caught up. The auxiliary receiver may continue to report this event as it continues to catch up. 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.
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 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/IMP, IMPX, and ZLT System Management Manual—524388-002 C-142
D Operational Limits Table D-1.
Operational Limits HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 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 A Abbreviations 8-25, A-3 ADD command 8-10, A-2 ADD EXTRACTOR command 3-24 ADD MONITOR command 3-23 ADD RECEIVER command 3-25, 3-27 ALTER command 8-14, A-2 ALTER command, FUP 3-8 Altering TMF configuration 3-13 ASAP, Using with RDF 1-34, E-1 Asterisk wildcard character 9-14 AT command 9-3, 9-17, A-14 ATINDEX parameter 8-19, 8-30, 8-53, 8-56, 8-71 Audit compression 3-2 Audit dumping, STATUS RDF command 4-22 Audit trail file purging 2-6 AUDITCOMPRESS file attribute 3-2 Auditing RDF requirements 2-5 turn
Index C Commands, RDFCOM (continued) DELETE 8-19, A-3 examples A-1 EXIT 8-21, A-3 FC 8-22, A-3 HELP 8-25, A-3 HISTORY 8-29, A-4 INFO 8-30, A-4 INITIALIZE RDF 8-38, A-4 OBEY 8-45, A-5 OPEN 8-47, A-5 OUT 8-49, A-5 RESET 8-51, A-6 SET EXTRACTOR 8-53, 8-56, A-6, A-7, A-8, A-9 SET MONITOR 8-57, 8-59, 8-69, A-7 SET RDF 8-64, A-9 SET RECEIVER 8-61, 8-71, A-10 SET VOLUME 8-75, A-10 SHOW 8-79, A-11 START RDF 8-84, A-11 START UPDATE 8-86, A-11 STATUS RDF 4-18, 8-87, A-12 STOP RDF 8-94, A-12 STOP SYNCH 8-96, A-12 ST
Index D Create operation error recovery 5-4 file system errors 5-4 RDF errors 5-4 D Database operations, replicating 2-9 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 modifications 6-8 NonStop SQL/MP backing up altered structures 6-4 catalog changes 6-5 DDL operations 6-5 partition key changes 6-8 synchronization 6-4 table purges 6-8 states 6-1 synchronizing entire database 6-9, 6-10 individual tables or
Index F Error recovery (continued) RDF error 705, open operation 5-2 RDF error 739, create operation 5-4 Event log scanning messages in EMS 1-11, 4-23 Exception files description B-8 examining B-7 records 1-10 EXCLUDE clauses 11-2 EXIT command 8-21, 9-6, A-3, A-14 Expand estimating required resources 2-3 multi-CPU paths (superpaths) 12-4 EXPAND line failure 5-6 Extractor process 1-15 auxiliary 12-1 configuration 3-24, 8-53, 8-56, A-6, A-7, A-8, A-9 failure 5-7 object code file 3-9, 3-10 parameters ADD EXT
Index G Files backup system 3-9 partitioned, synchronizing 3-8 preparing for RDF protection 3-2 File, log 9-1 File-ids 8-7 File-label modifications 6-8 G Gateway process, RDF 14-5 Guardian 90 see Operating system Initialization, online 3-16 INITIALIZE RDF command 3-14, 8-38, A-4 Initializing RDF 3-14 TMF 3-13 INITTIME parameter 3-16, 8-39 Installation 2-5 Installing the RDF subsystem 3-9 K Keywords 4-7 L H Hardware requirements 2-1 Help RDFCOM online 4-10 RDFSCAN online 4-15 HELP command 8-25, 9-9, A-
Index N Master audit trail, calculating amount of data 2-3 Master image trail 1-20 MATCH command 9-14, A-15 Match pattern for log messages 9-10, 9-14, 9-17, A-15 Messages displaying HELP text for 4-10 file system errors C-2 in log file 4-23 logged in log file 1-10 RDF C-2 RDFCOM C-69 RDFSCAN C-139 scanning in EMS event log 1-11, 4-23 scanning in log file 1-11 mixed-release 2-5 Mixed-release installation 2-5 Modify operation error recovery 5-2 file system errors 5-2 RDF errors 5-2 Monitor process 1-15 conf
Index O NonStop SQL/MP DDL operations 5-27 NonStop SQL/MX and RDF 15-1 Non-shared access DDL operations 5-27 O OBEY command 8-45, A-5 OBEY command file B-4 OBEY command files 4-6 backup system 3-3, 3-9 synchronizing databases with 3-5 OBEYFORM option 8-30 OBEYFORM option of INFO command 3-30 OBEYVOL command 8-45 ODBC catalog changes 6-5 Offline synchronization for a single partition 15-11 Online database synchronization 7-1 Online database synchronization, phases of 7-21 Online Dumps on Backup System 2-7
Index Q Primary system backing up files 2-7 configuration 2-1 preparing for RDF installation 3-1 processes 1-14 RDF requirements 2-1 PRIMARYSWAP parameter 8-64 PRIMARYSYSTEM network attribute 13-4 PRIORITY parameter 8-53, 8-56, 8-57, 8-59, 8-69, 8-75, A-7, A-8 extractor process 3-24 monitor process 3-23 receiver process 3-25, 3-27 Process file names A-16 Process identifiers A-16 PROCESS parameter 8-53, 8-56, 8-57, 8-59, 8-69, 8-75, A-7, A-8 extractor process 3-24 receiver process 3-25, 3-27 Processes, RDF
Index R RDF subsystem parameters (continued) PRIORITY 8-53, 8-56, 8-57, 8-59, 8-61, 8-69, 8-71, 8-75, A-7, A-8 PROCESS 8-53, 8-56, 8-57, 8-59, 8-61, 8-69, 8-71, 8-75, A-7, A-8 RDFVOLUME 8-61, 8-71 receiver process 3-25, 3-27 REMOTECONTROLSUBVOL 8-16 remotesys 8-16 RESET PROCESS 8-53, 8-56, 8-57, 8-59, 8-61, 8-69, 8-71, 8-75, A-7, A-8 RETAINCOUNT 8-61, 8-71 SUFFIX 8-38 TIMESTAMP 8-38, 8-97 UPDATERDELAY 8-64 UPDATEVOLUME 8-75 VOLUME 8-19 performance 3-2 processes 1-14 RDFCOM 4-1 requirements hardware 2-1 so
Index R RDFCOM commands (continued) VALIDATE CONFIGURATION 8-104, A-13 description 4-1 keywords 4-7 online help 4-10 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, 3-10 security requirements 3-12 RDFINST installation macro 3-9, 3-10 RDFLOCK file description B-9 RDFLOG 4-13, A-14 RDFMONO monitor object file 3-9, 3-10 security requirements 3-12 RDFNETO security
Index S Receiver process parameters (continued) resetting option values 8-51, A-6 SET RECEIVER example 8-63, 8-73, 8-74 setting option values 8-61, 8-71, A-10 SHOW RECEIVER example 8-81 Recompiling programs 3-9 Reload of Backup Database 2-8 REMOTECONTROLSUBVOL network attribute 13-4 REMOTECONTROLSUBVOL parameter 8-16 REMOTESYS parameter 8-16 Replicating database operations 2-9 Replication file-level 11-1 subvolume-level 11-1 to multiple backup systems 1-28 replication to multiple backup systems 1-28 Repor
Index T SQL/MX Name Mapping 15-13 SQL/MX offline synchronization for a single partition 15-11 SQL/MX tables, comparing 15-18 SQL/MX tables, restoring 15-16 START RDF command 3-31, 8-84, A-11 START TMF command, TMFCOM 3-30 START TRANSACTION command, TMFCOM 3-8, 3-13 START UPDATE command 3-32, 8-86, A-11 Starting the RDF subsystem 3-30 the TMF subsystem 3-30 STATUS RDF command 4-18, 8-87, A-12 STOP RDF command 8-94, A-12 STOP SYNCH command 8-96, A-12 STOP UPDATE command 5-25, 8-97, A-13 Stopping RDF from ba
Index U TMF subsystem (continued) transactions designing for RDF protection 2-8 volume crash 5-9 with dump process 2-6 without dump process 2-6 TMFCOM START TRANSACTION command 3-8, 3-13 Transactions designing for RDF protection 2-8 lockstep 14-4 network 13-1 Triple contingency feature 1-30, 10-1 INFO VOLUME example 8-35 RESET VOLUME example 8-52 resetting option values 8-51, A-6 SET VOLUME example 8-78 setting option values 8-75 SHOW VOLUME example 8-82 partitioned files, auditing 1-23 RDF errors 5-1 re
Index Z Z Zero lost transactions 16-1 ZLT 16-1 Special Characters * wildcard character 9-14 ? wildcard character 9-14 HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002 Index-14
