HP NonStop RDF Management Manual Download Page 21

Page: 21 / 478

List of Tables

1-1

Audit Records at the Time of a Primary System Failure..............................................................34

2-1

RDF Hardware Requirements.......................................................................................................57

2-2

Software Requirements.................................................................................................................60

3-1

RDF Process and Program Security Attributes.............................................................................76

4-1

RDFCOM Configuration Commands..........................................................................................105

4-2

RDFCOM Operational Commands.............................................................................................106

4-3

RDFCOM Utility Commands......................................................................................................107

4-4

RDFSCAN Commands................................................................................................................110

4-5

RDF States....................................................................................................................................113

5-1

Recovery From File Modification Failures (RDF Event 700).......................................................122

5-2

Recovery From File Open Failures (RDF Event 705)...................................................................123

5-3

Recovery From File Creation Failures (RDF Event 739)..............................................................123

8-1

Systems for RDFCOM Commands..............................................................................................188

8-2

Default User Security for RDFCOM Commands........................................................................189

9-1

Pattern Matching Symbols in RDFSCAN....................................................................................268

D-1

Operational Limits for RDF/IMP, IMPX, and ZLT......................................................................463

E-1

RDF Metrics Reported by ASAP.................................................................................................467

Summary of Contents for NonStop RDF

Page 1: ...NonStop RDF System Management Manual for J series and H series RVUs RDF 1 9 HP Part Number 529826 006 Published June 2009 Edition J06 03 and subsequent J series RVUs and H06 03 and subsequent H series RVUs ...

Page 2: ...if are trademarks of the Open Software Foundation Inc OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing performance or use of this mat...

Page 3: ... and Operations 38 Scanning the EMS Event Log 38 RDF Tasks 39 RDF Processes 40 Primary System Processes 41 Backup System Processes 42 RDF Operations 42 Monitor Process 42 Extractor Process 42 Receiver Process 44 Sorted Image Trails 45 RDF Control Points 46 RDFNET Process 46 Updater Processes 46 Audited Database Files 47 REDO Pass 48 UNDO Pass 48 Restart Information 48 Partitioned Files Alternate K...

Page 4: ... the Primary System 61 TMF Configuration Without Dump Process on the Primary System 61 Configuring TMF for RDF Operations on the Backup System 61 Preparing Databases for RDF Protection 62 Audited Files Per Volume on Primary System 62 Audited Backup Database Files 62 Reload of Backup Database 62 Disk Process Pins on Database Volumes 62 DSM Catalogs and File Code 900 63 Views on the Backup System 63...

Page 5: ...system Running Previously 79 Initializing and Configuring RDF 79 Initializing RDF 79 Initializing RDF To a TMF Shutdown Timestamp 80 Initializing RDF Without any Timestamp Option 80 Initializing RDF Without Stopping TMF Using INITTIME Option 80 Determining a Valid inittime Value 81 Special Considerations 81 Enscribe Create Records 81 Stop RDF Updater Records 81 TMF Shutdown Records 82 Online Insta...

Page 6: ...g Scripts for Easy and Fast RDF Initialization and Configuration 103 Managing Multiple RDF Environments from One RDFCOM Session 104 Controlling Multiple RDF Environments Running on Different Nodes with a Single Obey File 104 Using RDFCOM Commands 105 Configuration Commands 105 Operational Commands 106 Utility Commands 106 Entering Commands 107 Requesting Online Help 107 Help for Command Syntax 107...

Page 7: ...System 129 Volume Recovery Processing 129 Volume Recovery Failure 129 File Recovery on the Primary System 130 File Recovery on the Backup System 130 TMFCOM ABORT TRANSACTION With AVOIDHANGING Option on Primary System 131 Audit Trails Pinned by RDF on the Primary System 131 Stopping RDF 132 Stopping RDF by Stopping TMF 133 Stopping RDF From the Primary System 134 Stopping RDF From the Backup System...

Page 8: ...ail Files 153 TMF and Online Dumps on the Backup System 154 Doing FUP RELOAD Operations With Updaters Running 155 Exception File Optimization 155 Switching Disks on Updater UPDATEVOLUMES 155 Online Remirroring of Updater SUBVOLUMES 156 6 Maintaining the Databases 157 Understanding Database States 157 Making Changes to Database Structures 159 NonStop SQL MP or NonStop SQL MX Databases 160 Catalog C...

Page 9: ...uenced Files with Create Load Step 4 Method 1 177 Key Sequenced Files with FRNL Step 4 Method 2 178 Relative Files with Create Load Step 4 Method 1 178 Relative Files with FRNL Step 4 Method 2 178 Entry Sequenced Files 178 NonStop SQL MP and NonStop SQL MX Tables Without Partitions 178 Tables with SYSKEY or Clustering Keys 178 Tables without SYSKEY and Clustering Keys 178 NonStop SQL MP and NonSto...

Page 10: ...97 Where Issued 197 Security Restrictions 197 RDF State Requirement 197 Usage Guidelines 197 COPYAUDIT Restartability 198 Example 199 DELETE 199 Where Issued 199 Security Restrictions 200 RDF State Requirement 200 Usage Guidelines 200 Examples 200 EXIT 201 Where Issued 201 Security Restrictions 201 RDF State Requirement 201 Usage Guidelines 201 Example 201 FC 201 Where Issued 202 Security Restrict...

Page 11: ...E RDF 212 Where Issued 215 Security Restrictions 215 RDF State Requirement 215 Usage Guidelines 215 Examples 217 OBEY 217 Where Issued 217 Security Restrictions 217 RDF State Requirement 217 Usage Guidelines 218 Example 218 OPEN 218 Where Issued 218 Security Restrictions 218 RDF State Requirement 218 Usage Guidelines 218 Examples 219 OUT 219 Where Issued 220 Security Restrictions 220 RDF State Req...

Page 12: ...tions 231 RDF State Requirements 231 Usage Guidelines 231 SET RDFNET 231 Where Issued 232 Security Restrictions 232 RDF State Requirements 232 Usage Guidelines 232 Example 232 SET RECEIVER 232 Where Issued 234 Security Restrictions 234 RDF State Requirements 234 Usage Guidelines 234 Examples 234 SET TRIGGER 235 Where Issued 235 Security Restrictions 236 RDF State Requirements 236 Usage Guidelines ...

Page 13: ...ATUS 244 Where Issued 245 Security Restrictions 245 RDF State Requirement 245 Usage Guidelines 245 STATUS RDF Command Output Display 245 RDF Process 247 Name 247 RTD Time 247 Pri 248 Volume and Seqnce 248 Cpus 249 Error 249 Special Messages 249 Examples 250 STOP RDF 250 Where Issued 250 Security Restrictions 251 RDF State Requirement 251 Usage Guidelines 251 Examples 252 STOP SYNCH 252 Where Issue...

Page 14: ...the EMS Log 261 Elements of RDFSCAN Command Descriptions 261 RDFSCAN Commands 262 AT 262 Usage Guidelines 262 Examples 262 DISPLAY 262 Usage Guidelines 263 Examples 263 EXIT 263 Usage Guidelines 263 Examples 264 FILE 264 Usage Guidelines 264 Examples 264 HELP 265 Usage Guidelines 265 Examples 265 LIST 265 Usage Guidelines 265 Output Displayed 266 Examples 266 LOG 266 Usage Guidelines 267 Output Di...

Page 15: ...rmance Ramifications 282 Summary Examples 282 12 Subvolume Name Mapping 285 Creating a Mapfile to Define the Rules for Subvolume Name Mapping 285 Rules for Creating Mapfile Mapping Strings 285 How an Updater Manages Filename Collisions 286 Creating a Maplog to Log Subvolume Name Mapping 287 Adding a Mapfile and Maplog to an Updater s Configuration Record 288 Managing Subvolume Name Mapping for Par...

Page 16: ...Network Validation and Considerations 303 RDF Reinitialization in a Network Environment 303 Network Master Subsystem Initialization 303 Non Network Master Subsystem Initialization 303 RDF Networks and ABORT or STOP RDF Operations 304 RDF Networks and Stop Update to Time Operations 304 Sample Configurations 305 Sample Network Master Configuration 305 Sample Non Network Master Configuration 306 RDFC...

Page 17: ... for Partition 332 Consideration for Creating Backup Tables 333 Restoring to a Specific Location 333 Example 333 Comparing NonStop SQL MX Tables 335 17 Zero Lost Transactions ZLT 337 How It Works 337 Using CommitHoldMode 340 Hardware Setup 340 Assigning CPUs on the Standby System 340 RDF Configuration Attributes 341 RDF Remote Mirror Configuration 341 RDF Remote Standby Configuration 341 RDF Confi...

Page 18: ...PDATE 355 STATUS 355 STOP RDF 356 STOP SYNCH 356 STOP UPDATE 356 TAKEOVER 356 UNPINAUDIT 356 VALIDATE CONFIGURATION 356 RDFSCAN Commands Quick Reference 357 AT 357 DISPLAY 357 EXIT 357 FILE 357 HELP 357 LIST 357 LOG 357 MATCH 357 NOLOG 358 SCAN 358 File Names and Process Identifiers 358 Reserved File Names 358 Disk File Names 358 Nondisk Device Names 358 Process File Names 358 B Additional Referen...

Page 19: ...OM Messages 413 RDFSCAN Messages 461 D Operational Limits 463 E Using ASAP 465 Architectural Overview 465 Installation 466 Auto Discovery 466 Monitoring Specific RDF Environments 466 Adding and Removing RDF Environments 467 Version Compatibility 467 RDF Metrics Reported by ASAP 467 Index 469 Table of Contents 19 ...

Page 20: ...rations 158 6 3 Synchronized Databases No Outstanding Audit 158 6 4 Synchronized Databases After STOP TMF Command 159 6 5 Unsynchronized Databases 159 10 1 RDFZLT with Triple Contingency 276 17 1 ZLT Configuration With a Single Standby Backup System 338 17 2 ZLT Configuration With a Single Standby Backup System and With the Remote Mirror Located at an Intermediate Site 338 17 3 ZLT Configuration W...

Page 21: ...DFCOM Utility Commands 107 4 4 RDFSCAN Commands 110 4 5 RDF States 113 5 1 Recovery From File Modification Failures RDF Event 700 122 5 2 Recovery From File Open Failures RDF Event 705 123 5 3 Recovery From File Creation Failures RDF Event 739 123 8 1 Systems for RDFCOM Commands 188 8 2 Default User Security for RDFCOM Commands 189 9 1 Pattern Matching Symbols in RDFSCAN 268 D 1 Operational Limits...

Page 22: ...List of Examples 1 1 Reciprocal Replication 50 1 2 Chain Replication 51 1 3 Invalid Chain Replication 51 22 List of Examples ...

Page 23: ...nally it lists all RDF messages and describes their meaning and any corrective actions that users must take Supported Release Version Updates RVUs This manual supports J06 03 and all subsequent J series RVUs and H06 03 and all subsequent H series RVUs until otherwise indicated by its replacement publications Intended Audience This manual contains information for everyone responsible for RDF instal...

Page 24: ... Updated details on PROTECTED mode in UPDATEROPEN Attribute page 86 Added the section Dedicated Image Trails or Image Trails on UpdateVolumes page 89 Added the section Using Scripts for Easy and Fast RDF Initialization and Configuration page 103 Added and updated Table 4 5 RDF States in RDF States page 113 Updated Main STATUS RDF Display page 114 Updated effects and workaround for Exceeding the Ma...

Page 25: ...ccurs at the primary system site and perform other specialized tasks Chapter 6 page 157 details how to back up altered database structures and how to resynchronize the primary and backup databases Chapter 7 page 167 describes how to synchronize entire databases or selected database volumes online Chapter 8 page 187 and Chapter 9 page 261 present the syntax of all RDFCOM and RDFSCAN commands respec...

Page 26: ...ackets are required For example Use the cextdecs h header file Text displayed by the computer For example Last Logon 14 May 2006 08 02 23 A listing of computer code For example if listen sock 1 0 perror Listen Error exit 1 Bold Text Bold text in an example indicates user input typed at the terminal For example ENTER RUN CODE 123 CODE RECEIVED 123 00 The user must press the Return key after typing ...

Page 27: ... s char Punctuation Parentheses commas semicolons and other symbols not previously described must be typed as shown For example error NEXTFILENAME filename LISTOPENS SU process name su name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown For example repetition constant list Item Spacing Spaces shown between items ar...

Page 28: ... o i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes For example error FILE_GETINFO_ filenum i filename maxlen o i Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual Bold Text Bold text in an example indicates user input typed a...

Page 29: ...edes an octal number The B notation precedes a binary number The H notation precedes a hexadecimal number For example 005400 B101111 H2F P p register E e register Related Information This manual belongs to the NonStop data management library of manuals It is the only manual that fully and directly supports RDF To use this manual effectively however you should be familiar with the information for t...

Page 30: ... File Utility Program FUP Reference Manual which describes the command syntax and error messages for the File Utility Program FUP Operator Messages Manual which describes various error codes Guardian Procedure Errors and Messages Manual which provides additional details about understanding and correcting file system errors Publishing History Publication Date Product Version Part Number July 2005 N...

Page 31: ... for protection against regional disasters communicating with the primary system over an Expand network System managers and operators control RDF through RDFCOM a utility much like the TMFCOM command interpreter used to access TMF RDF IMP IMPX and ZLT generate fully tokenized command event error and warning messages in the Event Management System EMS log System managers and operators can monitor t...

Page 32: ...e same data for all committed transactions as in the primary database On the primary system RDF extractor processes read audit trails logs maintained by TMF of all database transactions that affect audited tables and files and send all audit records associated with volumes protected by RDF to RDF receiver processes on the backup system Each receiver process sorts the audit records and writes it to...

Page 33: ...e each receiver process writes all audit records 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 records from the secondary image trail and apply it to volumes D1 through D10 respectively on the backup system For example updater process UP1 only looks for audit records for tables a...

Page 34: ...m before the outage With ZLT functionality RDF fetches all remaining audit data from the remote mirror thereby guaranteeing no loss of committed data during the RDF takeover operation For information about the ZLT function see Chapter 17 page 337 Unplanned Outages Without ZLT Without ZLT functionality it is possible for some committed transactions to be lost during an unplanned outage When the RDF...

Page 35: ...was shut down After the primary database is consistent with the backup database you can perform another switchover this time from the backup system to the primary system and then restart the applications on the primary system For instructions on how to perform a switchover see Carrying Out a Planned Switchover page 136 Features In providing backup protection for online databases RDF offers many ad...

Page 36: ...int but can be useful for testing purposes Data from a set of volumes can be replicated to a different set of volumes on the same node 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 records from more than one audited vol...

Page 37: ...es and files that are being audited by TMF whether they are associated with the Master Audit Trail MAT or an auxiliary audit trail Subvolume and file replication In addition to volume replication the RDF IMP and IMPX products support replication of selected subvolumes and files RDF Subsystem Overview 37 ...

Page 38: ... as a stop update to time operation The latter allows you to do so without stopping TMF your applications or the RDF extractor Zero Lost Transactions ZLT ZLT is a functional capability that uses mirrored disks to guarantee that no committed transactions on the primary system will be lost in the event of an RDF takeover by the backup system User Interfaces To use RDF you run two online utilities RD...

Page 39: ...d to them by the extractor and the transformed audit records are then called image records On the backup system the receiver process accepts the buffer of image records sent by the extractor sorts each record to the correct image trail buffer and eventually writes the collection of image trail buffers to the actual image trailson disk On the backup system each updater process reads the image recor...

Page 40: ...he 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 in RDF Operations page 42 40 Introducing RDF ...

Page 41: ...dit trail the MAT or a particular auxiliary audit trail filters out audit records not relevant to the backup database transforms the audit record into an image record and then transmits the image records to an associated receiver process on the backup system Some control information for synchronizing the extractor and receiver process pair is included each time the extractor process transmits the ...

Page 42: ...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 RDF...

Page 43: ...s generated by applications Undo audit records for RDF protected files generated by TMF undo processing Filelabel modifications for the following Enscribe DDL operations CREATE PURGEDATA ALTER MAXEXTENTS PURGE if REPLICATEPURGE is enabled Filelabel modifications for the following NonStop SQL operation PURGEDATA NOTE Except for PURGEDATA RDF does not replicate NonStop SQL DDL operations on any SQL ...

Page 44: ...t trail file it pins the file by sending a message to TMF Once pinned an audit trail file remains pinned until the extractor unpins it or if you issue the RDFCOM UNPINAUDIT command at the primary system CAUTION Before deleting an RDF configuration always issue an UNPINAUDIT command to unpin any audit trail files that might be pinned by the configuration If you delete the configuration without firs...

Page 45: ...ils primarily contain the audit records that log changes made to the user s database on the primary system Updaters read secondary image trails and apply the changes recorded in the records to the database on the backup system All updaters must be configured to secondary image trails You can configure up to 255 secondary image trails Each secondary image trail is stored on a separate volume specif...

Page 46: ...cess The receiver also adds RDF control points to individual image trails if they have not received new audit while other trails have Thus the image trails can appear to be growing in size even though no transaction activity is taking place on the primary system The primary importance of RDF Control Points is that they are used to reflect accurate RTD times for the updaters when new audit has not ...

Page 47: ...pdaters will shut down if any of the following occurs You issue a STOP RDF or STOP UPDATE command on the primary system You issue a STOP RDF command on the backup system when the communications lines between the two systems are down You issue a STOP TMF command on the primary system The monitor detects the unexpected termination of any RDF process and sends out abort RDF messages You perform a Non...

Page 48: ...rations 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 For takeover operations there are three phases of und...

Page 49: ...lem goes away This would be the action for example if an updater process cannot create a data file on a backup volume because that volume is protected by the Safeguard security management subsystem in this case the updater logs error message 739 with an error 48 and restarts Skips the operation This would be the action for example in response to an error 10 record already exists RTD Times Write op...

Page 50: ...is still active The receiver is currently writing to image file AA000015 in both trails All updaters are currently reading audit records from AA000015 Although all the updater restart locations are in AA000015 none of the image files from AA000002 through AA000014 can be purged while T1000 is active or aborting because they will be required if T1000 needs to be backed out during an RDF takeover or...

Page 51: ... Replication The extractor of RDF Subsystem 1 sees that the update was for DATA and sends that update to B where the updater applies that update to Backup DB 1 This update generates an audit record that goes into the audit trail on B and is marked as updater generated The extractor for RDF Subsystem 2 reads the audit trail looking for audit associated with DATA When it reads the record generated b...

Page 52: ...ut Primary DB 2 and Backup DB 2 on DATA2 Thus the extractor can filter out the audit by volume name and not depend on records being marked as updater generated Alternatively if your two databases must share the same disks then you must explicitly specify which files and tables you want replicated by each RDF subsystem For example RDF Subsystem 1 would INCLUDE only Primary DB 1 and RDF Subsystem 2 ...

Page 53: ...RDF System Files page 362 Other RDF Features Triple Contingency If you are replicating your database to two backup systems and then lose your primary system you can perform an RDF takeover on both the backup systems upon loss of the primary system and continue application processing on the new system within minutes To proceed with full RDF protection however you must 1 Initiate a takeover on two o...

Page 54: ...this capability see Chapter 7 page 167 Online Dumps of the Backup Database With RDF IMPX or ZLT all backup databases are audited by TMF You can take online dumps of a backup database at any time thereby minimizing the amount of time necessary to perform any subsequent takeover operation For information about taking dumps while the updaters are running see Chapter 5 page 121 Subvolume Level and Fil...

Page 55: ...rocesses the extractor or any updater that have fallen behind the configured RTD threshold For information about setting the RTD threshold see SET RDF page 228 and RDF States page 113 Process Lockstep Operation Process lockstep operation which is available with the RDF IMPX and ZLT products prevents an application from executing further processing based on a committed business transaction until al...

Page 56: ... page 337 Monitoring RDF Entities With ASAP ASAP Availability Statistics and Performance allows many different subsystem entities to be monitored across a network of 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 PC client RDF IMP IMPX and ZLT a...

Page 57: ...d operating system for NonStop systems This system must be connected over an Expand data communication path to one or more RDF backup systems Backup System Configuration The RDF backup system like the primary system must operate under control of the NonStop operating system and be connected over an Expand path to one or more RDF primary systems In the event of a disaster at the primary site an ide...

Page 58: ...ifferently named subvolumes on the backup system For more information see Chapter 12 page 285 Expand Data Communication 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 Plan to configure sufficient communications resources between the primary and backup systems so that R...

Page 59: ...ths multi line Expand Each path should go through different communications carrier paths or switches and each should be able to transmit the peak data rate It is often sufficient to have a single Expand path driven out of a single processor and the use of Expand over Servernet Expand over IP Expand with ATM or Expand with Fast Ethernet provides considerable bandwidth For RDF environments where mul...

Page 60: ...RDF TMF does not retain pinning on behalf of RDF when TMF is stopped and then restarted If you must stop and restart TMF be sure to restart RDF before you restart your applications This causes RDF to re pin the audit trail files it needs and thereby prevents TMF from purging the files before RDF has finished processing them If you issue an UNPINAUDIT command while audit dumping is disabled and TMF...

Page 61: ...F is shut down If you must unpin one or more audit trail files you can do so by issuing an RDFCOM UNPINAUDIT command Later when RDF is restarted you can restore the necessary audit trail files from tape 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 TM...

Page 62: ...file must exist on a volume configured for an updater process on the backup system The volume name on the backup can differ from that on the primary For example if volume B on the backup system corresponds to volume A on the primary system then all files protected by RDF on volume A must be present and in the same subvolumes on B Chapter 3 page 69 explains how to copy NonStop SQL MP databases and ...

Page 63: ...hout interruption All base tables underlying the views must also reside on volumes protected by RDF on the primary system Partitioned Tables and Files If any partition of a partitioned NonStop SQL table or Enscribe file exists on a volume protected by RDF then all partitions for that file should be on volumes protected by RDF The partitions of a file protected by RDF can reside on separate systems...

Page 64: ...tem User programs should not create audited NonStop SQL tables and write to them without coordinating table creation on the primary system with table creation on the backup system Recommended procedures for performing NonStop SQL DDL operations in an RDF environment are described in NonStop SQL MP or NonStop SQL MX Databases page 160 Enscribe File Label Modifications In general RDF does not replic...

Page 65: ...y physical volumes and create SMF virtual disks from these pools In this configuration the files on any given virtual disk will be spread across multiple physical disks allowing you to pool together many physical disks to create a very large virtual disk NOTE A single updater process can only work on 3000 files at any time If you have a virtual disk that has a number of physical disks in its pool ...

Page 66: ... such limitation other than the limit of 255 updaters and each updater only being able to work on a maximum of 15 physical volumes Image trail volumes cannot reside on SMF logical volumes There are no restrictions on the placement of SMF catalog files on the backup system If the backup system could ever become a primary such as after an RDF takeover for example or as the result of a planned switch...

Page 67: ... allows physical disks to be added and removed from pools The RDF updaters must be stopped prior to the addition or deletion of any physical disks from SMF pools on the backup system Using SMF With RDF 67 ...

Page 68: ...68 ...

Page 69: ...u are going to do offline initialization or offline database synchronization stop the necessary software in this order a Stop all applications being protected by TMF b Stop TMF NOTE If you are going to use the DBSYNCHTIME parameter for online database synchronization or the INITTIME parameter for online initialization you do not need to stop your applications or TMF For information about online da...

Page 70: ...ync product to replicate everything else that is not audited such as important application files objects and scripts If the names of any volumes or devices that the applications might use on the backup system are different from the names on the primary system you must also change any references to these volumes or devices It is strongly recommended that the backup system have one volume for every ...

Page 71: ...nizing databases on NonStop systems are The TACL OBEY command enables you to create the same database structures on the primary system and the backup system by using commands in an EDIT file to create reusable TACL macros and routines The SQLCI or MXCI CREATE CATALOG command can re create NonStop SQL MP or NonStop SQL MX catalogs on the backup system The SQLCI or MXCI DUP utility can copy NonStop ...

Page 72: ...n the backup system by using the SQLCI DUP command In this example PRIM is the primary system and BACK is the backup system Notice that the catalog for this NonStop SQL MP table is created on the backup system before starting RDF on the primary system so that RDF will recognize the backup catalog and not report errors when attempting to process audit data for this catalog 1 Using SQLCI enter a CRE...

Page 73: ...p on the primary system to create a recovery point Synchronizing Databases With BACKUP and RESTORE Utilities You can use the BACKUP and RESTORE utilities to synchronize NonStop SQL MP NonStop SQL MX or Enscribe databases by copying a database to tape on the primary system and restoring the database from tape on the backup system This method is preferable when you want a backup tape of the primary ...

Page 74: ...en use FUP ALTER to incorporate the other partitions and any alternate indexes into the primary partition If the volume names for partitions on the backup system are different from the volume names on the primary system you need to change the volume references for those partitions Backing Up Application Programs and Files To enable the backup system to take over in the event of a primary system fa...

Page 75: ... The RDF extractor object code file RDFEXTO The RDFINST TACL macro an EDIT file RDFINST The RDF monitor object code file RDFMONO The RDFNET object code file RDFNETO The RDF receiver object code file RDFRCVO The RDF purger object code file RDFPRGO The RDFSCAN object code file RDFSCAN The RDFSCAN HELP file an EDIT file RDFSCANH The RDFSNOOP object code file RDFSNOOP The RDF updater object code file ...

Page 76: ...nly with the RDF IMPX and ZLT products For information about this capability see Chapter 15 page 309 Component Licensing Some of the files on the CD must be licensed before they can be run One of the advantages of using the RDFINST macro is that it automatically licenses those programs that need to be licensed RDFINST licenses these programs RDFAFXO RDFCOM RDFEXTO RDFMONO RDFPRGO RDFRCVO RDFSNOOP ...

Page 77: ...f the super user group user ID 255 nnn to change the running state of RDF Alternatively RDFCOM supports the use of the SAFEGUARD PROGID attribute to enable any user to start stop and manage RDF Once the PROGID attribute is set you must limit EXECUTE access to the RDFCOM object so that only those persons authorized to manage RDF can run RDFCOM RDFEXTO The RDF extractor program communicates with the...

Page 78: ...ter all RDF objects run as the userid of the RDF OWNER Initializing and Configuring TMF After copying the appropriate files from the primary system to the backup system you must ensure that TMF is configured on both systems to support RDF operations The actions you take to do this depend on whether or not TMF was running previously on this system TMF Subsystem Not Running Previously If TMF was not...

Page 79: ...ns exist for replication to multiple backup systems NOTE Previously you were required to purge the RDF control subvolumes on the primary and backup systems before you could run the RDFCOM Initialize RDF command see details on RDF control subvolume in Chapter 4 page 99 You can now specify a special option that automatically purges the existing control subvolume on the primary and backup system as p...

Page 80: ...m the primary system DALLAS RDF would respond by creating a configuration file in the control subvolume named SYSTEM DALLASA CONFIG Initializing RDF Without any Timestamp Option If you have just installed or deleted and reinstalled TMF so that it starts at relative byte address rba 0 in audit trail file sequence number 1 you should now issue an INITIALIZE RDF command without the TIMESTAMP paramete...

Page 81: ...nd with a timestamp specified with INITTIME there are three special cases that you might encounter Enscribe Create Records If the previous version of RDF performed an Enscribe create operation on the backup system prior to execution of the INITIALIZE RDF command and the extractor s restart position in the audit trail precedes the location of the Enscribe create record that an updater previously ap...

Page 82: ...d to stop RDF delete the control subvolumes reinitialize RDF and then restart RDF Although unlikely stopping RDF does leave you briefly vulnerable to inconsistent data on the backup system if your primary system should fail after you stop RDF and delete the previous RDF control files but before you restart RDF By using the procedure that follows you can install and initialize the RDF product witho...

Page 83: ...parallel sets of receivers for the two operating RDF subsystems although each subsystem has its own control subvolumes and its own imagetrail subvolumes 11 When the extractor s for RDF04A have caught up do the following a Issue a STOP RDF command for the previous RDF subsystem b Issue an UNPINAUDIT command for the previous subsystem c Issue a START UPDATE command for the RDF04A subsystem Wait unti...

Page 84: ...alues you want in the configuration memory table and then use ADD command to apply those values to the configuration file You do this for each process individually do all of the SETs for a process and then add the particular object Notice that the only purpose of the configuration memory table is to serve as a temporary repository of configuration attributes for the SET command Initially some of t...

Page 85: ...TEPVOL OFF REPLICATEPURGE OFF REMOTE MIRROR system undefined REMOTE STANDBY no default OWNER LOGFILE Attribute The LOGFILE attribute specifies the name of the EMS collector to which all RDF command event error and warning messages are to be directed The following commands specify the EMS collector CTD25 as the RDF log file on both the primary and backup systems SET RDF LOGFILE CTD25 ADD RDF The co...

Page 86: ...ld UPDATEROPEN Attribute The UPDATEROPEN attribute specifies the access mode PROTECTED PROTECTED OPEN or SHARED that updaters use when opening database files The default is PROTECTED PROTECTED mode is strongly recommended at all times to protect your backup database from improper write activity by processes other than an RDF updater PROTECTED mode also allows user applications to open backup datab...

Page 87: ...nly for the first and last audit records that must be undone the minimum logging necessary to support Triple Contingency operation LOCKSTEPVOL Attribute The LOCKSTEPVOL attribute specifies the primary system disk volume on which the RDF lockstep file control subvolume ZRDFLKSP is to be located The specified volume must be configured to the Master Audit Trail MAT and either the entire volume or at ...

Page 88: ...e a member of the super user group since that is an existing requirement in RDF for stopping and starting RDF OWNER is an unalterable value There is no need to change the value unless you configured it incorrectly in which case you must reinitialize RDF with the correct value If the OWNER attribute is omitted only the userid that initializes RDF can start or stop RDF as is true for all versions of...

Page 89: ...consider worst case situations where an updater might fall way behind in which case there might be a large number of image files on that UPDATEVOLUME Alternatively you may find that you can configure a small number of dedicated image trails and configure a large number of updaters to each dedicated trail provided that the volume of audit being written to the trail is generally less than 5 megabyte...

Page 90: ... volume name If you are configuring the network master RDF subsystem you must include a network configuration record for every RDF subsystem in the RDF network including the network master itself Each of those records must include the following parameters Name of the primary system PRIMARYSYSTEM system name Name of the associated backup system BACKUPSYSTEM system name Name of the primary system s ...

Page 91: ...ividual RDF processes the RDFNET monitor extractor receiver purger and updater processes RDFNET Process Use SET RDFNET and ADD RDFNET commands to configure the following RDFNET attributes CPUS primary CPU backup CPU PRIORITY PROCESS The CPUS attribute specifies the processors in the primary system in which the RDFNET process will run The PRIORITY attribute specifies the priority at which the RDFNE...

Page 92: ...s the extractor is associated with the MAT For information about protecting auxiliary audit trails see Chapter 13 page 291 The CPUS attribute specifies the processors in the primary system in which the extractor will run The PRIORITY attribute specifies the priority at which the extractor will run You should set the extractor s priority slightly lower than that of the RDF monitor process The PROCE...

Page 93: ...ding the symbol However you cannot specify HP reserved process names that are of the form X Y or Z in which is any alphanumeric string The RDFVOLUME attribute applies only to the master receiver It specifies which volume on the backup system will contain the receiver s master image trail The file naming convention for image trail files is volume control subvolume AAnnnnnn where n is a digit For ex...

Page 94: ...OCESS RETAINCOUNT PURGETIME The CPUS attribute specifies the processors in the backup system in which the purger is to run The PRIORITY attribute specifies the priority at which the purger will run You should set the purger s priority higher than that of any application s process and higher than that of any RDF updater process The PROCESS attribute supplies a name for the purger process You should...

Page 95: ...sly added to the RDF configuration You cannot add this updater process associating it to an image volume unless you have already added the image trail with the ADD IMAGETRAIL command Also the ATINDEX of this updater must match the ATINDEX of the associated image trail The UPDATEVOLUME attribute specifies the name of the disk volume on the backup system that corresponds to a particular volume on th...

Page 96: ...named RDF INIT enter the following command OUT RDF INIT 2 Issue an INFO command with the OBEYFORM attribute INFO OBEYFORM RDFCOM lists the current attributes in the RDF configuration file to RDF INIT in OBEY command file format 3 Issue another OUT command to redirect subsequent session output back to your terminal OUT For further information about configuration command files see the example file i...

Page 97: ...cess an RDFCOM object that has been PROGID d by the customer You can have a different super ID if the RDF OWNER attribute has been set You have a remote password on the primary system it is also recommended but not required that you have a remote password on the backup system as well The RDF configuration file contains all necessary attributes All updater volumes on the backup system are enabled f...

Page 98: ... processes you merely issue a START UPDATE command Restarting the Applications As the final step in establishing an RDF environment if you had shut down your applications previously you can restart them now 98 Installing and Configuring RDF ...

Page 99: ...sages with RDFSCAN The syntax and functional descriptions of all RDFCOM and RDFSCAN commands appear in Chapter 8 page 187 and Chapter 9 page 261 respectively For information about responding to error messages handling failures and stopping and restarting RDF see Chapter 5 page 121 For information about the messages themselves see Appendix C page 365 Running RDFCOM RDFCOM is an interactive command ...

Page 100: ...ted and RDFCOM output is directed to it If you specify a disk file that exists this must be an EDIT file file code 101 RDFCOM output is appended to that file If you omit the volume or subvolume portions of the file name specifier the default is your current volume or subvolume respectively control subvolume is the name of the RDF control subvolume on SYSTEM on the primary and backup systems as wel...

Page 101: ...sses it and then displays another right bracket prompt for your next command You continue interacting with RDFCOM in this way repeatedly receiving a prompt and entering a command until you explicitly end the session If it detects an error during startup RDFCOM displays an error message between the product banner and the right bracket prompt If it discovers an error in an RDFCOM command RDFCOM disp...

Page 102: ...nt configuration information for the RDF monitor the example assumes that LONDON is the primary system the suffix character A was specified in the INITIALIZE RDF command and the user did not explicitly name the monitor process 1 RDFCOM LONDONA INFO MONITOR RDFCOM T0346A07 05JUL05 C 2005 Hewlett Packard Development Company L P MONITOR CPUS 0 1 MONITOR PRIORITY 170 MONITOR PROCESS MON 2 As this exam...

Page 103: ...s Suppose you have created a command file named RDFINIT that contains the commands for initializing the subsystem You could execute all these commands by simply entering OBEY RDFINIT If you decide later that you want to use different installation attributes you can change the command file and then enter the OBEY command again Using command files makes performing repeated tasks very convenient Duri...

Page 104: ...st to edit the overall OBEY files to change the INITTIME value Secondly you might find it easier to keep the START RDFCOM command as a separate operation thereby keeping the configuration limited to just the different configuration commands Managing Multiple RDF Environments from One RDFCOM Session If you have multiple RDF subsystems running on a single node you can manage and monitor all of them ...

Page 105: ...r user group INFO and SHOW can be issued by anyone Table 4 1 RDFCOM Configuration Commands Function Object Command Applies option values from the configuration memory table to the RDF configuration file for the specified process or adds RDF and image trail configuration records to the RDF configuration file PURGER RDF RDFNET MONITOR NETWORK EXTRACTOR TRIGGER RECEIVER VOLUME IMAGETRAIL ADD Alters t...

Page 106: ... system that has the most audit to the one that has the least audit use this command only if you have configured RDF for Triple Contingency COPYAUDIT Starts RDF RDF START Starts all updater processes on the backup system UPDATE START Lists current information about RDF processes PROCESS MONITOR VOLUME RDF RTDWARNING EXTRACTOR RDFNET RECEIVER PURGER STATUS Stops RDF RDF STOP Signals the end of all ...

Page 107: ...ng if the maximum line length of your input device is less than 132 characters and your command input exceeds the device s limit the input will wrap around to the next line but will terminate when 132 characters have been read RDFCOM does not support additional entry lines or special command continuation characters RDFCOM supports a comments character vertical bar within command entry lines or wit...

Page 108: ...ESET SHOW SET RDF MONITOR EXTRACTOR RECEIVER IMAGETRAIL PURGER NETWORK RDFNET TRIGGER VOLUME Operational Commands COPYAUDIT START STATUS STOP TAKEOVER UNPINAUDIT VALIDATE Utility Commands EXIT FC HELP HISTORY OBEY OPEN OUT RDF Concepts Abbreviations RDF error messages error number E g help 700 prints an explanation for the RDF error message 700 Help for RDF Error Messages For information about a p...

Page 109: ... use the following command syntax RDFSCAN filename RDFSCAN is an implicit RUN command instructing the TACL command interpreter to run the RDFSCAN utility program filename specifies the entry sequenced file to be opened 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 d...

Page 110: ...ll of these commands are unrestricted they can be entered by any user Table 4 4 RDFSCAN Commands Function Object Command Specifies the record number at which to begin the next RDFSCAN function record number AT Enables or disables the display of record numbers for the lines listed ON OFF DISPLAY Terminates an RDFSCAN session EXIT Opens the specified file as the current EMS log log file FILE Display...

Page 111: ...DFscan function you want HELP LIST In response RDFSCAN displays the following LIST count List will display count records from the current record pointer set with AT If a pattern match has been selected with Match then only those records that match will be displayed count specifies how many records will be displayed even if many more must be read Scan will only read count no matter how many are dis...

Page 112: ...erforming Routine Operational Tasks Through RDFCOM and RDFSCAN you can perform many different RDF functions Among these are the routine operational tasks that system operators do from day to day These routine tasks include Displaying current configuration attributes and operating statistics Changing configuration attributes Reading RDF messages Other specialized tasks are described throughout the ...

Page 113: ... yet started Start Update Pending RDF was running with Update On Update was just turned Off but one or more updaters have not yet stopped Stop Update Pending RDF was running with Update On you issued a STOP UPDATE command with the timestamp option but one or more updaters have not reached the end of Redo and or Undo operations Stop Update Timestamp Pending RDF was running with Update On you have i...

Page 114: ...RCV0 are associated with the MAT while the extractor REXT1 and receiver RRCV1 are associated with auxiliary audit trail AUX01 Because of insufficient space however ATINDEX values are not displayed explicitly for updaters To determine the ATINDEX value of a particular updater see the ATINDEX value of the updater s specific image trail In this example a monitor process and two extractor processes ar...

Page 115: ...olume and Seqnce together specify a file associated with each process The monitor entry reflects the name of the MAT file to which TMF is writing AUDIT ZTMFAT AA000056 in this example Each extractor entry reflects the name of the TMF audit trail file that it is reading AUDIT ZTMFAT AA000056 for the master extractor and DATA17 ZTMFAT BB000004 for the auxiliary extractor in this example The master r...

Page 116: ...s why For example the report might indicate that the subsystem has never been started or that it has crashed The report also indicates where processing resumes in the TMF audit trail when RDF is restarted When the BREAK key is pressed while the STATUS RDF command is executing with the PERIOD option which requests repeated displays at a specified interval the break takes effect within one second ra...

Page 117: ...er processes To redirect messages from the current EMS log to the log named EMSC on the control subvolume CHICAGO enter ALTER RDF LOGFILE EMSC The specified collector must reside on the local system For example if you are in an RDFCOM session on the system SANFRAN you cannot specify something like CHICAGO EMSC as the log For more information about the EMS log see Chapter 1 page 31 Chapter 3 page 6...

Page 118: ...ace or you can enter HELP and the RDF event number to an RDFCOM prompt For example HELP 906 This command returns the following 906 Process creation error nnn nnn file file name Cause The process encountered an error while attempting to create an RDF process The error fields reported in the message are the error and error detail fields returned by the PROCESS_CREATE_ system procedure followed by th...

Page 119: ... Date is the date the message occurred as reflected on the sending system 1 Time is the time the message occurred as reflected on the sending system 2 System is the name of the system where the RDF process to which this message pertains is running 3 RDF Process is the name of the RDF process to which the message pertains 4 Message Number is the number that identifies the RDF message and its meanin...

Page 120: ...DF Remote Updater Started POPPY BPOPPY File SYSTEM RDF RDFLOG current record 761 last record 903 Pattern REMOTE Enter the next RDFSCAN function you want EXIT Thank you for using RDFSCAN More information about the RDFSCAN commands and elements shown in this example appears in Chapter 9 page 261 ASAP HP s NonStop ASAP product provides in depth monitoring of the RDF subsystem It monitors the availabi...

Page 121: ...n page 155 Switching Disks on Updater UPDATEVOLUMES page 155 Online Remirroring of Updater SUBVOLUMES page 156 Recovering From File System Errors All RDF processes can encounter file system error conditions If it is RDFCOM it reports an error message that includes the file system error in the RDFCOM Outfile For any other RDF process the monitor the extractor the receiver the purger the updater or ...

Page 122: ...ror condition you must reinitialize and reconfigure RDF to a point earlier than the record that caused the error and then restart RDF 2 Check the file integrity This could mean either loss of data or duplicated audit records If data was lost resynchronize the file If audit records were duplicated then no harm occurred The updater process skips the modify operation 10 Check the file integrity This ...

Page 123: ...r the device or clear the condition 120 through 121 Repair the device or clear the condition 130 through 139 Check file integrity 157 Repair the device or clear the condition 190 Alter the security probably Safeguard 199 Repair the device or clear the condition 200 through 231 Table 5 3 lists the file system error numbers and recovery actions for RDF event 739 which reports file creation failures ...

Page 124: ...error 43 condition however processing resumes automatically You can do this by moving any files that might not be needed be sure however to restore them before the receiver and updaters need them Alternatively you can accomplish this goal by backing up with the BACKUP utility an unopened image file then purging that file and finally restoring it with the RESTORE utility when the first file system ...

Page 125: ...minimum value of 10 seconds as a short term workaround If this does not correct the problem then the easiest way to correct the problem is to suspend the extractor on the primary system for 10 minutes If you have RDF ZLT protection then you are not at risk of losing any data if your primary system should fail while the extractor is suspended If you do not have RDF ZLT protection then you are vulne...

Page 126: ...m and reports that the line is down All of the processes on the backup system continue to run until a STOP RDF command is issued at the backup system NOTE If you issue a STOP RDF command on the primary or backup system while the network is down you must also issue a STOP RDF command on the other system while the network is still down If you have an RDF network running and the Network Master s RDFN...

Page 127: ...any disk volumes to the RDF configuration with the ADD VOLUME command If the primary CPU of the extractor process fails the backup extractor process requests from the receiver a new starting position in the audit trail ensuring a correct restart position This extractor receiver protocol also provides protection against messages from the extractor erroneously arriving out of order if a message arri...

Page 128: ...rocess Pair Directory PPD to ensure that the appropriate RDF processes all have stopped if they have not you must stop them manually If a state transition failure occurs during execution of a STOP RDF command and the operation appears to be stalled manually stop all of the RDF processes by issuing the following command on both the primary and backup system STATUS PROG RDF software loc STOP For exa...

Page 129: ... the same data over and over again without moving forward To correct that situation you merely stop and then restart the RDF subsystem 5 Restart your applications TMF Subsystem Failure on the Backup System RDF can recover from a TMF failure on the backup system if the TMF volume recovery operation is successful after the failure To perform this recovery 1 From the primary system stop updating of t...

Page 130: ...o a timestamp or first purge File Recovery on the Backup System You are encouraged to take online dumps on your backup database on a regular basis for the following reasons If you have lost your primary system and have taken over on your backup system the online dumps can be used for any type of file recovery operation provided the redo end point is located after all audit data that was generated ...

Page 131: ... to an RDF internal entry listed in the ZFILEINC file needs to be undone as a part of an RDF TAKEOVER operation then using the above described brute force method might corrupt the database on the backup system It might also affect the Stop Update To Time operations Audit Trails Pinned by RDF on the Primary System When you start RDF the extractor pins the audit trail file it is currently reading in...

Page 132: ...nt In this example however the control subvolume does not even exist because it was deleted at the end of the test If you find yourself in this situation then you must configure an RDF subsystem with the name of the control subvolume listed in the TMF event Once you have configured it you can then issue the RDFCOM OPEN command specifying this control subvolume and then issue the UNPINAUDIT command...

Page 133: ...s not wait for any other process to stop it merely stops when informed to do so 4 If updating is enabled each updater process stops when it reaches the TMF shutdown record in its image trail 5 The purger stops after all the updaters have stopped 6 The receiver s stop when the purger has stopped 7 The monitor stops after all the other RDF processes have stopped If you stop TMF and then restart it b...

Page 134: ...sue STATUS RDF commands and wait until all of the RDF Time Delay RTD times are zero Issue the STOP RDF command NOTE Even when no TMF transactions are in progress TMF periodically writes control points to the MAT which means that the MAT continues to fill even when no application activity occurs This can cause RTD times in the status display to fluctuate For an alternate method of bringing the back...

Page 135: ...orking on its own database and if not all are protected by the one RDF subsystem then you may not want to stop TMF just to shutdown the RDF subsystem In this situation you can use the STOP RDF DRAIN command but you must observe the following sequence of steps 1 Stop the application that is updating your RDF protected database 2 Enter the STOP RDF DRAIN command In response to the DRAIN command the ...

Page 136: ...est possible switchover time because the same issues apply whether you are moving business operations due to a switchover planned outage of your primary system or takeover unplanned outage of your primary system Standard Configurations In a standard RDF configuration system A the primary system B the backup the steps for performing a planned switchover from A to B are 1 On system A stop the busine...

Page 137: ...e 2 Watch for the extractor s RTD to be 0 00 3 Enter the STOP RDF REVERSE command When the extractor receives notice of the operation it notes where it is in the audit trail and shuts down and the updaters shut down as soon as they have reached the equivalent location This is identical to the DRAIN command Next RDF automatically executes the REVERSE trigger that you have configured You would want ...

Page 138: ...bsystem 2 Note the local system time you will need it later 2 On system A stop the business applications that access the primary database Applications 1 3 On system A stop TMF or if you do not want to stop TMF use the STOP RDF DRAIN command 4 Wait for RDF subsystem 1 on A to shut down 5 On system B restart Applications 1 At this point the RDF subsystem is down on both systems the business applicat...

Page 139: ...m at the time the primary system failed Alternatively the transactions might have been resolved on the primary system but the extractor was stopped before it could send the final outcomes to the backup system The takeover operation determines what audit needs to be backed out in order to bring the backup database into a stable and consistent state Audit is backed out of the backup database during ...

Page 140: ...or a complete description of the takeover operation in an RDF network see RDF Takeovers Within a Network Environment page 298 Transactions that must be undone during this undo pass are stored in the ZNETUNDO file in the Master Image Trail subvolume Issuing the TAKEOVER Command Before you issue a TAKEOVER command on your backup system you need to start an RDFCOM session for the correct control subv...

Page 141: ...me of this monitor on the backup system is generated by the system If RDF had been stopped RDFCOM starts the monitor in TAKEOVER mode The monitor then starts the receiver purger and all updater processes The name of this monitor is generated by the system If a monitor process was started on the backup system the monitor stops after the other RDF processes have all shut down The following example s...

Page 142: ...e RDFCOM prompt as shown below RDFCOM obey RDFTKOV 3 The third option is to write the TAKEOVER command appended with the bang character in an EDIT file and pass it as an IN file to RDFCOM For example consider an EDIT file RDFTKOV has the following content TAKEOVER Now you can use the EDIT file RDFTKOV as an INFILE to RDFCOM using the following command RDFCOM IN RDFTKOV NOTE RDFCOM does not allow t...

Page 143: ...your new primary configure a new RDF system to run from this new primary to the backup and then resume application processing on the new primary with full RDF protection If each reports a different MAT position then go to the backup system with the lowest MAT position and execute the COPYAUDIT command see Chapter 10 for details The COPYAUDIT command will copy over all additional audit that the oth...

Page 144: ... lowest possible RTO While the RDF takeover operation itself normally takes only a small number of seconds there are many other issues to consider in order to achieve an optimal RTO and this is the focus of the discussion that follows As a rule the more you plan in advance the more you can lower your RTO 2 Be Sure You Have All You Need While RDF keeps your backup database up to date there are doub...

Page 145: ...r command If specified it eliminates the user prompt and it eliminates the check to reach the primary system thereby eliminating the Expand level 4 timer But before you use this option you should consider the following points a How do you know if the primary system is down By having RDFCOM check to see if the primary system is accessible you avoid starting a takeover operation by mistake While the...

Page 146: ... for takeover authorization f Handle any tasks that pertain to your specific operations There may be any number of things to be done One task for example may be to determine what transactional work was either never completed on the primary at the time of the disaster and what was undone by RDF during the takeover this allows you to determine what work you might need to have your applications repro...

Page 147: ...ume business operations on your backup system Test your applications against your backup database When you have finished your testing clean up the backup database Either make your backup system your new primary or switch business operations back to your original primary system 13 Suggestions for cleaning up your backup database after a test a If your database is small you might just resynchronize ...

Page 148: ...Event 888 When File Recovery completes the database on your primary system is in complete logical synchronization with the database on your backup system at the time when the RDF takeover operation completed If you had resumed business operations on your backup system run a new RDF configuration to bring the old primary system up to date with the business operations that have taken place on the ol...

Page 149: ...te updating for transaction 50 To read the backup database while RDF is running your application should open the backup files with SHARED READ ONLY access Near Real Time Read Access to Updates on the Primary System The receiver configuration option FASTUPDATEMODE formerly known as SLOWMODE controls the frequency with which the receiver writes to the image trails and makes image trail audit availab...

Page 150: ...for RDF initialization 20JUN2004 12 48 for example When you include the timestamp its value must be based on the time of your primary system and must be at least 5 minutes in the future The updaters will apply all audit associated with transactions that committed prior to the timestamp you specify For any audit the updater may have applied prior to stopping its redo pass but where that audit is as...

Page 151: ...me operation had caused some audit to be backed out when you restart the updaters these updaters reapply all audit they had previously undone and the database stays in a state of synchronization with the database on the primary system If you erroneously set the timestamp too far into the future for example 26DEC3000 the only way to correct this mistake is to enter a STOP RDF command restart RDF an...

Page 152: ...d and the display from a STATUS RDF command shows that the RTD time for every updater process is zero the DDL operations can be safely applied Performing Shared Access DDL Operations DDL operations that include the WITH SHARED ACCESS option and are performed on the primary system generate a special Stop RDF Updater audit record in the MAT As each updater on the backup system encounters that record...

Page 153: ... can lead to an abort with database corruption You can however avoid that situation entirely by using the protocol described in Network Configurations and Shared Access NonStop SQL MP DDL Operations page 303 when performing shared access NonStop SQL MP DDL operations in a network environment RDF and NonStop SQL MX Operations For particular information about replicating NonStop SQL MX objects see C...

Page 154: ...les operation to recover the files onto a new disk Without the online dump you will have to stop RDF reinitialize RDF and then perform a partial database synchronization online or offline see Chapter 7 If your database files are smallish then perhaps database synchronization is a more viable solution to recovery from a media failure If your database files are very large then TMF File Recovery migh...

Page 155: ...ll If one or more long running transactions are active at the time of a takeover however the amount of undo required can increase substantially depending upon the amount of audit records generated by those transactions If you are protecting auxiliary audit trail volumes a considerable amount of undo could also be required if any of the extractor receiver pairs master or auxiliary falls behind the ...

Page 156: ...To avoid these errors always stop the updaters first issue the SCF PRIMARY DISK command and restart the updaters Online Remirroring of Updater SUBVOLUMES If you attempt to re mirror an updater s UPDATEVOLUME online the affected updater might report a number of RDF 700 events with the file system errors 10 11 and 71 In this situation these errors can be expected and they do not indicate that the ba...

Page 157: ... Figure 6 1 shows synchronized databases where RDF has just been initialized and the application on PRIMARY is going to be started The databases are synchronized because they contain the same logical data and no audit has been generated Figure 6 1 Synchronized Databases Before Starting RDF Figure 6 2 shows synchronized databases where the application is running on PRIMARY three more transactions T...

Page 158: ...abase Figure 6 3 Synchronized Databases No Outstanding Audit Figure 6 4 shows synchronized databases where TMF has just been shut down The databases are synchronized because RDF applies all audit generated on PRIMARY to the backup database before the subsystem reads the TMF shutdown record and subsequently shuts down the databases are not however logically identical until RDF has actually shut dow...

Page 159: ... an unexpected shutdown and the extractor cannot transmit the commit or abort status records for those transactions T5 and T6 to the backup system NOTE If you have not lost your primary system to a disaster then when the failed system comes back online and RDF is restarted RDF will put the backup database into synchronization with the primary when it has caught up Figure 6 5 Unsynchronized Databas...

Page 160: ...anges to a table that has a catalog file code An update operation to a table that does not exist causes RDF to log an RDF error message 736 citing file system error 11 and the updater retries until the file is created by the user DDL Operations Every NonStop SQL MP or NonStop SQL MX DDL operation performed on the primary system must also be performed on the backup system by NonStop SQL MP or NonSt...

Page 161: ... have processed all audit up to the point where you issued the STOP RDF DRAIN command which must be issued after you stopped your applications If no updaters stopped prematurely the purger logs RDF event 852 and it now safe for you to perform the same DDL change on the primary and backup systems before restarting RDF and your applications Adding a New Column This is an operation that cannot be per...

Page 162: ...ult catalog for the backup database CATALOG BACK DATA DBCAT 5 Create the index for the backup database Note because the updaters are stopped you do no need to include the With Shared Access option and the operation in fact completes faster CREATE INDEX BACK DATA1 DB FIRST ON BACK DATA1 DB EMPLOYEE FIRST NAME LAST NAME You should use WITH SHARED ACCESS for the CREATE INDEX operations in the above e...

Page 163: ...BASE TABLE CATALOG DATA RDFSQL VERSION 2 TYPE K EXT 16 PAGES 64 PAGES MAXEXTENTS 160 REC 416 PACKED REC 415 BLOCK 4096 KEY COLUMN 0 OFFSET 0 LENGTH 4 ASC INDEX 1 DATA RDFSQL MASTXYZ create this index first COLUMN 18 OFFSET 54 LENGTH 2 ASC COLUMN 19 OFFSET 56 LENGTH 2 ASC NOT UNIQUE INDEX 2 DATA RDFSQL MASTABC create this index second COLUMN 88 OFFSET 300 LENGTH 15 ASC COLUMN 87 OFFSET 285 LENGTH 1...

Page 164: ...n the primary system 2 Stop TMF on the primary system wait for RDF to read the STOP TMF message in the audit trail and stop itself 3 Start TMF on the primary system so the operations on audited Enscribe files can be performed 4 Start RDF so that no audit trails are lost but do not resume application processing 5 Perform each operation on Enscribe files on the backup system and the corresponding op...

Page 165: ... STOP RDF command is issued at the primary system If RDF fails and reports an event whose recovery text indicates that database resynchronization is required you must resynchronize the backup and primary databases Resynchronizing Entire Databases Offline To resynchronize an entire database offline you must stop TMF initialize RDF to the TMF shutdown timestamp and then copy the complete database fr...

Page 166: ...les 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 1 Stop your applications It is also recommended that you stop TMF too because this guarantees that no unexpected updates can touch the database but it is not a requirement if you are certain yo...

Page 167: ...ith shared access Because the load operation with shared access reads through transaction locks held by applications the resulting file is inconsistent with respect to transactions but it is consistent with respect to its physical state When you have completed getting a copy of your database by either of the methods stated above and you have moved the copy to the backup system issue a START UPDATE...

Page 168: ...LUDE and EXCLUDE options for your updaters 3 Configure RDF and then issue a START RDF UPDATE OFF command on the primary system 4 Make a copy of all tables and files in the database Method 1 Create an empty set of duplicate key sequenced and relative files and tables that do not have SYSKEYs and clustering keys on either the primary or backup system The duplicate tables and files must not be audite...

Page 169: ...es If the primary partition references secondary partitions that include the primary system name you must alter the primary system name to that of the backup system If you have an RDF network for replicating network transactions then you will need to alter the partition names to reference the correct names of the backup systems where the partitions are located 7 When a new copy of your database is...

Page 170: ... obtain the copy and prepare it than you have image space for then you might want to synchronize one part of the database at a time When that operation has completed you would then synchronize the next portion See the discussion on partial database synchronization and the issues pertaining to it that follows SYNCHDBTIME Issues With the SYNCHDBTIME option in the INITIALIZE RDF command there are thr...

Page 171: ... relative files and tables that do not have SYSKEYs and clustering keys on either the primary or backup system The duplicate tables and files must not be audited The LOAD command only works on tables and files that are nonaudited If you create the empty duplicate tables and files as audited entities you must then use FUP ALTER commands to turn off their audit attributes before you can load them Yo...

Page 172: ...e page 168 Partitioned tables You can initiate the load operation with a single command by executing the LOAD command against the primary partition Index tables With regard to index tables there are several considerations for relative and key sequenced tables Regardless of base table type you cannot load an index table by itself Index tables can only be loaded when the associated relative or key s...

Page 173: ...te tables You can create the duplicate tables on the backup system and then load them over the network from the primary system but you must be knowledgeable about issues regarding differences in table and catalog versions See the SQL MP Version Management Guide or SQL MX Database and Application Migration Guide You can create and load the duplicate tables on the primary system and then move them t...

Page 174: ...B SYNCHDBTIME 17JUN2004 17 05 NOTE If you have multiple RDF environments you can do online synchronization within one RDF environment without disturbing any of the other RDF environments Just be sure to include the appropriate SUFFIX attribute in the above INITIALIZE RDF command 3 Configure RDF and then issue the following RDFCOM command START RDF UPDATE OFF 4 Create a set of empty nonaudited Ensc...

Page 175: ...er 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 Remember that the files must be duplicated to the volumes on the backup system that are mapped to the corresponding volumes where the database resides on the primary system Assume you issue the FUP DUP command at the primary system and that...

Page 176: ...ready synchronized you do not need to obtain new copies see Step 4 of the files and tables and load copies of the files and tables on those volumes because they are already synchronized For the two new volumes you need to synchronize these following the steps for an entire database synchronization When these two new volumes have been synchronized you follow the same procedure discussed above and a...

Page 177: ... or Method 2 of Step 4 under Synchronizing Entire Databases Online page 168 to obtain a new copy of the file set Then use BACKUP and RESTORE or FUP DUP to move the duplicate file to the backup system Alternatively if you use Step 4 Method 1 you can create the duplicate file directly on the backup system and then load it across the network provided you have enough Expand capacity to handle both the...

Page 178: ...tive file Therefore only one command is possible FUP LOAD DATA1 TEST PART0100 DATA1 TEMP PART0100 SHARE You can then use BACKUP and RESTORE or FUP DUP with the PARTONLY option to copy the loaded partition you need to the backup system Relative Files with FRNL Step 4 Method 2 With this method you only need to use FRNL to obtain a copy of the specific partition you want and then move the copy to the...

Page 179: ...e of a complete media failure and you do not have a backup copy of the table on tape or in an online dump then you will have to resynchronize the entire table Therefore to prevent this you should have a copy of your backup database on tape or in an online dump The preferred method is to have on online dump because it can be used both for fast synchronization after a media failure on the backup sys...

Page 180: ... Purge the RDF control subvolume and then issue an INITIALIZE RDF command of the following form on the primary system INITIALIZE RDF BACKUPSYSTEM system SYNCHDBTIME ddmmmyyyy hh mm For the timestamp follow the guidelines for the INITTIME option 3 Configure RDF and then issue a START RDF UPDATE OFF command on the primary system 4 Make a copy of your table using one of the following two methods Meth...

Page 181: ...TORE utility with the PARTONLY option to put the loaded primary partition of the duplicate table into the correct location MAP NAMES is not required because the loaded partition now has the correct name on tape and can be restored directly 15 When the extractor has logged the message indicating it has completed its role in the online synchronization operation issue the RDFCOM START UPDATE command ...

Page 182: ...itions onto tape If you created the duplicate table directly on the backup system skip this step 8 If you created the duplicate table on the primary system then use the RESTORE utility to put the entire duplicate table with all its partitions onto disk on the backup system You must use MAP NAMES to correct the system name DATA DUP PART is now on the backup system If you created the duplicate table...

Page 183: ...was generated after the load or backup operation completed At this time the extractor begins building a list of all transactions that might have been started during the create load or backup operation Upon completion of phase 1 part 1 the extractor logs message 766 Phase 1 Part 2 The extractor has reached the next TMP control point record in the audit trail and now has a list of all transactions t...

Page 184: ...nchronization functions Where it resumes however depends upon where it was when the restart condition occurred If the restart condition occurs prior to the start of phase 1 the extractor resumes wherever the receiver tells it to If the restart condition occurs after phase 1 has begun the extractor might choose to resume at an earlier position than the receiver tells it to It does this to ensure th...

Page 185: ...ated entry in the error column is The following sample display shows that the updater process MUP1 for the data volume DATA1 has successfully completed synchronization while the updater process MUP2 for the data volume DATA2 is still doing the synchronization RDF Process Name RTD Time Pri Volume Seqnce Rel Byte Addr Cpus Err Monitor MMON 185 TRAILS 5 2 3 Extractor 0 MEXT 0 00 185 TRAILS 5 7110636 ...

Page 186: ...186 ...

Page 187: ...nds the attributes specify configuration values stored in either The RDF configuration memory table which you access by using the SET RESET and SHOW commands The RDF configuration file which you access through the ADD ALTER and DELETE commands Other attributes request display options or select systems disk volumes files and other objects Many attributes are optional but some are required Where Iss...

Page 188: ...raints and unexpected effects of the command hints on enhancing performance and avoiding errors and other considerations When a command is extremely basic or straightforward the command description omits the Usage Guidelines Table 8 1 Systems for RDFCOM Commands Other Objects Trigger Network RDFNET Volume Update Purger Receiver RDF Monitor Image Trail Extractor P P P P P P P P P P ADD E P P P P P ...

Page 189: ...M Commands Other Objects Trigger Network RDFNET Volume Update Purger Receiver RDF Monitor Image Trail Extractor S S S S S S S S S S ADD S S S S S S S S S ALTER O COPYAUDIT S S S DELETE A EXIT A FC A HELP A HISTORY A A A A A A A A A A A INFO O INITIALIZE X OBEY A OPEN Legend A All users S Super user group only O owner of RDF subsystem Must also have remote password for primary node X Depends on whi...

Page 190: ... appear are explained in Output Displayed Examples Under the heading Examples each command description presents one or more examples showing how the command is used For commands that display information sample output also appears Command entries and other user input appear in bold type RDFCOM output appears in regular type RDFCOM Related Filenames and Process Identifiers File names and process ide...

Page 191: ... volume name consists of a dollar sign followed by one to six alphanumeric characters the first alphanumeric character must be a letter subvol specifies the name of the subvolume on which the file resides A subvolume name has one to eight alphanumeric characters the first character must be a letter filename specifies the name of a permanent disk file A permanent file name consists of one to eight ...

Page 192: ...ation memory table a buffer that serves as a temporary repository for these values You define the parameter settings in this table through the SET command display them with the SHOW command and reset them to their default values with the RESET command RDF assigns default values for any parameter settings that you do not specify The parameter settings in the configuration memory table are reset to ...

Page 193: ...also previously have added the receiver process PURGER applies configuration parameters for the purger RDFNET applies configuration parameters for the RDFNET process NETWORK applies configuration parameters for an RDF network 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 thi...

Page 194: ... backup system To add a secondary image trail you specify the disk volume intended for its use through the ADD IMAGETRAIL command When you configure your individual updater processes with the SET VOLUME command you assign each of these processes to a different image trail reducing the number of updaters contending for a specific trail Each secondary image trail contains only that audit data requir...

Page 195: ...MAPFILE DATA05 CONFIG MAPFILE SET VOLUME MAPLOG DATA05 LOG MAPLOG SET VOLUME UPDATEVOLUME DATA1 SET VOLUME IMAGEVOLUME SECIT1 ADD VOLUME DATA01 The SET VOLUME commands supply only values that pertain to the backup system environment it is not until you issue an ADD VOLUME command that the updater process actually becomes associated with a particular volume on the primary system To define a reverse...

Page 196: ...irm your changes by again entering INFO RDF For using ALTER RDF UPDATEROPEN to coordinate the taking of online dumps or reloads on the backup system see the discussion in Chapter 5 page 121 If you use an ALTER RECEIVER command to change the EXTENTS parameter the change will occur on the next RDF image file rollover unless RDF has never been started since its last reinitialization Although you can ...

Page 197: ...TROLSUBVOL subvol REMOTESYS name specifies the name of the backup system that has the most audit records that was further ahead in its RDF processing REMOTECONTROLSUBVOL subvol specifies the name of the RDF control subvolume on the remote system Where Issued Backup system only the backup system that has the least amount of audit records Security Restrictions You can issue the COPYAUDIT command onl...

Page 198: ...he receiver on C again RDFCOM issues a message to let you know it is doing this RDFCOM must update the context records because it just added new audit records to the image trails and the updaters must have a chance to apply that information upon successful completion of a subsequent required takeover Each updater has an exception file containing information about all of the audit records it could ...

Page 199: ...OL A1 DELETE The DELETE command deletes the entire configuration record for the specified secondary image trail updater process or trigger from the RDF configuration file DELETE IMAGETRAIL volume ATINDEX audittrail index number VOLUME volume volume TRIGGER type IMAGETRAIL volume deletes a secondary image trail from the configuration implicitly identifying that trail by the name of the volume on th...

Page 200: ...OLUME command and then restart RDF When it is convenient to do so you can resynchronize the affected volume configure a new updater process by issuing appropriate SET VOLUME commands and then issue an ADD VOLUME command to restart RDF protection for the affected primary volume Before you can remove an image trail with the DELETE IMAGETRAIL command you must delete all updater processes that are con...

Page 201: ...l to the operating system If the EXIT command appears in a command file RDFCOM stops reading the command file and ignores any commands in the file that follow the EXIT command Furthermore the following applies If the command file name was supplied in the IN option of the command that runs RDFCOM RDFCOM passes control to the operating system If the command file name was supplied in an OBEY command ...

Page 202: ...d you can simply enter the replacement character directly under the character you want to replace 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 want to display the command not change it The FC command is a standard feature of many HP software products For more information about ...

Page 203: ...under the extra character displayed FC SHOW RDDF D SHOW RDF RDF SOFTWARELOC SYSTEM RDF RDF LOGFILE 0 RDF PRIMARYSYSTEM MICKEY RDF UPDATERDELAY 10 RDF UPDATERTXTIME 60 RDF UPDATERRTDWARNING 60 RDF UPDATEROPEN PROTECTED RDF NETWORK OFF RDF NETWORKMASTER OFF RDF UPDATEREXCEPTION ON RDF REPLICATEPURGE OFF RDF OWNER SUPER RDF HELP The HELP command displays explanatory text about RDFCOM commands and RDF...

Page 204: ...ER RDFNET NETWORK TRIGGER trigger type VOLUME volume volume Cannot be performed with RDF running Only a user in the SUPER group can execute this command 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 TRIGGER RDFNET VOLUME DELETE INFO INITIALIZE RESET SHOW S...

Page 205: ...til the primary process can be re created Recovery This is an informational message no recovery is required 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 ...

Page 206: ...1 through 15 specify auxiliary audit trails AUX01 through AUX15 respectively You can use this option only with the EXTRACTOR IMAGETRAIL RECEIVER and VOLUME volume variations of the INFO command For INFO EXTRACTOR INFO IMAGETRAIL and INFO RECEIVER commands the default is 0 If you omit this parameter RDFCOM assumes you want to display information about the designated object associated with the MAT F...

Page 207: ...ameter values for the receiver process RDFNET displays the current configuration parameter values for the RDFNET process NETWORK displays the current configuration parameter values for an RDF network PURGER displays the current configuration parameter values for the purger process TRIGGER trigger type displays the current configuration parameter values for the specified trigger type REVERSE TAKEOV...

Page 208: ...OLUME SANFRAN RDF LOGFILE 0 RDF PRIMARYSYSTEM SANFRAN RDF UPDATERDELAY 10 RDF UPDATERTXTIME 10 RDF UPDATERRTDWARNING 60 RDF UPDATEROPEN PROTECTED RDF NETWORK OFF RDF NETWORKMASTER OFF RDF UPDATEREXCEPTION OFF RDF REPLICATEPURGE OFF MONITOR CPUS 1 2 MONITOR PRIORITY 165 MONITOR PROCESS MON1 EXTRACTOR ATINDEX 0 EXTRACTOR CPUS 2 1 EXTRACTOR PRIORITY 165 EXTRACTOR PROCESS EXT EXTRACTOR RTDWARNING 60 P...

Page 209: ... auxiliary audit trail AUX02 enter the following command INFO EXTRACTOR ATINDEX 2 The output shows that the auxiliary extractor for AUX02 is configured with its default parameter values running in CPUs 2 and 1 with a priority of 165 and with the default RTD warning threshold of 60 seconds EXTRACTOR ATINDEX 2 EXTRACTOR CPUS 2 1 EXTRACTOR PRIORITY 165 EXTRACTOR PROCESS EXT2 EXTRACTOR RTDWARNING 60 I...

Page 210: ...FF RDF REMOTE MIRROR OFF RDF RDF IMPX ZLT The primary system name is set implicitly and the backup system name is set in the INITIALIZE RDF command INFO VOLUME Command Suppose that you configured an updater process named UP1 to back up all changes made to audited files on the primary volume named DATA01 and that the corresponding volume on the backup system is DATA1 Also suppose UP1 was configured...

Page 211: ...splay 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 CPUS 3 2 PURGER PRIORITY 165 PURGER PROCESS PURG PURGER RETAINCOUNT 50 PURGER ...

Page 212: ...he 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 ...

Page 213: ...lization It has the same format as the timestamp parameter described above NOW causes RDF to be initialized at the current date and time To determine the appropriate value to use as the inittime parameter first issue an RDFCOM STATUS RDF command and take note of the highest updater RTD time Then round that RTD time up to the next highest minute internal 0 43 becomes 1 00 1 27 becomes 2 00 3 04 bec...

Page 214: ...DF searches for the specified timestamp TMF shutdown at 12JAN2004 14 30 has been found RDF will start at RBA 376275 MAT file AUDIT ZTMFAT AA000414 Do you still wish to start at this point Y N Enter Y or YES to proceed enter N or NO to cancel the command If you include the INITTIME option without the option RDFCOM displays Do you wish to proceed Y N Enter Y or YES to proceed enter N or NO to cancel...

Page 215: ... INITTIME or SYNCHDBTIME options The INITIALIZE RDF command creates the configuration and context files for establishment of a new RDF configuration After issuing the INITIALIZE RDF command you must build the new configuration by entering the appropriate SET and ADD commands or by executing a command file containing those commands Only then can you issue the START RDF command to start RDF The INIT...

Page 216: ...FCOM sets the context of the extractor to the record following that record When RDF is initialized the contexts of the receiver and all updaters are initialized to the beginning of the first image file AA000001 When RDF is started for the first time after it has been initialized any previously existing image files are purged If you plan to include the TIMESTAMP option in the INITIALIZE RDF command...

Page 217: ...oceed Y N Y Please wait while RDF searches for the specified timestamp TMF shutdown at 12JAN2004 14 30 has been found RDF will start at RBA 376275 MAT file AUDIT ZTMFAT AA000414 Do you still wish to start at this point Y N Y 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 y...

Page 218: ...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 OPEN control subvol cont...

Page 219: ...stems TORONTO and DALLAS identifies TORONTO as the RDF control subvolume for subsequent RDFCOM commands OPEN TORONTO Having issued the above command the next command obtains RDF status information for TORONTO STATUS RDF The following command identifies DALLAS as the RDF control subvolume OPEN DALLAS Having issued the above command the next command requests RDF configuration information for DALLAS ...

Page 220: ...r 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 Examples Suppose that RDFCOM output is currently directed to the terminal at which you are entering commands To temporarily direct an RDF status display to a specific spooler location ...

Page 221: ...SET PURGER SET RDF SET RDFNET SET RDFNETWORK SET RECEIVER SET VOLUME and SET TRIGGER command descriptions Where Issued Primary system only Security Restrictions You can issue the RESET command if you are a member of the super user group RDF State Requirement You can enter the RESET command at any time whether or not RDF has been started Certain constraints however apply to the subsequent ADD comma...

Page 222: ...s a process pair on the primary system primary CPU is the primary CPU backup CPU is the backup CPU Values range from 0 through 15 The defaults are 0 1 PRIORITY priority identifies the execution priority for the extractor process priority is the execution priority from 10 through 199 The default priority is 165 PROCESS process name identifies the process name for the extractor process process name ...

Page 223: ... match the audit trail number of a configured auxiliary audit trail If you specify SET EXTRACTOR ATINDEX 2 for example there must be a configured auxiliary audit trail AUX02 Furthermore RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set If there is an extractor with an ATINDEX value of 1 there must also be a receiver with an ATINDEX value of 1 If the...

Page 224: ...e The default value is 0 For information about protecting auxiliary audit trails see Chapter 13 page 291 Usage Guidelines For ATINDEX values greater than 0 the specified value must match the audit trail number of a configured auxiliary audit trail If you specify SET IMAGETRAIL ATINDEX 2 for example there must be a configured auxiliary audit trail AUX02 Furthermore RDF objects with a particular ATI...

Page 225: ...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 Example To configure a monitor process named MON1 to run in CPUs 0 and 1 at a priority of 180 issue the following commands ...

Page 226: ...d so these values do not affect the subsystem until they are applied to the RDF configuration file with the ADD command Example To configure the primary system RDF04 and backup system RDF06 issue the following commands after RDF has been initialized SET NETWORK PRIMARYSYSTEM RDF04 SET NETWORK BACKUPSYSTEM RDF06 SET NETWORK REMOTECONTROLSUBVOLUME RDF04 SET NETWORK PNETTXVOLUME DATA07 ADD NETWORK SE...

Page 227: ...re relatively small such that the audit record at MAT 10 100000010 was placed at the start of image trail file AA000025 on B If the purger on B is allowed to purge AA000025 before the takeovers occur the triple contingency protocol will fail because C is missing some of the purged audit records Sno 10 RBA 100000010 through Sno 10 RBA 100500000 The RETAINCOUNT parameter is designed to prevent such ...

Page 228: ...ble 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 Example To configure a purger process named PRG to run in CPUs 0 and 1 with a RETAINCOUNT of 8 issue these commands SET PURGER PROCESS PRG SET PURGER CPUS 0 1 SET PURGER RETAINCOUNT 8 ADD PURGER By default in this example the purger process wi...

Page 229: ...activity aggregate updater throughput greater than 300 kb second Raising the tx time in such environments could adversely affect TMF performance on the backup system In RDF environments with low to moderate updater activity and where no other transaction activity is occurring on the backup system you could raise the tx time without affecting TMF performance on the backup system UPDATERRTDWARNING r...

Page 230: ...minimum logging necessary to support Triple Contingency operation LOCKSTEPVOL volume specifies the primary system disk volume on which the RDF lockstep file ZRDFLKSP control subvolume 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 l...

Page 231: ...sers By default this attribute is not set and therefore is not included in the INFO RDF output The userid associated with OWNER must be a valid Guardian userid and must identify an existing user account on the RDF primary and backup systems The OWNER must also be a member of the super user group which is a requirement in RDF for stopping and starting RDF OWNER is an unalterable value You need not ...

Page 232: ...ate Requirements None 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 Example To configure a RDFNET process named MNET to ru...

Page 233: ...ocess will receive error 43 messages Unable to obtain disk space for extent from the file system until the situation is corrected PRIORITY priority identifies the execution priority for the receiver process priority is the execution priority from 10 through 199 The default is 165 PROCESS process name specifies the process name for the receiver process process name is any unique valid process name ...

Page 234: ...nfigured auxiliary audit trail AUX02 Furthermore RDF objects with a particular ATINDEX value greater than 0 must together constitute a complete set 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 An updater with an ATINDEX va...

Page 235: ...ironment must be empty before the STOP RDF REVERSE is issued If it is not empty RDF will not be able to initialize and the reverse environment cannot be started infile is the name of an edit file that will be passed as the IN file to the trigger process when it is created infile must be a properly formed Guardian disk file name The file does not have to exist This parameter is mandatory outfile is...

Page 236: ...STEM TACL SET TRIGGER CPUS 3 4 SET TRIGGER PRIORITY 160 SET TRIGGER NOWAIT ADD TRIGGER TAKEOVER The RDF configuration on RIGHT is contained in the file RIGHT DATA01 RDFCONF RIGHT specified in the INFILE That file includes these commands the standard SET ADD RDF EXTRACTOR RECEIVER PURGER IMAGETRAIL and VOLUME configuration commands are omitted INITIALIZE RDF BACKUPSYSTEM LEFT INITTIME NOW START RDF...

Page 237: ...olume 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 UPDATEVOLUME volume specifies what volume on the backup system will...

Page 238: ...INDEX 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 An updater with an ATINDEX value of 1 must be protecting a primary system data volume configured to auxiliary audit trail AUX01 and its secondary image trail must also have an ATINDEX value of 1 For a discussion on the use of INCLUDE and EXCLUDE lists see Chapter 11 pa...

Page 239: ...her volume on the primary system is named DATA02 and you want to create an updater process named U02 to replicate changes to only those tables and files on DATA02 whose subvolume name begins with OEM2 or OEM5 To configure the updater process to run in CPUs 5 and 6 at the default priority of 160 using secondary image trail volume SECIT2 and data volume DATA2 on the backup system issue these command...

Page 240: ...es information from the RDF configuration memory table which serves as an input buffer for a subsequent ADD command If you have not yet issued any SET commands for the specified object or have issued a RESET command for it the SHOW command displays the default option values for the object If you want to see what parameter values are already set in the configuration file use the INFO command Output...

Page 241: ...GE RECEIVER FASTUPDATEMODE OFF RECEIVER PROCESS REC RDFCOM includes the line containing PROCESS process name in the display only if the process name was specified in a SET command SHOW PURGER Command Suppose that a series of SET PURGER commands specifies that a purger process named PURG is to run in CPUs 3 and 2 at priority 165 with a RETAINCOUNT of 50 To display the values specified by those SET ...

Page 242: ...NFO RDFNET RDF displays RDFNET PROCESS MNET RDFNET CPUS 0 1 RDFNET PRIORITY 180 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 To display the values specified by those SET...

Page 243: ...e started and transactions enabled on both primary and backup systems before you issue the START RDF command When RDF starts it automatically executes an implicit VALIDATE CONFIGURATION command with these results If any parameter value in the RDF configuration file is invalid RDFCOM displays an error message and the START RDF operation fails If all of the parameters in the RDF configuration file a...

Page 244: ... database Example To initiate updating on the backup system of all volumes protected by RDF enter START UPDATE STATUS The STATUS command displays current configuration information and operational statistics for the RDF environment or specified portions thereof All forms of the STATUS command except STATUS RTDWARNING automatically include information and statistics for the monitor process STATUS MO...

Page 245: ...T repeat option but include the PERIOD seconds option the command is executed repeatedly at the specified time intervals until you press the BREAK key Where Issued Primary or backup system Security Restrictions None anyone can enter a STATUS command RDF State Requirement You can enter a STATUS command at any time after RDF has been initialized Usage Guidelines The STATUS command provides you with ...

Page 246: ...ith Update On and the second example the state indicates that an RDF takeover operation has begun The following list represents all possible RDF states For a discussion of each of these states see Displaying Current Operating Statistics and Configuration Information page 112 in Chapter 4 Normal Normal Update Stopped Start Update Pending Stop Update Pending Stop Update Timestamp Pending STOP RDF In...

Page 247: ... behind the application program each process is running Please note that an RTD time is not a precise indication of how far an RDF process is behind An RTD time is only relative and is an approximation The more accurate RTD time is that of the extractor An updater s RTD is even more relative because it may show 20 seconds one instance and then show 0 seconds in the next instance The reason for thi...

Page 248: ...RCV0 writes image records for updater RUPD1 to IMAGE0 RRCV1 writes image records for updaters RUPD2 and RUPD3 to IMAGEA1 in this example Each updater entry reflects the name of the secondary image file from which it is reading DATA03 RDF04 AA000020 for RU01 DATA04 RDF04 AA000003 for RU02 and DATA05 RDF04 AA000003 for RU03 in this example If RDFCOM cannot connect to a particular process RDFCOM disp...

Page 249: ...back out any updates for transactions that need to be undone In a takeover operation for an RDF network undo indicates the first undo pass when local transactions are undone because their outcomes are unknown net During an RDF network takeover operation there are three possible undo phases local undo marked undo as stated above file undo not marked because this highly rare and typically only lasts...

Page 250: ...ng that all updaters have stopped and the drain has completed REVERSE causes RDF to replicate all audit records up to the time the command was issued then run the configured reverse trigger program You must stop all transaction activity on the primary system before issuing the STOP RDF REVERSE command If there is active transaction activity on the RDF protected database the database could lose int...

Page 251: ...s closed and is in the same state as if TMF was stopped See Critical Operations Special Situations and Error Conditions page 121 for a discussion on how this operation may be of value to you For information about when to use the STOP RDF command and how it affects the primary and backup databases see Stopping RDF page 132 There are three ways to stop RDF Issue a STOP TMF command at the primary sys...

Page 252: ...he related discussion in Critical Operations Special Situations and Error Conditions page 121 RDF must be running in the Normal state with Update On to issue a STOP RDF DRAIN or STOP RDF REVERSE command In addition entering either command under any of these conditions results in an error on the backup system while RDF is stopping due to a stop TMF while a stop update to timestamp operation is pend...

Page 253: ...ror message appears Additionally all transactions that committed prior to the timestamp are applied and retained in the backup database Any transactions that committed at or after the specified timestamp are backed out of the backup database When you subsequently restart Update any transactions undone during the previous stop update to time operation are reapplied to the backup database thereby ke...

Page 254: ...date to time operation typically includes an undo pass to back out any updates the updaters may have applied for transactions that did not commit by the specified timestamp Any transactions backed out are reapplied when you issue the next START UPDATE command If you issue the STOP UPDATE command without the TIMESTAMP option the RDFCOM prompt is not returned until all updaters have stopped If you i...

Page 255: ...primary system fails or otherwise becomes unavailable and you want to make the backup database your new database of record for your applications CAUTION The TAKEOVER command is not a normal operational command Operators should never issue this command strictly on their own initiative Issue this command only when specifically told to do so by someone in high authority For a thorough discussion of a...

Page 256: ... your primary system that did a large number of updaters at the time the primary system failed then all of these need to be undone by the updaters if UPDATEREXCEPTION is ON then each update of the batch needs to be undone and an exception record written Auxiliary Audit and a Comm Problem If your RDF environment includes extractor receiver pairs associated with auxiliary audit trails then if one ex...

Page 257: ...ssumes a disaster on SANFRAN has occurred Are you sure you want to TAKEOVER To proceed with the TAKEOVER operation enter Y or YES To stop the TAKEOVER operation enter N or NO After you enter your response RDFCOM prompts you for your next command 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 oper...

Page 258: ...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 Example To unpin TMF audit trail files on the primary system enter UNPINAUDIT VALIDATE CONFIGURATION The VALIDATE CONFIGURAT...

Page 259: ...mes for the image files have enough room for two more image files for an RDF restart The primary volumes associated with the updater processes are valid and are being audited to the TMF audit trail The backup volume associated with each updater process specified by the UPDATEVOLUME option of the SET VOLUME command exists on the backup system Mapping strings specified in the mapfiles of all the upd...

Page 260: ...260 ...

Page 261: ... file At configuration time you can either Supply the name of the desired collector in a SET RDF LOGFILE command and add it to the configuration file with an ADD RDF command Let RDF use 0 by default At any later time you can change the collector specified in the configuration file by entering an ALTER RDF LOGFILE command You can use RDFSCAN to examine the RDF messages in the EMS log by way of an i...

Page 262: ... Usage Guidelines Messages generated by RDF are written to an EMS event log The AT command specifies the starting point in the intermediate entry sequenced file generated by the RDFFLTO filter where the LIST and SCAN commands used to examine these messages begin their operations If you enter the AT command without the record number RDFSCAN prompts you Enter record number Examples Suppose that SYST...

Page 263: ...d number 2948 2004 06 11 16 10 01 LAB1 RDFCOM 835 STOP UPDATE Record number 2949 2004 06 11 16 10 06 LAB1 ZRDF 808 Update mode has been set OFF Record number 2950 2004 06 11 16 49 56 LAB1 RDFCOM 835 STOP RDF File SYSTEM SANFRAN RDFLOG current record 2951 last record 2955 Enter the next RDFscan function you want If you issue a LIST 4 command only without setting the display feature on RDFSCAN displ...

Page 264: ...sion is currently accessing In fact you can use the FILE command to specify any entry sequenced file When you issue the FILE command RDFSCAN identifies the file specified as the one to which subsequent AT DISPLAY LIST MATCH and SCAN commands in this session apply the target file for these commands This file remains the target file until you specify a new target in a later FILE command or until you...

Page 265: ...displayed via LIST If filename does not exist an EDIT file is created for you File SYSTEM SANFRAN RDFLOG current record 9454 last record 9466 Enter the next RDFSCAN function you want 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 r...

Page 266: ...5 Pattern AU02 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 ...

Page 267: ...OG issue a NOLOG command 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 examin...

Page 268: ...nter the next RDFSCAN function you want MATCH LOG FILE File SYSTEM SANFRAN RDFLOG current record 6454 last record 9466 Pattern LOG FILE Enter the next RDFSCAN function you want AT 1000 File SYSTEM SANFRAN RDFLOG current record 1000 last record 9466 Pattern LOG FILE Enter the next RDFSCAN function you want LIST 5 Record number 1134 2004 06 04 11 31 50 LAB2 Z048 709 Log File Opened or Altered SYSTEM...

Page 269: ...essages starting at the current record This behavior is identical to using the LIST command with pattern matching disabled NOTE The SCAN command performs a slightly different operation than the LIST command when pattern matching is enabled For example If you specify SCAN 10 RDFSCAN searches the next 10 records for the currently specified pattern and displays all records from among those 10 in whic...

Page 270: ...u want SCAN 1000 Record number 1011 2004 06 08 04 13 49 LAB1 AU02 790 Backup Process Created in Processor 03 Record number 1342 2004 06 08 04 13 49 LAB1 AU02 718 Switched to original Primary Processor Record number 1792 2004 06 08 05 01 35 LAB1 AU02 790 Backup Process Created in Processor 03 Record number 1933 2004 06 08 05 01 35 LAB1 AU02 718 Switched to original Primary Processor File SYSTEM SAN...

Page 271: ... release of RDF on all three systems All protected data volumes in both RDF environments must be mapped to the Master Audit Trail MAT of the associated primary system It is recommended but not required that the two backup systems have the same hardware configuration They must however have the same data volumes and image trails The two RDF configurations must be configured identically with a few mi...

Page 272: ...mperative that you carefully obey the instructions and caveats presented in this chapter Hardware Requirements Both backup systems should have similar hardware with respect to RDF operation in particular the data volumes and image trails must be identical between the two systems It is also strongly recommended that the Expand bandwidth between the primary and backup systems be the same for both co...

Page 273: ...ssing on C Suppose that the image trail files are relatively small such that the audit record at MAT 10 RBA 100000010 was placed at the start of image trail file AA000025 on B If the purger on B is allowed to purge AA000025 before the takeovers occur the triple contingency protocol will fail because C is missing some of the purged audit records Sno 10 RBA 100000010 through Sno 10 RBA 100500000 The...

Page 274: ...mmand copies missing audit records from the backup system that was further ahead in its RDF processing had the most amount of audit data to the system that was further behind had the least amount of audit data Upon successful completion of the two takeovers examine the EMS event log on both backup systems for a 735 message That message which follows the 724 message in the log specifies the last po...

Page 275: ...DF on both systems and then resume application processing on the new primary system with full RDF protection COPYAUDIT Restartability The COPYAUDIT command is restartable If an error condition aborts execution of a COPYAUDIT command you merely correct the condition and then reissue the command Upon restart RDFCOM quickly checks the local system image files it had previously created to be sure they...

Page 276: ...g system A Using ZLT to Achieve the same Protection While the COPYAUDIT command does not work for RDF configurations that include auxiliary audit you can achieve Triple Contingency with auxiliary audit by using the ZRDF ZLT product because the ZLT functionality supports auxiliary audit To achieve the same result using the RDF ZLT product you configure system B as the ZLT standby node for both RDF ...

Page 277: ...the backup systems it must be the same on both Upon loss of the primary system you must 1 Issue a TAKEOVER command on both backup systems 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 records 3 On the system with the least amount of audit records issue a COPYAUDIT command specifying the...

Page 278: ...278 ...

Page 279: ...CLUDE clauses require the use of Guardian names If you have an ANSI named NonStop SQL MX object that you want to include or exclude you must first obtain the underlying Guardian name by using the MXGNAMES utility or the MXCI SHOWDDL command as described in Chapter 16 page 323 INCLUDE Clauses INCLUDE clauses explicitly designate those subvolumes files and tables residing on a particular primary sys...

Page 280: ... are also stored in the in memory table too This can make using the same INCLUDE and EXCLUDE lists for each volume very convenient because you only have to specify them for the first volume and they are carried over to each subsequent volume that you add for RDF protection For example consider the following SET VOLUME CPUS 1 2 SET VOLUME IMAGEVOLUME IMAGE SET VOLUME PRIORITY 185 SET VOLUME PROCESS...

Page 281: ...E with the exact same wildcard functionality and with the exact same performance ramifications There is one additional consideration The total number of INCLUDE EXCLUDE INCLUDEPURGE and EXCLUDEPURGE clauses that you can have for one updater is 100 This means for example that you can have 25 for each of the these clauses but not one more If you have 50 INCLUDEs and 50 EXCLUDEs then you cannot add a...

Page 282: ...he extractor must also test the subvolume name and filename Hence there is more work to do with subvolume and file level replication If you use large numbers of INCLUDE and EXCLUDE clauses for each volume the extractor might have to evaluate the subvolume name and filename against multiple lists which could lead to increased CPU usage by the extractor and lower extractor performance than with simp...

Page 283: ...ry system to DATA01 on the backup system but the INCLUDE and EXCLUDE clauses explicitly identify which subvolumes and files on PRIMARY DATA01 are to be replicated all audited files and tables in the subvolumes MMTEST10 DATA and DB are replicated except MMTEST10 CONC0826 and any files or tables in DATA whose names start with C Summary Examples 283 ...

Page 284: ...284 ...

Page 285: ...ame Mapping for Partitioned Files page 288 For more information about the problems associated with using differently named subvolumes see Managing Subvolume Name Mapping for Partitioned Files page 288 Creating a Mapfile to Define the Rules for Subvolume Name Mapping You define subvolume name mapping in a mapfile The mapfile is an EDIT file that contains the supported subvolume mapping strings whic...

Page 286: ...DF events and RDFCOM error messages see RDF Messages page 365 and RDFCOM Messages page 413 Examples of valid mapping strings include MAP NAMES HISSTUFF TO TEST10 MAP NAMES HERSTUFF TO TEST11 MAP NAMES THEIR TO TEST12 Examples of invalid mapping strings including disallowed reserved words are MAP NAMES TEST TO TEST MAP NAMES TEST1 TO TEST MAP NAMES TEST1 TO TEST2 MAP NAMES DATA01 TEST TO DATA02 TES...

Page 287: ...ation filenames on the backup system The updater logs the entry of the data file only once until the time that the data file is open on the backup system However if the data file is closed and reopened on the backup system the updater logs multiple entries for the same data file If the maplog file already exists at the cold start it will be emptied with a Purgedata operation If the maplog does not...

Page 288: ... mapfile is not edited or modified by the user since the updater was last stopped Compares the last modification timestamp and CRVSN number of the mapfile with those stored in its configuration record If they match the updater reads all the mapping strings from the mapfile and skips their validation If they do not match the updater performs validation of all the mapping strings and generates the a...

Page 289: ...MES SVOL TO SVOL2 As a result of these mapping rules both partitions on the backup system are created in the same subvolume SVOL1 When the second updater applies an audit to the secondary partition DATA22 SVOL2 FILE it reports an error 11 because the partition DATA22 SVOL2 FILE does not exist If you run FUP COPY on the primary partition file DATA02 SVOL1 FILE on the backup system FUP reports file ...

Page 290: ...290 ...

Page 291: ...mple assume that DATA1 on the primary system is configured as a data volume in auxiliary audit trail AUX01 and an auxiliary extractor is configured for AUX01 The auxiliary extractor sends all audit records for DATA1 to a corresponding auxiliary receiver on the backup system The receiver writes the data to an image trail that is in turn read and processed by an updater responsible for replicating d...

Page 292: ...nteger 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 1 through 15 specifies auxiliary audit trail AUX01 through AUX15 respectively and the data volume on the primary system must be mapped to the designated auxiliary audit trail The default value is ...

Page 293: ... audit trail Using Expand Multi CPU Paths The use of Expand with ATM Fast Ethernet or Servenet provides considerable bandwidth and it is often sufficient to have a single Expand path driven out of a single processor If your RDF configuration is replicating auxiliary audit trails however the total amount of audit data to be sent from the primary system to the backup system could be more than a sing...

Page 294: ...For more information about Expand multi CPU paths see the Expand Configuration and Management Manual 294 Auxiliary Audit Trails ...

Page 295: ...ce all application activity both local and remote so that no further database updates are being performed and then bring down the communication lines between the primary and backup systems before initiating the takeover With network transaction support you must now be more careful when creating Enscribe files that have alternate key files Specifically when you create an Enscribe file with an altke...

Page 296: ...me REMOTECONTROLSUBVOL subvolume name Name of the primary system volume on which the RDF subsystem stores an audited network synchronization file PNETTXVOLUME volume name If you are configuring a non network master RDF subsystem you must include a single network configuration record containing these attributes Name of the network master s primary system PRIMARYSYSTEM system name Name of the networ...

Page 297: ...nly 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 The process does that by updating an audited file named ZRDFNETX on the primary system of each RDF subsystem in the RDF network The overhead of this process should be transparent because the RDFNET process only starts a single transacti...

Page 298: ...d ten updates and you committed the transaction but the extractor process was only able to transmit the first five updates to the backup system before being terminated by an unplanned outage In such a case the RDF subsystem recognizes it is missing data for the particular transaction because it does not know how the transaction ended and it undoes the five updates it had previously applied to the ...

Page 299: ...t behind will have to go through 60 minutes of data to determine what must be undone due to data missing on the system that had fallen behind A variation of the first example is that no extractors have fallen behind but you have 25 systems in your RDF network In such a case phase 3 processing might take many additional seconds because data must be checked for so many different systems in order to ...

Page 300: ...database To do so you merely execute a planned RDF switchover from the backup to the newly restored primary The problem with doing a planned switchover from backup to primary after an RDF takeover operation is that some transactions might have committed on the primary system immediately prior to the unplanned outage and the outage brought down the extractor before it could send that data to the ba...

Page 301: ...tion was active on both A and B when B went down Therefore even though T12 originated on A and was committed on A it must be undone on X the backup system of A because it was undone on Y the backup system of B This ensures database consistency across both nodes When the purger identifies the first network transaction that must be undone during network undo processing it logs an RDF 877 event messa...

Page 302: ...12 and T13 did indeed commit Therefore although the commit record for T12 is missing from B the commit record for T13 is present This guarantees that T13 committed prior to T12 and that the results of T13 can be kept intact on both nodes When a purger determines that it can keep the results of a transaction even though that transaction follows one that must be undone because data for it is missing...

Page 303: ...Because you cannot validate the network master until all non network master subsystems have been validated you cannot start the network master until all non network master subsystems have been validated 3 If you have validated a non network master you are allowed to start that subsystem even though the network master has not been validated See Appendix C page 365 for the error messages that can oc...

Page 304: ...ing check the communication lines to the other systems in the network If one of them is down and the RDFNET process is tying up the orderly shutdown of RDF stop the RDFNET process manually CAUTION If you stop any RDF subsystem in an RDF network you could lose large amounts of committed data in the event of an unplanned outage RDF Networks and Stop Update to Time Operations Stop update to time oper...

Page 305: ...TER ON SET RDF UPDATEREXCEPTION OFF ADD RDF SET MONITOR CPUS 1 2 SET MONITOR PRIORITY 185 SET MONITOR PROCESS MMON ADD MONITOR SET EXTRACTOR ATINDEX 0 SET EXTRACTOR CPUS 1 2 SET EXTRACTOR PRIORITY 185 SET EXTRACTOR PROCESS MEX1 SET EXTRACTOR RTDWARNING 60 ADD EXTRACTOR SET RECEIVER ATINDEX 0 SET RECEIVER CPUS 3 2 SET RECEIVER EXTENTS 100 100 SET RECEIVER PRIORITY 185 SET RECEIVER RDFVOLUME DATA11 ...

Page 306: ... RDF UPDATERTXTIME 60 SET RDF UPDATERRTDWARNING 60 SET RDF UPDATEROPEN PROTECTED SET RDF NETWORK ON SET RDF NETWORKMASTER OFF SET RDF UPDATEREXCEPTION OFF ADD RDF SET MONITOR CPUS 1 2 SET MONITOR 185 SET MONITOR PROCESS MMON ADD MONITOR SET EXTRACTOR ATINDEX 0 SET EXTRACTOR CPUS 1 2 SET EXTRACTOR PRIORITY 185 SET EXTRACTOR PROCESS MEX1 SET EXTRACTOR RTDWARNING 60 ADD EXTRACTOR SET RECEIVER ATINDEX...

Page 307: ...Hewlett Packard Development Company L P Status of RDF04 RDF05 RDF 2008 08 11 05 26 49 082 Control Subvol SYSTEM RDF04 Current State Normal RDF Process Name RTD Time Pri Volume Seqnce Rel Byte Addr Cpus Err Monitor RMON 185 AUDIT 56 1 2 Extractor 0 REXT0 0 00 185 AUDIT 56 928000 1 2 Extractor 1 REXT1 0 00 185 DATA17 4 10435580 1 2 Receiver 0 RRCV0 0 00 185 MIT 44 1 2 Receiver 1 RRCV1 0 00 185 1 2 I...

Page 308: ...308 ...

Page 309: ...although the business transaction is actually committed on the primary system and the file locks or table locks are released the process cannot continue processing until all of the audit data associated with that transaction is safely stored in the image trails on the backup system While the process waits until DoLockstep completes other processes can view and modify the just changed records and t...

Page 310: ...le FDOLOCK For example include these lines of code where you add procedure declarations LIST NOLIST SOURCE EXTDECS LIST NOLIST SOURCE FDOLOCK LIST 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 ...

Page 311: ...kstep transaction all audit records associated with your business transaction are guaranteed to be flushed in the audit trail on the primary system before any lockstep audit is generated Therefore when the lockstep audit is safely in the image trail on the backup system you are also guaranteed to have all audit records of your business transaction safely in the image trail as well because your bus...

Page 312: ... or tables on volumes that are configured to auxiliary audit trails In such a case the lockstep protocol behaves exactly as it would if all volumes were configured to the MAT Remember however that you must still configure an RDF lockstep volume for the lockstep file and this volume must be configured to the MAT The Lockstep Gateway Process The RDF lockstep gateway process is managed by the Subsyst...

Page 313: ...uppose that the communications lines have been down for so long that your applications are getting no work done at all In such a case you might 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 If you should subsequently lose th...

Page 314: ...pter 8 page 187 1 I O completed on an unknown file number Cause While reading RECEIVE the lockstep gateway received an I O completion on an unknown file number Effect The lockstep gateway stops Recovery This is an internal error but the gateway is restarted If the problem persists contact the Global Mission Critical Solution Center GMCSC or your service provider 2 A STARTUPMSG argument is missing ...

Page 315: ...tep operations Effect The lockstep gateway stops Recovery If you want to perform RDF lockstep operations you must be sure you have the correct version of the RDF product and you must be sure you have configured your RDF subsystem for lockstep operation 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...

Page 316: ...0 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 1 1 Lockstep file filename is not audited filename is ...

Page 317: ...nal error unless the gateway stops If it stops correct the condition that caused the error and then restart the gateway 15 Read error errnum on RECEIVE errnum is a file system error number Cause The lockstep gateway received the specified error when reading RECEIVE Effect The lockstep gateway stops Recovery This is an internal error but the gateway is restarted If the problem persists contact the ...

Page 318: ...cript 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 The specified error was returned when the lockstep gateway attempted to obtain information about itself Effect The lockstep gateway stops Recovery This is an internal error but the gateway ...

Page 319: ...hat caused the error and then restart the gateway 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 If the proble...

Page 320: ...as encountered on a lockstep transaction 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 If it stops correct the condition that caused the error and then restart the gateway 30 ENDTRANSACTION error errnum encountered on lockstep transaction errnum is a file s...

Page 321: ...g the lockstep gateway the STARTUPMSG attribute contained an extra or unrecognizable argument Effect The lockstep gateway stops Recovery The STARTUPMSG attribute must include exactly two arguments the word ENABLE or DISABLE and a valid RDF extractor process name all enclosed in quotes Correct the STARTUPMSG attribute script and then manually delete the RDF lockstep gateway process from SCF and run...

Page 322: ...322 ...

Page 323: ...tem data volume are replicated to an associated backup system data volume RDF also supports subvolume and file level replication To use this capability you use INCLUDE and EXCLUDE clauses when configuring updaters to identify specific database objects you want replicated or not replicated INCLUDE and EXCLUDE clauses require the use of Guardian names If you have an ANSI named NonStop SQL MX object ...

Page 324: ...ZSD and the entire name must be eight characters in length For example if issued on the primary system this command without a LOCATION clause creates a schema called PCAT SCH on the primary system CREATE SCHEMA PCAT SCH If you omit the LOCATION clause then after creating the schema you must use this query to obtain the subvolume of the schema where you fill in the correct node name schema name and...

Page 325: ...name for the object using The volume you specified for the object in the LOCATION clause The subvolume associated with the object s ANSI schema as indicated in that portion of the object s ANSI name The system generated Guardian filename In this case you must obtain the underlying Guardian filename using SHOWDDL or a metadata query before you can set up your backup database Now the full CREATE TAB...

Page 326: ...2 When you have completed Steps 6 and 7 for each table and index the primary database is ready for transaction activity and the backup database is ready for RDF to replicate that transaction activity Creating a NonStop SQL MX Backup Database From an Existing Primary Database To create an RDF backup NonStop SQL MX database from an existing primary database perform these steps 1 Create a catalog on ...

Page 327: ...volume names manually by editing this file LOCATION PNODE DATA01 ZSDABCDEF FILE100 TO BNODE DATA0A ZSDABCDEF FILE100 PNODE DATA02 ZSDABCDEF FILE100 TO BNODE DATA0B ZSDABCDEF FILE100 PNODE DATA03 ZSDABCDEF FILE100 TO BNODE DATA0C ZSDABCDEF FILE100 You can generate one such location file for each table or a single file in one MXGNAMES command by providing an input list of NonStop SQL MX names The in...

Page 328: ... or creating the fuzzy copy on the backup system Please note however that the method of taking an online dump and then the use of TMF File Recovery to a New Location FRNL is an alternative to getting a fuzzy copy than the method below and this is discussed in Chapter 7 Creating the Fuzzy Copy on the Primary System The advantage of this method is that in creating and populating the fuzzy copy on th...

Page 329: ...f you want each catalog to be seen from both systems register your primary and backup catalogs To register the primary catalog on the backup system issue a REGISTER CATALOG command on the primary system To register the backup catalog on the primary system issue a REGISTER CATALOG command on the backup system The format of the REGISTER CATALOG command is REGISTER CATALOG catalog ON node volume Wher...

Page 330: ... system that you want replicated 5 Create each object on the backup system See Creating NonStop SQL MX Primary and Backup Databases page 323 6 Determine where you will run the command to load the data from the primary objects to the backup objects If you run the command on the primary system NonStop SQL MX selects the data locally and inserts over the network into the backup object Alternatively y...

Page 331: ...nt synchronized into the temporary partition INSERT INTO backup table SELECT FROM primary table WHERE key column F AND key column K 5 Use Backup to put the temporary table on tape 6 Create a catalog on the backup system to correspond to the temporary catalog on the primary system 7 Create the schema on the backup system using the same schema name and the same subvolume name as the schema for the t...

Page 332: ...clause Alternatively you can drop the entire catalog and then recreate it and all dependent schemas and objects Primary and Backup ANSI Schema Names Are 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 tha...

Page 333: ...re created If you have never added any additional columns to your primary table after it was created use the CREATE LIKE statement Of course you must have registered your catalogs first See Creating NonStop SQL MX Primary and Backup Databases page 323 for instructions If you have added columns to your primary table after it was created you must take particular care when creating the backup table a...

Page 334: ...FGHIJ00 P data03 ZSDBBBBB DEFGHI00 PCAT MYSCHEMAX MYTABLE2 PCAT MYSCHEMAX MYINDEX2 2 The RESTORE command would be RESTORE tape MX TBL PCAT MYSCHEMA MYTABLE1 TGT CATALOG BCAT TBL PCAT MYSCHEMA MYTABLE2 TGT CATALOG BCAT TBL PCAT MYSCHEMX MYTABLE1 TGT CATALOG BCAT TBL PCAT MYSCHEMX MYTABLE2 TGT CATALOG BCAT LOCATION P data01 ZSDAAAAA HEBFRW00 TO B data01 ZSDAAAAA HEBFRW00 P data02 ZSDAAAAA HEBFRX00 T...

Page 335: ...ble on your primary against a NonStop SQL MX table on your backup system for example one method of doing so is as follows 1 Use the NonStop SQL MX Select statement to select all rows in the primary table and then store them in an Enscribe entry sequenced file 2 Use the NonStop SQL MX Select statement to select all rows in the backup table and then store them in another Enscribe entry sequenced fil...

Page 336: ...336 ...

Page 337: ...nd the TMF Reference Manual If all of the remote mirrors are functioning ZLT functionality has no impact on normal RDF operations If you must perform an RDF takeover operation however there are additional steps involved that can lengthen the time to perform the overall operation In return you get the ZLT guarantee of not losing any transactions that committed on the primary system When CommitHoldM...

Page 338: ...andby and backup systems and the remote mirror is located at an intermediate site Figure 17 2 ZLT Configuration With a Single Standby Backup System and With the Remote Mirror Located at an Intermediate Site Figure 17 3 shows the configuration where individual standby and backup systems are located at separate sites 338 Zero Lost Transactions ZLT ...

Page 339: ...re generated on the primary system prior to the system failure and no committed data is lost NOTE You must connect the remote mirrors to the standby system before starting the RDF takeover operation otherwise the takeover aborts because RDF cannot find the disks you configured in RDF for remote mirroring In such a case you should connect the disks and then restart the RDF takeover operation If you...

Page 340: ...nsaction processing If ZLT protection is critical to your disaster recovery plan specify ON TIMEOUT CRASH Crashing TMF under these circumstances provides ZLT protection If it is important to resume transaction processing on the primary system specify ON TIMEOUT SUSPEND Suspending commit hold mode under these circumstances however deprives you of ZLT protection should you lose the primary system to...

Page 341: ...ndby system name is SET RDF REMOTE STANDBY node name node name must be a valid name and must identify a system in your current Expand network If you set the standby to a different node than your backup system the specified system must be accessible to the backup system RDF Configuration Record Validation When you ADD the RDF configuration record these checks are performed If you set the RDF REMOTE...

Page 342: ...RROR configuration attribute off on the primary system so that if you need to execute a takeover operation you can complete the takeover as quickly as possible Remember if you have the RDF REMOTE MIRROR configuration attribute turned off at the time of a takeover you do not have ZLT protection When the troublesome mirror comes back up and is fully revived so that it is current with the local mirro...

Page 343: ...ers are required for the audit fixup process The audit fixup process runs in the same CPU as the extractor primary process with a process priority one less than the extractor priority Phase 2 Takeover Processing The initial part of Phase 2 takeover processing is performed by the purger in building the undo lists When an updater reaches the end of file of its image trail it asks the purger for an u...

Page 344: ...tion completes you should not purge the old audit trail files on the remote mirrors connected to the standby system if you believe you can recover the primary system The old audit trail files are necessary for recovering the primary system If you can t recover the primary system you might purge the files because they have no further use Because the old audit trail files are not managed by TMF on t...

Page 345: ...255 255 gggg 3840 3840 aa000004 134 125808640 01feb2005 10 31 255 255 gggg 3840 3840 aa000005 134 125829120 01feb2005 10 38 255 255 gggg 3840 3840 aa000006 134 125829120 01feb2005 10 45 255 255 gggg 3840 3840 aa000007 134 125829120 01feb2005 10 54 255 255 gggg 3840 3840 aa000008 134 125829120 01feb2005 11 04 255 255 gggg 3840 3840 aa000009 134 125829120 01feb2005 11 14 255 255 gggg 3840 3840 aa000...

Page 346: ...ying Out a Planned Switchover page 136 ZLT and RDF Networks If you have an RDF network and also want ZLT protection on any of the nodes in that network then every node that participates in a user transaction must be configured for ZLT protection For example assume that systems A and B are both configured as nodes within an RDF network and that system B is also configured for ZLT protection If syst...

Page 347: ...T 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 SQL Shared Access DDL Operations 347 ...

Page 348: ...348 ...

Page 349: ...mand interpreter to the NonStop operating system The RDFCOM command starts a session that lets you enter RDFCOM commands interactively noninteractively or through a command file Where issued primary or backup system Security Any user RDFCOM IN command file OUT output file control subvolume command command For more detailed information about RDFCOM commands see Chapter 8 page 187 RDFCOM Commands Qu...

Page 350: ...dary 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 TRIGGER type EXIT The EXIT command ends your current RDFCOM session Where Issued Primary or backup system Security Any user EXIT FC The FC command enables you to selectively examine edit o...

Page 351: ...NCHDBTIME parameter you can initialize the product online and synchronize the entire database online Where Issued Primary system only Security Super user group member INITIALIZE RDF BACKUPSYSTEM backup system name SUFFIX suffix character TIMESTAMP day mon year hour min INITTIME day mon year hour min NOW SYNCHDBTIME day mon year hour min OBEY The OBEY command executes a series of commands entered i...

Page 352: ...system only Security Super user group member SET EXTRACTOR extractor option where extractor option is CPUS primary CPU backup CPU PRIORITY priority PROCESS process name ATINDEX audittrail index number RTDWARNING rtd time VOLUME volume name 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 R...

Page 353: ...l you issue an ADD command Where Issued Primary system only Security Super user group member SET PURGER purger option where purger option is CPUS primary CPU backup CPU PRIORITY priority PROCESS process name PURGETIME mins RETAINCOUNT num 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...

Page 354: ...CPU EXTENTS primary extent size secondary extent size PRIORITY priority number PROCESS process name RDFVOLUME volume FASTUPDATEMODE on off value SET TRIGGER The SET TRIGGER command sets trigger parameters within the RDF configuration memory table The supplied values are not applied to the RDF configuration file however until you issue an ADD TRIGGER command The trigger type REVERSE or TAKEOVER is ...

Page 355: ... Any user SHOW RDF MONITOR EXTRACTOR RECEIVER IMAGETRAIL TRIGGER VOLUME PURGER RDFNET NETWORK START RDF The START RDF command starts the RDF subsystem Where Issued Primary system only Security Super user group member with remote password from the primary system to the backup START RDF UPDATE ON OFF START UPDATE The START UPDATE command starts all updater processes on the backup system Where Issued...

Page 356: ...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 with remote password from the primary system to the backup STOP UPDATE TIMESTAMP timestamp TAKEOVER The TAKEOVER command causes the backup database to become the database of record Where Issued Backup system only Security Sup...

Page 357: ...og file to which subsequent RDFSCAN commands apply FILE system volume subvolume file 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...

Page 358: ... 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 volume subvol filee or system volume temp file Nondisk Device Names The syntax for a file name that identifies a nondisk device is system device name qualifier or system ldev num...

Page 359: ...eters MAX MIN Default Value s Parameter n a n a BACKUPSYSTEM value used on INITIALIZE RDF RDF BACKUPSYSTEM n a n a 0 RDF LOGFILE n a n a off RDF NETWORK n a n a none RDF OWNER n a n a off RDF REPLICATEPURGE n a n a SYSTEM RDF RDF SOFTWARELOC 10 1 10 RDF UPDATERDELAY n a n a PROTECTED RDF UPDATEROPEN 300 10 60 RDF UPDATERTXTIME none 0 60 RDF UPDATERRTDWARNING n a n a on RDF USEEXCEPTION 199 10 165 ...

Page 360: ...OG 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 RDF Global Parameters SET RDF SOFTWARELOC SYSTEM RDF SET RDF REPLICATEPURGE ON SET RDF NETWORK OF...

Page 361: ...5 LOG MAPLOG SET VOLUME INCLUDE RAGH TEST SET VOLUME INCLUDE RRANGA RAJ SET VOLUME EXCLUDE ARVI SHUK SET VOLUME INCLUDEPURGE NITIN C SET VOLUME EXCLUDEPURGE SAHADEV BN SET VOLUME PROCESS U01 Add the RDF updater parameters for the first updater process to the configuration file ADD VOLUME DB01 Set the updater parameters for the second volume to be protected by the RDF product U02 is the name of thi...

Page 362: ... records If no exception records were written for that volume RDFSNOOP displays this message No exception records written for specified volume If the specified volume has exception records RDFSNOOP displays the image records where the exceptions occurred Here is an example of a formatted display of an RDF exception record Input control subvolume name PRIM1 Input volume name TEST3 ACO INSERT TRANSI...

Page 363: ...lume in which volume is specified by the RDFVOLUME parameter of the ADD RECEIVER command and ADD IMAGETRAIL command The actual file names are of the form AAnnnnnn 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 processe...

Page 364: ...operation or takeover operation They can be read with the READLIST utility which creates a similarly named file in the MIT that can be read with RDFSCAN The ZNETUNDO file only exists in RDF network environments The undo list files resides on the backup node and are named master image trail volume control subvolume ZTXUNDO master image trail volume control subvolume ZFILUNDO master image trail volu...

Page 365: ... and the Operator Messages Manual Many messages include file names that identify objects such as disk files and processes When present these names appear in the message descriptions as parameters such as filename or procname Sometimes these messages simply report syntax errors that result from improperly specifying these file names in commands For more information about file names and the rules th...

Page 366: ...tered the error sno is the sequence number of the file that encountered the error rba is the relative byte address within the file where the error occurred Cause A file system error occurred The message includes both the file system error number and the name of the file or table that encountered the error Effect Variable depends on which file system error occurred Recovery ANSI name or filename is...

Page 367: ...r stopped prematurely and did not stop at the specified timestamp Effect The updaters are stopped but the backup database is not in a consistent state corresponding to the stop update timestamp Recovery Restart the updaters If you still need to bring the backup database to a consistent state do the following Wait for the updaters to catch up and then issue a new stop update to time command specify...

Page 368: ...erlying problem and then restart RDF If you do that however you should select a convenient time to stop TMF and verify that the primary and backup databases are synchronized You should also check the event log to determine whether the shutdown and startup proceeded without error If that is not the case no recovery is possible 707 TMF is not yet started Cause The extractor detected that TMF has not...

Page 369: ...atus returned by the NEWPROCESS system procedure followed by the filename of the program that was to be run Effect The process is not started and RDF shuts down Recovery See the description of the NEWPROCESS procedure in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure Once the underlying cause is corrected RDF can be restarted 713 Backup process creation err...

Page 370: ...t in fault tolerant mode until the primary process can be re created Recovery This is an informational message no recovery is required 716 Primary abended Cause The primary process of a NonStop process pair has abended 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 ...

Page 371: ...the synchronization of the primary and backup databases 721 Audit trail multiple blocks missing Cause The extractor detected an error in block sequence numbers in the TMF audit trail The sequence numbers show that multiple blocks are 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 Re...

Page 372: ... TACL Because the updater might not have processed all image audit the RDF TAKEOVER operation cannot be considered complete Scan the EMS event log for RDF message 726 this message identifies the updater process that did not complete TAKEOVER processing Effect Normal purger shutdown processing continues Recovery If UPDATE was OFF at the time of the RDF TAKEOVER then a second RDF TAKEOVER operation ...

Page 373: ...ect The process runs at the new priority Recovery This is an informational message no recovery is required 731 RDF monitor started Cause The operator issued a START RDF command Effect The RDF monitor process is running and starting up the other RDF processes Recovery This is an informational message no recovery is required 732 Unable to create exception file filename error error filename is the na...

Page 374: ...hat 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 Effect The message type is reported with no other effect Recovery Th...

Page 375: ... file is an Enscribe file you must create the file on the backup system You should always create SQL objects on the backup system first and then create them on the primary system 737 RDF extractor establishing synch Cause When the extractor is starting or restarting it must send a request to the receiver to obtain its starting position in the TMF audit trail The extractor issues event 737 indicati...

Page 376: ...e 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 The receiver has received a message from the extract...

Page 377: ...bends thereby stopping the other RDF processes Recovery This is an internal error Contact your service provider 746 Error during program initialization Cause A fatal error occurred during RDF subsystem initialization Effect RDF stops Error 743 should follow this message Recovery Check the EMS event log for any preceding errors that might indicate the source of the problem If it is possible to corr...

Page 378: ...E specifying a different set of CPUs 751 FILE_OPEN_CHKPT_ 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 FILE_OPEN_CHKPT_ procedure failed and the backup process of a process pair is still running The message includes the file system error number encountered when the pri...

Page 379: ...it trail file and report this error to your service provider 754 Network restored continuing service Cause The primary system processes have determined that the communications lines have been restored The extractor is now able to communicate with the receiver Effect Processing continues from the point at which the network failed Recovery This is an informational message no recovery is required 755...

Page 380: ...ter subsequently encounters another audit record associated with that file the updater pauses its processing until that file is created Alternatively if the record was associated with a PURGEDATA or increase to MAXEXTENTS the operation is not replicated on the backup system Recovery If the record was associated with an Enscribe create you must manually create the file on the backup system If the r...

Page 381: ...ted an internal inconsistency regarding RDF s understanding of an SQL shared access operation Effect The monitor abends Recovery This is an internal error Contact your service provider 765 Invalid audit record encountered type record type Cause The updater process has sent an audit record to the disk process that is the wrong version to the disk process that is in the wrong version The record type...

Page 382: ...y is required 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 This is an informational message no recovery is required 772 TMF is not running on the remote system Cause The receiver has determined that TMF is not started on the RDF backup system Effect The receiver abends Re...

Page 383: ...peration was in progress you must restart RDF If a database synchronization operation was in progress you must restart the entire operation from the beginning 778 Remote RDF updater shutdown complete Cause The updater has terminated normal processing as the result of a STOP TMF STOP RDF STOP UPDATE or TAKEOVER command Effect Normal RDF shutdown processing continues If this message is issued as the...

Page 384: ...e Phase two of the database synchronization involving the process generating this message has completed Effect If the process is the extractor then all operations performed by the extractor for the database synchronization are complete although the updaters might not have completed their work on the backup system If the process is an updater then the backup database is synchronized for the volume ...

Page 385: ...ename is the name of the image trail file that contained the error sno is the sequence number where the error occurred rba is the relative byte address where the error occurred Cause The receiver or an updater has encountered the indicated error while attempting to position into an image file Effect The process abends Recovery Correct the problem that caused the error and then restart RDF 788 ALLO...

Page 386: ...d with the error Cause The receiver or purger process could not create the specified file due to the specified file system error Effect This is a catastrophic error the process abends and RDF stops Recovery Correct the underlying condition then restart RDF 797 Warning Image file purge error error on filename File is currently opened by proc id program filename error is the file system error number...

Page 387: ... an error 12 associated with an image file perform a FUP LISTOPENS on the file to determine which process currently has the designated file open If the process that has the image file open is not an RDF process then stop that process In all other cases restart RDF 799 Image trail file read error error on filename RBA rba error is the file system error number that identifies the specific error file...

Page 388: ...s 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 then you will need to reinitialize RDF and report the error to your service provider 803 Position error error on filename error is the file system error number that identifies the specific error filename is the name of the affected file Cause The RDFNE...

Page 389: ...s required 807 Update mode has been set ON Cause The operator issued a START UPDATE command Effect RDF starts updating the backup database Recovery This is an informational message no recovery is required 808 Update mode has been set OFF Cause The operator issued a STOP UPDATE command Effect RDF stops updating the backup database Recovery This is an informational message no recovery is required 80...

Page 390: ...a restart point from which processing can continue In the latter case there will be a performance degradation Recovery This is an informational message If the condition persists however your database administrator should consider moving some of the files protected by TMF on the primary node volume to another volume and adding another updater to back up the new volume If you do that you must synchr...

Page 391: ... You must initialize RDF to a new database synchronization timestamp and then restart the entire operation from the beginning 819 RDF extractor stopped unexpectedly extractor extractor is the name of the extractor process that stopped Cause The extractor has stopped unexpectedly The message includes the name of the stopped process The message might be expected during ZLT processing depending on th...

Page 392: ...ndo It can be kept because it committed prior to the first network transaction marked for undo on a different node in the RDF network Note however that this transaction could still be undone during final checking for business consistency across all backup nodes Effect This is an internal event There is no effect Recovery This is an informational message no recovery is required 824 Missing RDF extr...

Page 393: ... recovery is required 829 An RDF takeover operation was initiated on the backup system Cause This message indicates that the monitor detected an RDF takeover operation was executed on the RDF backup system Effect This is a catastrophic error and will cause the RDF processes on the primary system to stop Recovery You must reinitialize RDF and you might need to synchronize your databases 830 Warning...

Page 394: ...The 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 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 This message is issued by the purger if i...

Page 395: ...atavol to allow the updater to resume operations 837 Info Restarting at image trail file position SNO sno RBA rba sno is the sequence number of the image file in use at the updater restart rba is the relative byte address in the image file where the updater restart occurred Cause This informational message is logged by an updater when it begins a restart operation The image file sequence number an...

Page 396: ...covery If you can stop the process and give it another name you can then simply restart RDF otherwise you will have to alter the name of the RDF process so that the name does not conflict with other process names 841 Error Unable to complete STOP UPDATE Error error error is a file system error number Cause The monitor was unable to send a shutdown message to an updater because of the indicated fil...

Page 397: ...e database might not be in a consistent state Recovery There is no recovery If you lose your primary system during an online database synchronization the backup database has not yet been synchronized and its data therefore might not be consistent 847 RDF TAKEOVER during initialization synchronization Cause When the updater completed its RDF Takeover operation it had not yet completed its role in a...

Page 398: ...ent nodes The receiver has encountered transactions that have originated on more than 255 nodes Effect The receiver abends and the RDF system aborts Recovery Recovery is not possible Contact your service provider 852 STOP RDF DRAIN completed All updaters have stopped Cause A STOP RDF DRAIN command has completed successfully Effect This RDF environment shuts down Recovery This is an informational m...

Page 399: ...informational message no recovery is required 858 A safe File Recovery position does not exist Cause A network takeover operation has completed but for this particular node in the RDF network there is no safe MAT position with which you can issue a File Recovery operation on your primary system should that node become available again Effect There is no effect Recovery This is an informational mess...

Page 400: ...er continues normal processing Recovery This is an informational message You should however try to determine why the updater has fallen behind and take corrective action if necessary 863 Missing RDFNET CONFIG record Cause The RDF monitor process was unable to find the RDFNET configuration record when performing a START RDF command Effect The START RDF operation fails and RDF shuts down Recovery Re...

Page 401: ...imary system whose final outcome is unknown If the updater was involved in a stop update to time operation it must undo any changes previously made for transactions on the primary system that were not resolved when the shutdown timestamp was reached Effect The updater commences undo processing Recovery This is an informational message no recovery is required 870 No image files present on image tra...

Page 402: ... abends and RDF will abort Recovery The file must be altered or recreated with the correct file format and then RDF can be restarted 876 Imagetrail safe position SNO sno RBA rba sno is the sequence number rba is the relative byte address Cause This is an imagetrail safe position Effect This is an internal event There is no effect Recovery This is an informational message for historical purposes ab...

Page 403: ...bject type ANSI name Partition partition id file filename ANSI object type is the ANSI object type for example table index and so on ANSI name is the ANSI name of the SQL MX object that encountered the error partition id is the partition ID of the SQL MX object that encountered the error filename is the Guardian filename of the file that encountered the error Cause The specified table or file on t...

Page 404: ...process encountered a condition that caused it to restart Effect The process restarts and resumes normal processing Recovery Examine the preceding events for this process to try to determine why the process is restarting Take corrective action if necessary 885 Updater phase one takeover processing complete Cause The updater has completed the local undo processing phase Effect The updater is ready ...

Page 405: ...he purger is ready to try to build the network undo list This event indicates that this is the purger s first attempt or it is about to retry the operation because of a previous failure Effect The purger starts an attempt to build the list Recovery This is an informational message no recovery is required 891 First network transaction to be undone identifier identifier is the transaction identifier...

Page 406: ...DDL operation on your backup system After having done this you might restart your updaters 895 File incomplete record encountered during stop update to time operation Cause You have performed a stop update to time operation but not all the volumes on the RDF primary system are up and recovered Effect The operation is aborted and the RDF subsystem aborts Recovery You can restart the RDF product imm...

Page 407: ...required 902 The remote mirror for volume is missing volume is a volume name Cause The extractor has determined that the specified remote mirror is not connected to the ZLT standby system or that an expected audit trail file is missing Effect The extractor abends Recovery Connect all required remote mirrors to the ZLT standby system and then re issue the RDF TAKEOVER command If you have already co...

Page 408: ... message are the error number and error detail returned by the PROCESS_CREATE_ system procedure followed by the filename of the program that was to be run Effect The process is not started and RDF shuts down Recovery See the description of the PROCESS_CREATE_ procedure in the Guardian Procedure Calls Reference Manual to determine the cause of the failure Once the underlying cause is corrected RDF ...

Page 409: ...sage no recovery is required 910 Update stopped as a result of a STOP UPDATE command Cause The purger logs this event whenever all updaters have stopped following a STOP UPDATE command Effect The updater processes are stopped Recovery This is an informational message no recovery is required 91 1 Updaters stopped before STOP RDF DRAIN has completed Cause The purger has detected that all the updater...

Page 410: ...e file returned the specified Guardian error Effect The file is not created and the effect on RDF depends on which process reported the error and on what it was attempting to do at the time Recovery If possible the user should attempt to correct the underlying problem or seek assistance from their service provider 917 Shared access DDL operation encountered while DRAIN or REVERSE is pending Cause ...

Page 411: ...ve action to alleviate the cause of the exception if possible and restart RDF If the cause of the exception is not immediately obvious contact your service provider 921 The updater s MAPFILE filename is not an edit file Cause The updater has detected that the mapfile is not an edit file Effect The updater stops and RDF aborts Recovery Provide an edit file then restart RDF 922 Mapping string mappin...

Page 412: ...ing mapping string at position index in the MAPFILE filename mapping string identifies the invalid mapping string index is the string index at which the character is detected filename is the name of the updater mapfile specified in the updater configuration Cause The updater has detected the character in the specified mapping string The volume name is not allowed in the mapping string The position...

Page 413: ...iguration Cause RDFCOM detected a character in the mapping string specified in the updater mapfile when an ADD VOLUME ALTER VOLUME START RDF START UPDATE or VALIDATE CONFIGURATION command was being executed Effect The command fails Recovery Correct the mapping string by removing the character then reenter the command Allocation error error on IMAGETRAIL volume name error is the file system error n...

Page 414: ...and it is impossible to determine the correct intended time This problem typically occurs in Autumn when the clock is set back from Daylight Savings Time If you specify an RDF initialization timestamp between 1 00AM and 2 00AM on that day the intended time is ambiguous Did you mean before the clock was turned back or after To eliminate this ambiguity a specified RDF initialization timestamp in thi...

Page 415: ...more network records to the configuration describing the non network master subsystem s Audit is missing Contact 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 might be no recovery for this problem To verify that required audit is missing from your local image trail contact your local HP...

Page 416: ...for which the ALTER command failed Cause An ALTER command failed for the specified components Effect The command fails Recovery See 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 t...

Page 417: ...performed after INITIALIZE RDF Effect START RDF processing is aborted Recovery See 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 Couldn...

Page 418: ...ate a temporary image file on the IMAGETRAIL volume This allocation failed for the reason indicated by the file system number error Effect The command fails Recovery See 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 Correct the error indicated by err...

Page 419: ...you respond NO or N however the subsystem will not be initialized Recovery This is an informational message no recovery is required 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 sh...

Page 420: ...ommand fails Recovery See the Guardian Procedure Errors and Messages Manual for a description of and recovery actions for the file system error Correct the error indicated by error then reenter the command Error error obtaining pool information for SMF volume error is the file system error number that identifies the specific error volume is the SMF volume Cause RDFCOM experienced an error while at...

Page 421: ...tanding and correcting file system errors see the Guardian Procedure Errors and Messages Manual Correct the error and reenter the INITIALIZE RDF command If the problem persists contact your system manager Error error on filename while cleaning the control subvolume on the remote system error is the file system error number that identifies the specific error filename is the name of the remote contr...

Page 422: ...see the Guardian Procedure Errors and Messages Manual Take appropriate corrective action and then reissue the COPYAUDIT command Error error on setmode for imagefile security error is the file system error number that identifies the specific error Cause The COPYAUDIT command encountered the specified error while attempting to set the security for a new image file on the local image trail where it i...

Page 423: ...T RDF START UPDATE or VALIDATE CONFIGURATION command was being executed Effect The command fails Recovery Add the keyword NAMES in the mapping string then reenter the command Expected TO in the mapping string mapping string in the MAPFILE filename mapping string is the erroneous mapping string specified in the mapfile filename is the name of the updater mapfile specified in the updater configurati...

Page 424: ...ual If possible correct the error and reenter the command that encountered the error Otherwise see your system manager Extended Swap File Segment Error error error is the NEWPROCESS 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 See the Operator Messages Manual ...

Page 425: ...tem to the local system Effect RDF begins to copy the ZFILEINC file Recovery This is an informational message no recovery is required 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 valid...

Page 426: ...ls Recovery Add the image trail Then add the updater IMAGETRAIL for IMAGEVOLUME vol name does not exist or the atindex of the IMAGEVOLUME does not match the updater s atindex vol name is the image trail volume Cause You tried to add an updater for a particular ATINDEX but there is no imagetrail configuration for that value Either you have not yet added the imagetrail or you added it with a differe...

Page 427: ...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 IMAGETRAIL VOLUME volume name is not a disk volume volume name is the name of the volume Cause While validating your configuration RDFCOM determined that volume name does no...

Page 428: ...nitialize 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 This message follows a previous error message that indicates why the INITIALIZE RDF command failed Effect RDF is no...

Page 429: ...tifies the specific error Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing Effect The START RDF or TAKEOVER operation is aborted Recovery See 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 Correct the error and reenter the START R...

Page 430: ...ping string is invalid in the MAPFILE filename The subvolume subvolume name is invalid mapping string is the erroneous mapping string specified in the MAPFILE filename is the name of the updater MAPFILE specified in the updater configuration subvolume name is the erroneous subvolume specified in the mapping string Cause RDFCOM detected that the subvolume indicated by subvolume name is invalid when...

Page 431: ...ct 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 The INFO command could not find a monitor record in the configuration file Effect The command fails Recovery Alter the c...

Page 432: ...ecified ATINDEX but there is no extractor with that value Effect The validation fails Recovery Add an extractor with the same ATINDEX value or delete the particular receiver No RECEIVER is configured for ATINDEX atindex Cause You added an extractor with the specified ATINDEX but there is no receiver with that value Effect The validation fails Recovery Add a receiver with the same ATINDEX value or ...

Page 433: ... invalid Effect The configuration validation fails Recovery Check the updater process parameters in the configuration file for invalid values and correct any errors found 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 s...

Page 434: ... Correct the error indicated by error then reenter the command Open error error on MAPLOG file filename error is the file system error number that identifies the specific error filename is the name of the updater maplog specified in the updater configuration Cause RDFCOM was not able to open the updater maplog when an ADD VOLUME ALTER VOLUME START RDF or START UPDATE command was being executed Eff...

Page 435: ...te the operation at any time by pressing the BREAK or equivalent key PNETTXVOLUME volume for ctrl subvol must be protected by a MAT based updater volume is the name of an RDF data volume ctrl subvol is the name of an RDF subsystem control subvolume Cause The specified volume for the RDF subsystem with the specified control subvolume is not configured to the Master Audit Trail MAT Effect Validation...

Page 436: ...he specified image file on the local image trail volume Effect The COPYAUDIT command aborts Recovery See 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 prov...

Page 437: ... Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing Effect The START RDF or TAKEOVER operation is aborted Recovery See 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 encount...

Page 438: ... An ADD RDF command was issued when the configuration file already contained an RDF global record Effect The command fails Recovery No recovery is required if you want to use the subsystem with the existing RDF global parameters configured If you want to change any of the global parameters however enter an ALTER RDF command that specifies those changes RDF record NOT found Cause The INFO command c...

Page 439: ...n Critical Solution Center GMCSC 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 In response to a prompt you requested RDFCOM to trigger restoration of an audit trail file If the file has been previously dumped to tape you must now watch the EMS log for the TMP s prompt...

Page 440: ...ntifies the specific error 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 See 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 Mes...

Page 441: ...e on the receiver s RDFVOLUME and then to allocate all 16 extents This check if successful verifies that If RDF is starting for the first time there is enough storage for at least one image file If RDF has been started previously there is enough storage for one image file when the next image file rollover occurs If the check fails because there is insufficient storage this message appears Effect T...

Page 442: ...ause You tried to add an imagetrail with the specified ATINDEX but there is no receiver with that value Effect The ADD command fails Recovery You must add the corresponding receiver process before adding an imagetrail with the same ATINDEX value Remote system for Triple Contingency CopyAudit command is unavailable remote system remote system is the name of the RDF backup system that received the m...

Page 443: ...F image trail volumes on the remote system named in the COPYAUDIT command Cause The COPYAUDIT command is about to search for missing audit this audit reached the specified image trail on the remote system but did not reach the local system before the original primary system was lost Effect The COPYAUDIT command begins the search Recovery This is an informational message no recovery is required Shu...

Page 444: ...e Specified network primary system name is unavailable Cause RDFCOM is unable to reach the specified primary system Effect The configuration command fails Recovery Determine why the comm path to this system is down and take the appropriate recovery steps to bring it up Specified TMF shutdown timestamp at timestamp is earlier than the earliest timestamp in the TMF MAT Please examine the OPRLOG for ...

Page 445: ...s started and then reenter the STATUS RDF command STOP SYNCH command is aborted Cause You are attempting to execute the RDFCOM STOP SYNCH command but either the RDF product is not running or another critical operation is already in progress Effect The RDFCOM STOP SYNCH command aborts Recovery Correct the situation and then reissue the command STOP SYNCH command is aborted because database synchron...

Page 446: ... identifies the specific error Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing Effect The command fails Recovery See 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 encoun...

Page 447: ...IZE RDF command The control subvolume sys SYSTEM subvol is not empty The files on the control subvolume must be purged Please note these files might belong to another RDF configuration sys is the name of the primary system subvol is the name of the local RDF control subvolume Cause You tried to execute an INITIALIZE RDF command but RDF control files such as CONFIG or CONTEXT already exist on the l...

Page 448: ... The MAPLOG file filename could not be created error error filename is the name of the updater maplog specified in the updater configuration error is the file system error number that identifies the specific error Cause Create operation returned an error when RDFCOM tried to create the updater maplog file when an ADD VOLUME ALTER VOLUME START UPDATE or START RDF command was being executed Effect T...

Page 449: ...t RDF will not start Recovery Upgrade the RDF software to RDF IMPX or reconfigure your disks on the RDF backup node so that the total number of physical disks for all the UPDATEVOLUMEs is less than 255 The PURGER must be a named process Cause You must specify a process name for the purger process before issuing an ADD command Effect The start command fails Recovery You must reconfigure RDF with a ...

Page 450: ... least five minutes ahead of the current time The STOP SYNCH command is aborted because it has been issued previously Cause You are attempting to execute an RDFCOM STOP SYNCH command but the command has already been issued previously Effect The RDFCOM STOP SYNCH command aborts Recovery You can only execute the STOP SYNCH command if the RDF product is currently involved in online database synchroni...

Page 451: ...nd 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 Your current RDF subsystem is not listed in your the configuration of your network master Effect Validation fails Recovery You must reconfigure your network master and possibly your loc...

Page 452: ...TOP in progress Cause A TMF stop operation is in progress Effect TMF stops and RDF automatically stops thereafter Recovery This is an informational message no recovery is required 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 aud...

Page 453: ...utdown timestamp and then its attempt to initialize RDF Recovery Check to see if TMF is started If it is not start TMF before you again attempt to initialize RDF If it is running and this error occurs this is an internal error Contact the Global Mission Critical Solution Center GMCSC or your service provider Unable to obtain the process access id of RDFCOM Cause RDFCOM could not obtain the process...

Page 454: ... 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 Unlicensed Privileged Program Cause A NEWPROCESS error occurred during START RDF or TAKEOVER processing Effect The operation is aborted Recovery License the ...

Page 455: ...nsists 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 VOLUME volume does NOT exist volume is the volume on the primary node for which the updat...

Page 456: ... 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 The command fails Recovery Alter the configuration to include the updater process WARNING BACKUPSWAP parameter has no effect KMSF swap volume takes pr...

Page 457: ...trail beyond the specified shutdown timestamp RDF will ignore all audit generated before this timestamp Cause You entered an INITIALIZE RDF command that attempted to initialize RDF at a specific TMF shutdown timestamp Effect RDF is ready to start reading the Master Audit Trail MAT Recovery This is an informational message no recovery is required WARNING RDF will start at the first record in the TM...

Page 458: ...tional details about understanding and correcting file system errors see the Guardian Procedure Errors and Messages Manual Correct the problem and reissue the STOP SYNCH command Write error error on local image file error is the file system error number that identifies the specific error Cause The COPYAUDIT command encountered the specified error while attempting to write data to a local image fil...

Page 459: ...ceed Cause You have asked RDFCOM to unpin a file that is currently needed by the extractor If you respond yes the file is unpinned and TMF can rename it If the file is renamed RDF cannot be restarted until you restore the file 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 cr...

Page 460: ... primary system You should also ensure that the takeover operation completed successfully 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 U...

Page 461: ... file associated with the error Cause A file system error occurred while RDFSCAN was trying to open the specified log file Effect The command fails Recovery See 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 t...

Page 462: ...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 anoth...

Page 463: ...p system 255 Number of auxiliary image trails 3000 Number of files per updater 37 Number of RDF configurations with the same primary system 255 Number of systems that can contribute audit to a primary system 65 500 Maximum number of image trail file primary and secondary extents 48 Maximum number of primary systems that can be in an RDF network for protection of a distributed database 463 ...

Page 464: ...464 ...

Page 465: ...er Process SGP SGP is the interface between ASAP and the RDF environments For every system in which ASAP is configured to collect RDF data the ASAP monitor starts an RDF SGP process Figure E 1 shows a single RDF environment replicating from PRI to BAK To monitor an RDF environment using ASAP you must configure an RDF SGP on both the primary and backup RDF systems The SGP on the primary system repo...

Page 466: ...volumes on SYSTEM for RDF configuration files By default it monitors the status of all RDF IMP and IMPX environments it finds NOTE Before starting the RDF SGP for the first time you should purge any control subvolumes that are old and no longer being used to ensure that ASAP monitors only current RDF environments Monitoring Specific RDF Environments If you only want to monitor specific RDF environ...

Page 467: ...ompatibility The RDF SGP supplied with each version of RDF IMP X only runs with that version of RDF All RDF IMP X environments on a given system must match the version of the RDF SGP RDF Metrics Reported by ASAP For each RDF entity the RDF SGP passes the information shown in Table E 1 back to ASAP Table E 1 RDF Metrics Reported by ASAP Updater RDFNET Purger Imagetrail Receiver Extractor Monitor In...

Page 468: ... to ASAP X X X X TMF Auxiliary Audit Index X X X X File Sequence Number X X Relative Byte Address X X X X RTD Time X X1 X X X X Primary CPU X X1 X X X X Backup CPU X X1 X X X X Priority 1 Only in an RDF Network environment 2 Only reported by the master receiver where the master image trail MIT volume is reported 468 Using ASAP ...

Page 469: ...iles needed 62 configuration 57 failure 129 files 74 NonStop SQL MP catalogs contents 71 NonStop SQL MP objects on 70 program files 74 RDF requirements 57 recompiling programs 74 tasks 39 views 63 volume names 58 BACKUPSWAP parameter 228 BACKUPSYSTEM network attribute 296 BACKUPSYSTEM parameter 212 Bracket prompt 99 C Catalog changes NonStop SQL MP 160 ODBC 160 Catalogs NonStop SQL MP backup syste...

Page 470: ...1 File Utility Program FUP 74 OBEY command files 71 when to synchronize 251 Databases backing up altered structures 159 Enscribe file label modifications 164 NonStop SQL MP backing up altered structures 160 catalog changes 160 DDL operations 160 partition key changes 163 synchronization 160 table purges 163 NonStop SQL MX 323 states 157 synchronizing entire database 165 individual tables or files ...

Page 471: ...ater 127 FC command 201 350 Features RDF subsystem 35 File auditing by TMF required 59 backing up 62 configuration command example 360 error recovery creation failures 123 modification failures 122 open failures 122 exception examining 362 label modifications 64 log 38 261 OBEY command 103 360 partitioned 63 placement of partitions 65 RDF requirements 59 temporary 65 File code 900 63 FILE command ...

Page 472: ...235 352 object code file 75 parameters 91 360 adding to configuration file 193 349 altering 196 displaying configuration values 206 351 displaying option values 239 355 INFO MONITOR example 210 resetting option values 220 352 SET MONITOR example 225 226 232 setting option values 224 225 231 235 352 Multiple backup systems replication to 52 N Name mapping SQL MX 332 NETWORK attribute 295 Network tr...

Page 473: ...ram FUP 74 OBEY command files 71 Primary system backing up files 62 configuration 57 failure 128 preparing for RDF installation 69 processes 41 RDF requirements 57 Primary system failure stopping the backup system before restarting the primary system 132 PRIMARYSWAP parameter 228 PRIMARYSYSTEM network attribute 296 PRIORITY attribute extractor process 92 monitor process 91 receiver process 93 94 P...

Page 474: ...e delay RTD 134 user interfaces 38 RDF IMP product components 75 RDF IMPX product components 75 RDF ZLT product components 76 RDFCHEK file comparison utility 75 licensed program 76 RDFCOM command summary 103 command syntax 99 101 commands ADD 193 349 ADD EXTRACTOR 88 92 ADD MONITOR 91 ADD RECEIVER 93 94 ALTER 195 349 COPYAUDIT 350 DELETE 199 350 examples 187 349 EXIT 201 350 FC 201 350 HELP 203 35...

Page 475: ... Recompiling programs 74 Reload of backup database 62 REMOTECONTROLSUBVOL network attribute 297 REMOTECONTROLSUBVOL parameter 197 REMOTESYS parameter 197 Replicating database operations 64 Replication file level 279 subvolume level 279 to multiple backup systems 52 Report definitions SQLCI 71 Requirements RDF hardware 57 software 59 TMF 60 Reserved file names 358 RESET command 220 352 RESET PROCES...

Page 476: ...n online 176 Syntax of RDFCOM commands 99 187 349 SYSGEN parameters 63 T Tables NonStop SQL MP backup system 70 partition key changes 163 partitioned 63 placement of partitions 65 preparing for RDF protection 70 purges 163 TACL macros backup system 71 RDFINST for RDF installation 75 TAKEOVER command 255 356 audited volumes on backup system 70 stopping the RDF subsystem 139 Takeover operations ZLT ...

Page 477: ...TEVOLUME parameter 236 User interfaces RDF subsystem 38 V VALIDATE CONFIGURATION command 258 356 Views NonStop SQL MP 63 70 Volume audited on backup system 70 configuration 58 failure TMF 128 limit 58 mapping 58 mapping primary to backup 70 names 191 names different on primary and backup 70 VOLUME command 218 VOLUME parameter 199 W Wildcard characters in match patterns 268 Z ZLT overview 337 takeo...

Page 478: ......

Search results

Summary of Contents for NonStop RDF

Reviews:

Related manuals for NonStop RDF

Brands by name

Popular brands

HP NonStop RDF, Management Manual

Search results

Summary of Contents for NonStop RDF

Reviews:

Related manuals for NonStop RDF

Brands by name

Popular brands