ibm i: recovering your system€¦ · field descriptions for r estor e output file .... . 52...

IBM iVersion 7.3

Systems managementRecovering your system

SC41-5304-12

IBM

NoteBefore using this information and the product it supports, read the information in Notices on page 519.

This edition applies to IBM i 7.3 (product number 5770-SS1) and to all subsequent releases and modifications untilotherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC)models nor does it run on CISC models.

This edition replaces SC41-5304-11.

This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and islicensed to you under the terms of the IBM License Agreement for Machine Code.

Copyright IBM Corporation 1997, 2015.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . xiii

Recovering your system . . . . . . . xv

What's new for IBM i 7.3. . . . . . . xvii

Part 1. Saving information on yoursystem . . . . . . . . . . . . . . . 1

Chapter 1. Saving the system . . . . . 3Overview of the GO SAVE command . . . . . . 3GO SAVE command menu options . . . . . . . 4GO SAVE: Option 21 (saving the entire system). . . 6Performing a complete save using the GO SAVEchecklist . . . . . . . . . . . . . . . . 7Optional features that affect your backup . . . . 12

Are you using user-defined file systems . . . . 13Are you using software encryption for tapes . . 13Do you use virtual storage . . . . . . . . 13Do you use independent disk pools . . . . . 13Have you configured independent disk pools toswitch between systems in a cluster . . . . . 13Do you use WebSphere MQ for IBM i on thissystem . . . . . . . . . . . . . . . 14Do you use OptiConnect controllers . . . . . 14Do you use network servers . . . . . . . . 14Do you use the Hardware Management Console 14

Printing system information . . . . . . . . . 14Save considerations when checking out objects . . 17Tape write error recovery . . . . . . . . . . 17ObjectConnect function . . . . . . . . . . 17

Components of ObjectConnect . . . . . . . 18Setting up your system to use ObjectConnect . . 18How the system runs an ObjectConnectcommand . . . . . . . . . . . . . . 19Using the ObjectConnect commands . . . . . 20

Save/Restore (SAVRST) command. . . . . 20Save/Restore Object (SAVRSTOBJ) command 20Save/Restore Changed Objects (SAVRSTCHG)command . . . . . . . . . . . . . 20Save/Restore Library (SAVRSTLIB) command 20Save/Restore Document Library Object(SAVRSTDLO) command . . . . . . . . 21Save/Restore Configuration (SAVRSTCFG)command . . . . . . . . . . . . . 21

Investigating ObjectConnect problems . . . . 21CPFAD84 error codes . . . . . . . . . . 21

Source system-specific error codes fromCPFAD84 message . . . . . . . . . . 22Target system-specific error codes fromCPFAD84 message . . . . . . . . . . 22

Source or target system error codes fromCPFAD84 message . . . . . . . . . . 22

Part 2. Recovering information onyour system. . . . . . . . . . . . 23

Chapter 2. Restoring the system:Introduction . . . . . . . . . . . . 25The relationship between save and restorecommands. . . . . . . . . . . . . . . 27What happens when you restore objects . . . . . 28Sequence for restoring related objects . . . . . . 31Deferring the restore of dependent objects . . . . 31Putting your system in a restricted state . . . . . 33Reclaim Storage (RCLSTG) command. . . . . . 34

Reclaiming storage . . . . . . . . . . . 37Reclaiming object links . . . . . . . . . . 38Controlling restoration of security-sensitive objects 40

QALWOBJRST system value. . . . . . . . 40Setting the QALWOBJRST system value to allowcomplete recovery . . . . . . . . . . . 41Setting the QALWOBJRST system value torestrict restore operations . . . . . . . . . 41QVFYOBJRST system value . . . . . . . . 41Setting the QVFYOBJRST system value to allowcomplete recovery . . . . . . . . . . . 42Setting the QVFYOBJRST system value to restrictrestore operations . . . . . . . . . . . 43

Minimizing object scans after restore operations . . 43Setting the QPFRADJ system value for a differentprocessor or memory . . . . . . . . . . . 44Locked objects while restoring . . . . . . . . 44Verifying whether objects are restored successfully 44Recovery from an unsuccessful restore operation . . 47

Recovering from an error while restoring libraries 47Recovering from an error while restoringdocument library objects . . . . . . . . . 48

Recovering documents and folders . . . . 48Recovering from unsuccessful system signon 49

Performing a normal initial program load . . . . 49Parallel restore operations . . . . . . . . . 50Restore operation output file information . . . . 50Field descriptions for restore output file . . . . . 52

Chapter 3. Selecting the appropriaterecovery strategy . . . . . . . . . . 59Some common recovery terminology . . . . . . 59Recovery procedure for a power failure . . . . . 60Recovery procedure for a system failure . . . . . 61Recovery procedure for a program failure or humanerror. . . . . . . . . . . . . . . . . 61Recovering the vital product data information if thepartition does not IPL in A-mode or B-mode . . . 61

Copyright IBM Corp. 1997, 2015 iii

Choosing the recovery procedure for a disk failureor disk errors . . . . . . . . . . . . . . 62

Checklist 1: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 64Checklist 2: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 65Checklist 3: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 66Checklist 4: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 68Checklist 5: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 71Checklist 6: Actions for non-load source disk unitfailure or disk units in basic user auxiliarystorage pool disk failure . . . . . . . . . 75Checklist 7: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 76Checklist 8: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 77Checklist 9: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 78Checklist 10: Actions for non-load source diskunit failure . . . . . . . . . . . . . 82Checklist 11: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 85Checklist 12: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 86Checklist 13: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 88Checklist 14: Actions for non-load source diskunit failure . . . . . . . . . . . . . 90Checklist 15: Actions for non-load source diskunit failure . . . . . . . . . . . . . 91Checklist 16: Actions for non-load source diskunit failure . . . . . . . . . . . . . 92Checklist 17: Actions for independent auxiliarystorage pool disk failure . . . . . . . . . 93Checklist 18: Actions for a failure in anindependent auxiliary storage pool disk unit . . 94Checklist 19: Actions for a failure in anindependent auxiliary storage pool disk unit . . 95Checklist 20: Recovering your entire system aftera complete system loss . . . . . . . . . 97Checklist 21: Recovering your entire systemafter a complete system loss includingindependent auxiliary storage pools . . . . . 100Checklist 22: Restoring a logical partition toanother logical partition . . . . . . . . . 104Checklist 23: Actions for a failed cache card . . 106

Choosing the procedure to recover userinformation . . . . . . . . . . . . . . 107

Checklist 24: Recovering user information usingcommands . . . . . . . . . . . . . 109Checklist 25: Using option 21 from the restoremenu . . . . . . . . . . . . . . . 112Checklist 26: Using options 22 and 23 from therestore menu . . . . . . . . . . . . 115Checklist 27: Recovering user information usingtapes from Operational Assistant backup . . . 118

Chapter 4. Recovering the LicensedInternal Code . . . . . . . . . . . 123Preparing for loading the Licensed Internal Code 124

Task 1: Getting ready to load the LicensedInternal Code . . . . . . . . . . . . 124Task 2: Powering down the system . . . . . 125Task 3: Preparing to start the system from analternate IPL device . . . . . . . . . . 126Task 4: Loading the Licensed Internal Codefrom media . . . . . . . . . . . . . 126

Loading the Licensed Internal Code . . . . . . 129Recovering the vital product data information ifthe partition does not IPL in A-mode or B-mode . 132Setting up your disk configuration after installingthe Licensed Internal Code . . . . . . . . . 133Using System i Navigator to set up your diskconfiguration after installing Licensed InternalCode . . . . . . . . . . . . . . . . 134Recovering your disk configuration . . . . . . 138Starting your system after restoring the LicensedInternal Code . . . . . . . . . . . . . 140

Chapter 5. Restoring the operatingsystem . . . . . . . . . . . . . . 143Choosing the right procedure for restoring theoperating system . . . . . . . . . . . . 144Loading the operating system using a manualinitial program load . . . . . . . . . . . 144Tasks to restoring the operating system. . . . . 145

Task 1: Starting to restore the operating system 146Task 2: Selecting the installation options . . . 150Task 3: Selecting initial program load options 154Task 4: Setting major system options . . . . 155Task 5: Defining or changing the system atinitial program load (IPL) . . . . . . . . 156Task 6: Completing the initial program load . . 158

Recovering from SRC A900 2000 . . . . . . . 159Creating a configuration for other tape units 159

Chapter 6. Starting the system after itends abnormally . . . . . . . . . . 161What happens when your system stops . . . . 161

Using the Disk Configuration Error Reportdisplay . . . . . . . . . . . . . . 161Using the Main Storage Dump Occurred display 162

Restarting your system . . . . . . . . . . 162Task 1: Performing an attended initial programload . . . . . . . . . . . . . . . 163Task 2: Editing the rebuilding of access paths 165Task 3: Editing check pending constraints . . . 166Task 4: Recovering from damaged objects andunreadable sectors. . . . . . . . . . . 167

Recovering a damaged journal . . . . . 169Recovering a damaged journal receiver . . . 170Recovering a journaled object that isdamaged or not synchronized . . . . . . 170Recovering damaged objects in the integratedfile system . . . . . . . . . . . . 171Recovering other types of damaged objects 171

iv IBM i: Recovering your system

Chapter 7. Recovering information ina user auxiliary storage pool. . . . . 173Describing the contents of your user auxiliarystorage pools . . . . . . . . . . . . . 173Choosing the procedure to recover user auxiliarystorage pools (ASPs) . . . . . . . . . . . 174Recovering a basic user auxiliary storage pool(ASP) after recovering the system ASP . . . . . 174

Task 1: Reclaiming storage . . . . . . . . 175Task 2: Restoring user profiles . . . . . . . 176Task 3: Restoring the configuration . . . . . 177Task 4: Recovering journals and journalreceivers in the QRCL library . . . . . . . 177Task 5: Restoring libraries to the systemauxiliary storage pool . . . . . . . . . 178Task 6: Restoring document library objects tothe system auxiliary storage pool . . . . . . 179Task 7: Restoring user-defined file systems tothe user auxiliary storage pool . . . . . . 179

Recovery steps for unmounted user-definedfile systems in a user ASP . . . . . . . 180Recovery steps for a mounted user-definedfile systems if data is not restored . . . . 180Recovery steps for a mounted user-definedfile system if data is restored . . . . . . 180

Task 8: Reclaiming document library objects . . 180Task 9: Recovering save files from the QRCLlibrary. . . . . . . . . . . . . . . 181Task 10: Associating journal receivers withjournals . . . . . . . . . . . . . . 181Task 11: Restoring object ownership . . . . . 182

Recovering an overflowed user auxiliary storagepool . . . . . . . . . . . . . . . . 184

Resetting an overflowed user auxiliary storagepool (ASP) without an initial program load(IPL) . . . . . . . . . . . . . . . 184Resetting an overflowed user auxiliary storagepool (ASP) during an initial program load (IPL) . 185

Deleting overflowed objects during recovery . . . 187Recovering a damaged basic auxiliary storage pool 188

Task 1: Restoring user profiles . . . . . . . 188Task 2: Determining the contents of the lostauxiliary storage pool . . . . . . . . . 188Task 3: Determining tasks to restore objects . . 189Task 4: Restoring libraries to a basic auxiliarystorage pool . . . . . . . . . . . . . 190Task 5: Restoring journals to a basic auxiliarystorage pool . . . . . . . . . . . . . 190Task 6: Restoring documents to a basic auxiliarystorage pool . . . . . . . . . . . . . 191Task 7: Restoring user-defined file systems to abasic auxiliary storage pool. . . . . . . . 191

Recovery steps for unmounted user-definedfile systems . . . . . . . . . . . . 191Recovery steps for a mounted user-definedfile system if data is not restored . . . . . 192Recovery steps for a mounted user-definedfile system if data is restored . . . . . . 192

Task 8: Restoring journal receivers to a basicauxiliary storage pool . . . . . . . . . 192

Task 9: Restoring save files to a basic auxiliarystorage pool . . . . . . . . . . . . . 192

Recovering an independent auxiliary storage pool 193Task 1: Restoring user profiles . . . . . . . 193Task 2: Determining tasks to restore objects toan independent auxiliary storage pool . . . . 193Task 3: Restoring libraries to the independentauxiliary storage pool . . . . . . . . . 194Task 4: Restoring user-defined file systems tothe independent auxiliary storage pool . . . . 195

Recovery steps for unmounted user-definedfile systems . . . . . . . . . . . . 195Recovery steps for a mounted user-definedfile system if data is not restored . . . . . 195Recovery steps for a mounted user-definedfile system if data is restored . . . . . . 196

Task 5: Restoring authority for an independentauxiliary storage pool . . . . . . . . . 196

Removing a failed disk unit from the systemauxiliary storage pool . . . . . . . . . . 196

Task 1: Accessing dedicated service tools . . . 197Task 2: Deleting the auxiliary storage pool data 198Task 3: Removing the disk unit from theauxiliary storage pool configuration . . . . . 199

Chapter 8. The restore menu . . . . . 201What the restore menu options do . . . . . . 201Using restore menu options 21, 22, and 23. . . . 203

Chapter 9. Restoring specific types ofinformation . . . . . . . . . . . . 209Recovering system information . . . . . . . 209Recovering TCP configuration information . . . 210Sequence for restoring security information . . . 210Restoring user profiles . . . . . . . . . . 211

What happens when you restore user profiles 212What you should know about restoring userprofiles . . . . . . . . . . . . . . 214How the system establishes ownership forrestored objects . . . . . . . . . . . . 215How the system establishes the authorizationlist for a restored object . . . . . . . . . 216How the system establishes the primary groupfor restored objects . . . . . . . . . . 216

Restoring object authorities . . . . . . . . . 216Overview of restoring authorities. . . . . . 217Restoring private authorities in a full-systemrecovery . . . . . . . . . . . . . . 217Restoring private authorities for selected objects 218Restoring authority on a system in anonrestricted state . . . . . . . . . . . 219

What you should know before running theRestore Authority command . . . . . . 219Job log considerations . . . . . . . . 220

Restoring authority on a system in a restrictedstate . . . . . . . . . . . . . . . 223Examples: How the system restores authority 223

Restoring authorities for independent auxiliarystorage pool data . . . . . . . . . . . . 225Restoring configuration objects . . . . . . . 229

Contents v

Correcting problems with the system resourcemanagement information . . . . . . . . 230

Recovering devices that will not vary on . . 231Recovering when you change the console type 232Recovering the System/36 environmentconfiguration . . . . . . . . . . . . 232

Restoring logical partitions . . . . . . . . . 233Restoring libraries . . . . . . . . . . . . 233

Restoring a library from a previous release . . 234Restoring multiple libraries . . . . . . . . 234Considerations and restrictions of the RestoreLibrary command . . . . . . . . . . . 235Restoring all libraries from a single saveoperation . . . . . . . . . . . . . . 235Restoring all libraries from multiple saveoperations . . . . . . . . . . . . . 236

Restoring objects . . . . . . . . . . . . 236Restoring journaled objects . . . . . . . . 237

What happens when you restore journaledobjects to a different library or directory . . 240

Restoring user-defined file systems . . . . . . 241Restoring an unmounted user-defined filesystem . . . . . . . . . . . . . . 241

Restrictions while you restore an unmounteduser-defined file systems . . . . . . . 241

Restoring an individual object from anunmounted user-defined file systems . . . . 241Restoring a mounted user-defined file system 241Restore actions for mounted user-defined filesystems . . . . . . . . . . . . . . 242

Restoring database files . . . . . . . . . . 242Comparing file attributes during a restoreoperation . . . . . . . . . . . . . . 244How the system matches file members during arestore operation . . . . . . . . . . . 247Restoring members to a file . . . . . . . 247

Restrictions on the file member (FILEMBR)parameter . . . . . . . . . . . . 247

Restoring logical files. . . . . . . . . . 248How the system restores access paths . . . . 249

Examples: Restoring a file network . . . . 250Preventing the system from rebuilding alarge access path . . . . . . . . . . 251

How the system restores files with sharedformats . . . . . . . . . . . . . . 252How the system restores files with referentialconstraints . . . . . . . . . . . . . 252

Example: Referential constraint network . . 252How the system restores files with triggers . . 253Restoring SQL materialized query tables . . . 254Deleting a physical file . . . . . . . . . 255Restoring physical files that are temporal . . . 255

Restoring journals and journal receivers . . . . 255Restoring journals . . . . . . . . . . . 256Deleting a journal . . . . . . . . . . . 257Restoring journal receivers . . . . . . . . 258

Resolving name conflicts when restoringjournal receivers . . . . . . . . . . 258Correcting the journal receiver directory . . 258

Deleting a journal receiver . . . . . . . . 259How the system restores programs . . . . . . 259

Restoring programs to a different release . . . 261Restoring save file data . . . . . . . . . . 261Saving and restoring spooled files . . . . . . 262Restoring licensed programs . . . . . . . . 263Restoring documents and folders . . . . . . . 264

Restore Document Library command options 264Using multiple concurrent document libraryobject commands . . . . . . . . . . . 264Output from the Restore Document LibraryObject Command . . . . . . . . . . . 264Considerations and restrictions . . . . . . 265

Moving documents . . . . . . . . . 265Searching tape files . . . . . . . . . 265Selecting files from DVD-RAM optical media 265Searching index database errors . . . . . 265Authority required to restore documentlibrary objects . . . . . . . . . . . 266How the system restores new documentlibrary objects . . . . . . . . . . . 266How the system restores existing documentlibrary objects . . . . . . . . . . . 266Size limitations when restoring documentlibrary objects . . . . . . . . . . . 266

Restoring folders . . . . . . . . . . . 266Renaming documents when restoring . . . . 267How the system restores descriptive informationfor document library objects . . . . . . . 267How the system restores authority andownership for document library objects . . . 267When to run the Rename Directory Entrycommand . . . . . . . . . . . . . 268When to run the Rename Document LibraryObject command . . . . . . . . . . . 268

Restoring objects in directories . . . . . . . 268Completing recovery for integrated servers . . . 271

Restoring IXS or IXA-attached integratedWindows servers . . . . . . . . . . . 271Restoring iSCSI-attached integrated servers . . 272Recovery for save operation of network serverstorage spaces . . . . . . . . . . . . 272Recovery for save operation of data in QNTCfile system . . . . . . . . . . . . . 273Recovering AIX, IBM i, or Linux in a logicalpartition . . . . . . . . . . . . . . 273

Recovering a Domino server . . . . . . . . 274Recovering an entire Domino server . . . . . 274Recovering Domino mail . . . . . . . . 274Recovering specific Domino databases . . . . 275Restoring changed objects to a Domino server 276

Example: Restoring changed Domino objectsfrom a cumulative backup . . . . . . . 276Example: Restoring changed Domino objectsfrom a nightly backup . . . . . . . . 276Example: Restoring Domino databases froman incremental backup . . . . . . . . 277Example: Restoring changed objects from aspecific Domino subdirectory . . . . . . 277

Restrictions when using the Restore command . . 278Restoring program temporary fixes (PTFs). . . . 281Restoring system information . . . . . . . . 281

vi IBM i: Recovering your system

||

Chapter 10. Restoring changedobjects and apply journaled changes . 283Task 1: Restoring changed objects . . . . . . 284

Restoring changed objects by library . . . . 284Restoring changed objects individually . . . . 284

Task 2: Restoring changed objects in directories . . 285Task 3: Determining whether you need to applyjournaled changes . . . . . . . . . . . . 286Task 4: Determining what journal receivers to use 286Task 5: Applying journaled changes for userjournals . . . . . . . . . . . . . . . 288Task 6: Applying journaled changes for theQAOSDIAJRN journal . . . . . . . . . . 290Task 7: Replaying journaled changes in a disasterrecovery . . . . . . . . . . . . . . . 290Task 8: Restoring changed documents and folders 291

Chapter 11. Mirrored protectionrecovery actions . . . . . . . . . . 293System actions for permanent errors. . . . . . 293Suspending mirrored units . . . . . . . . . 294Resuming mirrored units . . . . . . . . . 295Replacing a mirrored unit . . . . . . . . . 295

Using spare nonconfigured units forreplacement . . . . . . . . . . . . . 297Mirrored protection recovery actions performedby the service representative . . . . . . . 298

Actions when concurrent maintenance ispossible . . . . . . . . . . . . . 298Actions when concurrent maintenance is notpossible . . . . . . . . . . . . . 299

Other recovery considerations for mirroredprotection . . . . . . . . . . . . . 299Mirrored protection disk-error handling . . . 299Missing disk units . . . . . . . . . . . 300Saving a unit . . . . . . . . . . . . 301Restoring a unit . . . . . . . . . . . 301Active mirrored load source failure . . . . . 301

System cannot find active mirrored loadsource for initial program load . . . . . 301Active mirrored load source being used forinitial program load failure . . . . . . . 302Active mirrored load source fails late in theinitial program load (IPL) or at run time . . 303Cannot read system configuration data fromactive mirrored load source. . . . . . . 303

Unknown unit 1 status . . . . . . . . . 303Recovering the state of the unknown loadsource . . . . . . . . . . . . . . 304

Displaying incorrect Licensed Internal Codeinstallation . . . . . . . . . . . . . 304

Recovering remote load source mirroring . . . . 305Recovering after the remote load source hasfailed . . . . . . . . . . . . . . . 305Recovering after the local load source has failedon the system . . . . . . . . . . . . 305

Dedicated recovery of local load source Local system is still functional . . . . . . 306Dedicated recovery from remote disk units After a local site disaster . . . . . . . 306

Using the recover mirrored load source function 306

Chapter 12. Restoring your systemusing Operational Assistant tapes . . 309Restoring your libraries . . . . . . . . . . 310Restoring libraries that you saved by using abackup list . . . . . . . . . . . . . . 311Restoring changed objects that you saved by usingOperational Assistant. . . . . . . . . . . 312

Chapter 13. Restoring encryptedbackups and encrypted auxiliarystorage pools . . . . . . . . . . . 313Recovering from an encrypted backup usingsoftware encryption . . . . . . . . . . . 313Recovering from an encrypted backup using anencrypted tape . . . . . . . . . . . . . 314Backing up the Encryption Key Manager . . . . 314Restoring encrypted auxiliary storage pools . . . 315

Part 3. Release-to-release support 317

Chapter 14. Release-to-releasesupport . . . . . . . . . . . . . . 319Current release to previous release support . . . 319

Creating the object for the previous release . . 320Saving the object for the previous release . . . 321Testing the object on the current release . . . 327Restoring and using the object on the previousrelease. . . . . . . . . . . . . . . 327Restrictions for current release to previousrelease support . . . . . . . . . . . . 327

Previous release to current release support . . . 327Considerations when moving systemcustomization information . . . . . . . . 328Restoring previous release user data to a newsystem . . . . . . . . . . . . . . 328

Prerequisites for the recovery . . . . . . 331Restoring previous release user data to a newsystem . . . . . . . . . . . . . 331Saving spooled files . . . . . . . . . 344

Restrictions when going from previous releaseto current release . . . . . . . . . . . 345

Chapter 15. System synchronization:Planning and procedures . . . . . . 347Synchronization methods: Overview. . . . . . 348Moving changed objects . . . . . . . . . . 349

Saving changed objects . . . . . . . . . 350Restoring changed objects . . . . . . . . 351Problems when restoring changed objects . . . 352

Problems restoring journal receivers . . . . 352Problems restoring database file members 353Problems with object authority or ownership 354

Moving entire libraries . . . . . . . . . . 354Considerations for moving entire libraries . . . 355

Moving individual objects . . . . . . . . . 356Applying journaled changes . . . . . . . . 356

Contents vii

Refreshing your new system . . . . . . . . 358Additional synchronization tips . . . . . . . 359

Part 4. Tips for merging two ormore IBM i operating systems. . . 361

Chapter 16. Tips for merging twosystems into a single system . . . . 363Guidelines for restoring information from thedevelopment system . . . . . . . . . . . 363

Part 5. Alternate Installation device 365

Chapter 17. Using an alternateinstallation device . . . . . . . . . 367Alternate installation device: Overview . . . . . 367Setting up an alternate installation device . . . . 367Disabling an alternate installation device . . . . 370Verifying and selecting an alternate installationdevice during a manual installation . . . . . . 370

Part 6. Disk configuration andprotection . . . . . . . . . . . . 373

Chapter 18. Configuring disks anddisk protection. . . . . . . . . . . 375Choosing the right procedure for configuring disks 375

Checklist 1: Configuring disks on a new system 376Checklist 2: Adding disk units without deviceparity protection . . . . . . . . . . . 377Checklist 3: Adding disk units to an existinginput/output adapter . . . . . . . . . 378Checklist 4: Adding a new input/outputadapter . . . . . . . . . . . . . . 379Checklist 5: Moving disk units between nonmirrored auxiliary storage pools . . . . . . 380Checklist 6: Moving disk units betweenmirrored auxiliary storage pools . . . . . . 381Checklist 7: Deleting an auxiliary storage pool 383Checklist 8: Removing disk units without deviceparity protection . . . . . . . . . . . 384Checklist 9: Removing disk units that havedevice parity protection from an auxiliarystorage pools without mirrored protection . . . 384Checklist 10: Removing disk units that havedevice parity protection from an auxiliarystorage pool with mirrored protection . . . . 385Using system service tools and dedicatedservice tools . . . . . . . . . . . . . 387

Starting dedicated service tools . . . . . 387Stopping dedicated service tools . . . . . 389Starting system service tools . . . . . . 389Stopping system service tools . . . . . . 390

Displaying your disk configuration . . . . . 390Displaying your disk configuration(hardware view) . . . . . . . . . . 390

Displaying disk hardware configuration(command method) . . . . . . . . 390Displaying disk hardware configuration(DST method) . . . . . . . . . . 391

Displaying your disk configuration (softwareview) . . . . . . . . . . . . . . 392Disk configuration and status displays . . . 393

Chapter 19. Working with auxiliarystorage pools . . . . . . . . . . . 395Adding disk units to an existing auxiliary storagepool . . . . . . . . . . . . . . . . 395Creating an unencrypted auxiliary storage pool 398Creating an encrypted auxiliary storage pool . . . 400Changing the storage threshold for an auxiliarystorage pool . . . . . . . . . . . . . . 402Changing the storage threshold for the systemauxiliary storage pool . . . . . . . . . . 403Moving a disk unit to a different auxiliary storagepool . . . . . . . . . . . . . . . . 405Removing a disk unit from an auxiliary storagepool . . . . . . . . . . . . . . . . 407Deleting an auxiliary storage pool . . . . . . 409Calculating space requirements for an auxiliarystorage pool . . . . . . . . . . . . . . 410Displaying the objects in a user auxiliary storagepool . . . . . . . . . . . . . . . . 410Balancing an auxiliary storage pool . . . . . . 411

Capacity balancing . . . . . . . . . . 411Usage balancing . . . . . . . . . . . 411Hierarchical storage management balancing . . 411Media preference balancing . . . . . . . 412

Transferring objects between auxiliary storagepools . . . . . . . . . . . . . . . . 412

Transferring a library to a different auxiliarystorage pool . . . . . . . . . . . . . 412Transferring a folder to a different auxiliarystorage pool . . . . . . . . . . . . . 413Transferring journals and objects to a differentauxiliary storage pool . . . . . . . . . 413Creating objects in a library user auxiliarystorage pool . . . . . . . . . . . . . 414

Example: Placing a document in a basicauxiliary storage pool . . . . . . . . 415Example: Placing an object in a user auxiliarystorage pool . . . . . . . . . . . . 415Example: Creating a user-defined file systemin user auxiliary storage pool . . . . . . 415

Placing journal receivers in a user auxiliarystorage pool . . . . . . . . . . . . . 415

Placing journal receivers in a user auxiliarystorage pool . . . . . . . . . . . . 416

Moving journal receivers from an overflowedbasic user auxiliary storage pool . . . . . . 416Resetting a journal with a status of overflowed 417

Working with nonlibrary user auxiliary storagepools . . . . . . . . . . . . . . . . 418

Creating objects in a nonlibrary user auxiliarystorage pool . . . . . . . . . . . . . 418Transferring an object to a nonlibrary auxiliarystorage pool . . . . . . . . . . . . . 419

viii IBM i: Recovering your system

Transferring a journal to a nonlibrary userauxiliary storage pool . . . . . . . . . 419

Placing journal receivers in a nonlibrary basicauxiliary storage pool . . . . . . . . 420

Chapter 20. Working with deviceparity protection . . . . . . . . . . 421Starting device parity protection . . . . . . . 421

Starting device parity protection for aninput/output adapter . . . . . . . . . 421

Stopping device parity protection. . . . . . . 423Stopping device parity protection on aninput/output adapter . . . . . . . . . 423

Removing disk units that have device parityprotection for System i while powered on . . . . 424Removing disk units that have device parityprotection for System i while powered off . . . . 426Removing disk units that have device parityprotection for a IBM i . . . . . . . . . . 428Including a disk unit in device parity protection 430Excluding a disk unit from device parity protection 431Displaying device parity status . . . . . . . 432

Chapter 21. Working with mirroredprotection . . . . . . . . . . . . . 435Mirrored protection: Configuration rules . . . . 435Starting mirrored protection . . . . . . . . 435

What the system does when you start mirroredprotection . . . . . . . . . . . . . 437

Mirrored protection configuration errors . . . . 438Stopping mirrored protection . . . . . . . . 438

Chapter 22. Working with diskcompression. . . . . . . . . . . . 441Introduction to disk compression . . . . . . . 441

Restrictions and considerations . . . . . . 441Disk compression and capacity . . . . . . 442Disk unit full considerations . . . . . . . 443How the system responds to disk unit full 448reference code A6xx 0277 . . . . . . . . 444

SRC code A6xx 0277 . . . . . . . . . . . 445User action 1 . . . . . . . . . . . . 445User action 2 . . . . . . . . . . . . 445User action 3 . . . . . . . . . . . . 446User action 4 . . . . . . . . . . . . 446Examples of A6xx 0277 . . . . . . . . . 447

Starting disk compression . . . . . . . . . 447Stopping disk compression . . . . . . . . . 449Procedural sequences for configuring disks andprotection . . . . . . . . . . . . . . 451

Checklist: Adding a new I/Ocompression-capable storage controller . . . . 451Checklist: Adding disk units to an existingcompression-capable storage controller . . . . 452Checklist: Moving disk units from the systemASP to a user ASP. . . . . . . . . . . 453

Recovering from error codes . . . . . . . . 454Recovering from SRC 6xxx 7051 . . . . . . 454Recovering from SRC 6xxx 7052 . . . . . . 455

Chapter 23. Managing auxiliarystorage pools . . . . . . . . . . . 457Working with ASP trace and ASP balance . . . . 457

Capacity balance . . . . . . . . . . . 458Hierarchical storage management (HSM)balance . . . . . . . . . . . . . . 459Usage balance . . . . . . . . . . . . 459Auxiliary storage pool trace . . . . . . . 460

Determining adequate disk storage . . . . . . 460

Part 7. Backup and recovery toolsand techniques. . . . . . . . . . 463

Chapter 24. Examples: Techniquesand programming for backup andrecovery . . . . . . . . . . . . . 465Examples: Backup and recovery . . . . . . . 465

Using the Retrieve Journal Entry command in aprogram . . . . . . . . . . . . . . 465Control language program to handle escapeconditions . . . . . . . . . . . . . 465Writing output to save media using the ReceiveJournal Entry command . . . . . . . . . 467

Considerations when writing to tape . . . 467Journal entries written to an intersystemcommunications function file . . . . . . 469

Part 8. Appendixes . . . . . . . . 471

Appendix A. Licensed Internal Codeinstallation error displays . . . . . . 473

Appendix B. Example: Disasterrecovery plan . . . . . . . . . . . 481Section 1. Example: Major goals of a disasterrecovery plan . . . . . . . . . . . . . 481Section 2. Example: Personnel . . . . . . . . 481Section 3. Example: Application profile . . . . . 482Section 4. Example: Inventory profile . . . . . 482Section 5. Information services backup procedures 483Section 6. Disaster recovery procedures. . . . . 483

Disaster action checklist . . . . . . . . . 484Recovery startup procedures for use after actualdisaster . . . . . . . . . . . . . . 484

Section 7. Recovery plan for mobile site . . . . 485Mobile site setup plan . . . . . . . . . 486Communication disaster plan . . . . . . . 486Electrical service . . . . . . . . . . . 486

Section 8. Recovery plan for hot site . . . . . . 486Alternate-site system configuration . . . . . 487

Section 9. Restoring the entire system . . . . . 487Section 10. Rebuilding process. . . . . . . . 487Section 11. Testing the disaster recovery plan . . . 488Section 12. Disaster site rebuilding . . . . . . 489

Vendors . . . . . . . . . . . . . . 490Floor plan . . . . . . . . . . . . . 490

Section 13. Record of plan changes . . . . . . 490

Contents ix

Appendix C. Recovering your system 491

Appendix D. Recovering your systemto a different system . . . . . . . . 505

Notices . . . . . . . . . . . . . . 519Programming interface information . . . . . . 521

Trademarks . . . . . . . . . . . . . . 521Terms and conditions. . . . . . . . . . . 521

Bibliography. . . . . . . . . . . . 523

Index . . . . . . . . . . . . . . . 525

x IBM i: Recovering your system

Figures

1. Save commands and menu options . . . . . 42. ObjectConnect job flow . . . . . . . . 193. Restore procedures . . . . . . . . . . 264. Save procedures and restore procedures for file

systems . . . . . . . . . . . . . . 275. User ASP configuration before failure 1736. Basic user ASP configuration after restoring

operating system . . . . . . . . . . 1757. User ASP configuration after reclaiming

storage. . . . . . . . . . . . . . 1768. User ASP configuration after recovering

isolated journal receiver . . . . . . . . 1789. Restore menufirst display . . . . . . . 201

10. Sample job log for RSTAUT on a system in arestricted state . . . . . . . . . . . 221

11. Expanded text for message CPF3736 . . . . 22112. Expanded text for message CPF3845 . . . . 22113. Sample job log for RSTAUT on a system in a

nonrestricted state . . . . . . . . . . 22214. Expanded text for message CPF3845 . . . . 22215. Save data from an independent ASP and

restore it to an independent ASP with anidentical name . . . . . . . . . . . 226

16. Save data from *SYSBAS and restore it to anindependent ASP . . . . . . . . . . 227

17. Save data from an independent ASP andrestore it to an independent ASP with adifferent name . . . . . . . . . . . 228

18. Save data from an independent ASP andrestore it to *SYSBAS . . . . . . . . . 229

19. Example: Restoring a journaled object to adifferent library . . . . . . . . . . . 240

20. Example of a database file with two members 24321. Restoring a copy of a file . . . . . . . 24322. Restoring database files with different

creation dates . . . . . . . . . . . 24523. Restoring database files with different

creation dates . . . . . . . . . . . 24624. Restoring access paths . . . . . . . . 25025. Restoring a referential constraint network 25326. An object with hard linksExample . . . . 27027. An object with a symbolic linkExample 27128. Sample recovery time line . . . . . . . 28329. Receiver directorySaving attached receivers 28730. Receiver directorySaving detached receivers 28731. How the system is saved with Operational

Assistant backup . . . . . . . . . . 31032. Recovery steps for restoring previous release

user data to a new system . . . . . . . 33033. Overview of synchronization process 34834. Display hardware resource listing . . . . . 39135. Program for retrieving journal entries 46536. Program for writing the RCVJRNE command

output to save media . . . . . . . . . 467

Copyright IBM Corp. 1997, 2015 xi

xii IBM i: Recovering your system

Tables

1. Spooled files created by the system . . . . 162. ObjectConnect and associated IBM i save and

restore commands . . . . . . . . . . 183. Basic components of ObjectConnect . . . . 184. Relationship between save and restore

commands . . . . . . . . . . . . . 275. Restoring objects with ALWOBJDIF . . . . 296. Possible values for the OPTION parameter of

the ENDSBS command. . . . . . . . . 337. Resolving problems detected by the RCLSTG

procedure . . . . . . . . . . . . . 368. Possible values for the QALWOBJRST system

value. . . . . . . . . . . . . . . 419. Lock type needed for restore operation 44

10. QASRRSTO (restore output file) information 5011. Choosing the correct recovery procedure for

disk media failure . . . . . . . . . . 6312. Recovery checklist for disk failureChecklist 1 6513. Recovery checklist for disk failureChecklist 2 6614. Recovery checklist for disk failureChecklist 3 6715. Recovery checklist for disk failureChecklist 4 6816. Recovery checklist for disk failureChecklist 5 7217. Recovery checklist for disk failureChecklist 6 7518. Recovery checklist for disk failureChecklist 7 7619. Recovery checklist for disk failureChecklist 8 7720. Recovery checklist for disk failureChecklist 9 7921. Recovery checklist for disk failureChecklist 10 8222. Recovery checklist for disk failureChecklist 11 8623. Recovery checklist for disk failureChecklist 12 8724. Recovery checklist for disk failureChecklist 13 8925. Recovery checklist for disk failureChecklist 14 9126. Recovery Checklist for disk failureChecklist

15 . . . . . . . . . . . . . . . . 9127. Recovery checklist for disk failureChecklist 16 9228. Recovery checklist for disk failureChecklist 17 9329. Recovery checklist for disk failureChecklist 18 9430. Recovery checklist for disk failureChecklist 19 9531. Recovery checklist for complete system

lossChecklist 20 . . . . . . . . . . . 9732. Recovery checklist for complete system

lossChecklist 21 . . . . . . . . . . 10033. Recovery checklist for complete system

lossChecklist 22 . . . . . . . . . . 10434. Recovery checklist for failed cache

cardChecklist 23 . . . . . . . . . . 10635. Choosing the correct recovery procedure for

user information . . . . . . . . . . 10836. Checklist for recovering user information

using commands . . . . . . . . . . 10937. Checklist for recovering user information

using option 21 . . . . . . . . . . . 11338. Checklist for recovering user information

using options 22 and 23 . . . . . . . . 11539. Checklist for recovering user information

using Operational Assistant backup tapes . . 118

40. Options from the Install the Licensed InternalCode (LIC) Menu . . . . . . . . . . 123

41. SRC codes when loading the LicensedInternal Code . . . . . . . . . . . 127

42. Configuring disk while installing theoperating system . . . . . . . . . . 148

43. Recovery for damaged objects by object type 16844. Object types that require special procedures

for deleting . . . . . . . . . . . . 18545. Tasks for restoring basic ASP objects . . . . 18946. Example of restore order for independent

ASPs saved with GO SAVE: Option 21 or 23 . 19447. Tasks for restoring independent ASP objects 19448. Commands for changing system information 20949. How user profiles are restored . . . . . . 21150. Copying user profiles without affecting the

Digital Certificate Manager information . . . 21251. Results of restoring user profiles . . . . . 21352. Restoring an object linked to an authorization

list . . . . . . . . . . . . . . . 21653. Saving and restoring private authorities using

the PVTAUT parameter . . . . . . . . 21854. How configuration objects are restored 22955. Methods for restoring all librariessingle save

operation . . . . . . . . . . . . . 23656. Methods for restoring all librariesmultiple

save operations . . . . . . . . . . . 23657. Restoring a file network . . . . . . . . 25158. Restoring files that have trigger programs 25459. Save and restore spooled files . . . . . . 26260. Restoring objects that have hard links 27061. Using the RST Command for QSYS.LIB

Objects. . . . . . . . . . . . . . 27962. New name options on the RST

commandExamples . . . . . . . . . 28063. Restore procedures for changed objects 28464. Values for TGTRLS parameter . . . . . . 31965. Language support for the target release

parameter. . . . . . . . . . . . . 32066. Previous-release support by object type 32267. Comparison of synchronization methods 34968. Choosing the right disk procedure . . . . 37569. Configuring disks on a new systemTasks 37670. Adding disk units without device parity

protectionTasks . . . . . . . . . . 37871. Adding disk units to an existing IOATasks 37972. Adding a new IOATasks . . . . . . . 38073. Moving disk units between ASPsTasks 38174. Moving disk units between ASPs with

mirrored protectionTasks . . . . . . . 38275. Deleting an user ASPTasks. . . . . . . 38376. Removing disk units that do not have device

parity protectionTasks . . . . . . . . 38477. Removing disk units from an IOA and a

non-mirrored ASPTasks . . . . . . . . 385

Copyright IBM Corp. 1997, 2015 xiii

78. Removing disk units from an IOA and amirrored ASPTasks . . . . . . . . . 386

79. Word formats for SRC codes . . . . . . 44580. Adding a new I/O storage controller and

disk units . . . . . . . . . . . . . 45181. Adding compressed disk units to an existing

storage controller . . . . . . . . . . 452

82. Moving disk units from the system ASP to auser ASP . . . . . . . . . . . . . 453

83. Checklist for testing the disaster recoveryplan . . . . . . . . . . . . . . 488

xiv IBM i: Recovering your system

Recovering your system

This topic provides general information about backup and recovery options for the IBM i environment.It describes the options available on the system, compares and contrasts them, and tells where to findmore information about them.

This topic covers the following information:v Procedures on how to save your system using the GO SAVE commands.v Restoring to a different release of IBM i.v Selecting the right recovery strategy.v Procedures for restoring information to your system.v Device parity protection procedures.v Mirrored protection procedures.Related information:Backing up your system

Copyright IBM Corp. 1997, 2015 xv

xvi IBM i: Recovering your system

What's new for IBM i 7.3

Read about new or significantly changed information for the Recovering your system topic collection.

Recovery enhancements

Authorization list links for objects in the QSYS library are now preserved during a system recovery. Formore information, see What you should know about restoring user profiles on page 214.

Information has been added about restoring database files. See Restoring physical files that aretemporal on page 255.

Performance enhancements

An object may now be restored faster when you use the Starting position in file (POSITION) parameteron the RST and RSTOBJ commands and the QSRRSTO and QsrRestore APIs. For more information, seeRestoring objects on page 236.

How to see what's new or changed

To help you see where technical changes have been made, this information uses:v The

image to mark where new or changed information begins.

v The

image to mark where new or changed information ends.

In PDF files, you might see revision bars (|) in the left margin of new and changed information.

To find other information about what's new or changed this release, see the Memo to users.Related information:Backing up your system

Copyright IBM Corp. 1997, 2015 xvii

|

||

||

|

|||

xviii IBM i: Recovering your system

Part 1. Saving information on your system

Copyright IBM Corp. 1997, 2015 1

2 IBM i: Recovering your system

Chapter 1. Saving the system

If this is your first experience with your IBM i model, use the instructions in this topic collection to saveall of the information about your system. Do this with the GO SAVE menu options.

You can browse the Backing up your system topic in IBM i Information Center, or print a copy of theinformation about how to back up your entire system.

Overview of the GO SAVE commandUse the GO SAVE command to save your entire system or parts of your system that change regularly.

Using the GO SAVE command is a simple way to make sure that you have a good backup of your entiresystem. The GO SAVE command presents you with Save menus that make it easy to back up yoursystem, no matter what backup strategy you decide to use. It is a good idea to use menu option 21 of theGO SAVE command right after you install your system.

Menu option 21 of the GO SAVE command is the basis for all save strategies. This option allows you toperform a complete save of all the data on your system. Once you have used menu option 21, you canuse other menu options to save parts of the system, or to use a manual save process.

Another save method uses Backup, Recovery, and Media Services (BRMS), which automates your saveprocesses. BRMS provides a comprehensive and easy solution for your backup and recovery needs.

Important: Be sure to permanently apply all Licensed Internal Code PTFs (fixes) before using theSAVSYS command, or the GO SAVE menu option 21 or 22.

The following figure illustrates the commands and menu options you can use to save the parts of thesystem and the entire system.

Copyright IBM Corp. 1997, 2015 3

GO SAVE command menu optionsThis information describes the GO SAVE command and the most common menu options that you canuse.

Figure 1. Save commands and menu options


Access the GO SAVE command menu by typing GO SAVE from any command line. From the Save menu,you see option 21, option 22, and option 23 along with many more save options.

SAVE SaveSystem: SYSTEMA

Select one of the following:

Save Data1. Files2. Libraries3. Documents and folders4. Programs5. Other objects6. Changed objects only7. Licensed programs8. Security data

10. Configuration11. Objects in directories

More...Selection or command===>

F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information AssistantF16=System Main menu

SAVE SaveSystem: SYSTEMA

Select one of the following:

Save System and User Data20. Define save system and user data defaults

++ 21. Entire system++ 22. System data only+ 23. All user data

Save Document Library Objects30. All documents, folders, and mail31. New and changed documents, new folders, all mail32. Documents and folders33. Mail only

More...Selection or command===>

F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information AssistantF16=System Main menu

A single plus sign (+) indicates that the option places your system into a restricted state if you run itwithout prompting for commands, which means that nothing else can be running on your system whenthe menu option is selected. If you do prompt for commands, you can skip the ENDSBS command thatplaces the system in restricted state.

A double plus sign (++) indicates that your system must be in a restricted state to run this option. Youcannot skip the ENDSBS command that runs as part of the option.

The options that place your system into a restricted state (options 21, 22, 23, and 40) also end TCP priorto ending the subsystems. Commands issued as part of these options are:v ENDTCPSVRv ENDHOSTSVRv DLYJOBv ENDTCP

Chapter 1. Saving the system 5

v DLYJOBv ENDSBS SBS(*ALL)

The two Delay job (DLYJOB) commands allow time for TCP processing to end. You can choose theamount of time that each DLYJOB command waits. The default value is 300 seconds for a total delay of10 minutes before the End subsystem (ENDSBS) command is run.

GO SAVE: Option 21 (saving the entire system)Option 21 saves everything on your system and allows you to perform the save while you are not there.

Option 21 saves all of your data for additional licensed programs, such as a Domino server or anintegrated server that uses the IBM i Integrated Server Support option, when you select to vary off yournetwork server. You also can back up data that is stored on a logical partition. If you have Linux or AIX

installed on a guest logical partition, you can back up that partition when you vary off your networkserver.

Option 21 puts your system into a restricted state. This means that when the save begins, no users canaccess your system and the backup is the only thing that is running on your system. It is best to run thisoption overnight for a small system or during the weekend for larger system. If you schedule anunattended save, make sure your system is in a secure location; after you schedule the save, you will notbe able to use the workstation where the backup is initiated until the save is complete.

Note: If you are saving information on independent ASPs (also called independent disk pools in Systemi Navigator), make sure that you have varied on the independent ASPs that you want to save beforeusing option 21.

If you have set the save/restore master key when you do a full system save, the master key also getssaved.

Tip: If you are using the Hardware Management Console (HMC), you can perform system saves usingOption 21 while you are at a remote location. For example, you can open a shared console on your HMCfrom your office, travel to another location and link to the shared session from there.

OptionNumber

Description Commands

21Entire server (QMNSAVE)

ENDTCPSVRENDHOSTSVRDLYJOBENDTCPDLYJOBENDSBS SBS(*ALL) OPTION(*IMMED)CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK or *NOTIFY)SAVSYSSAVLIB LIB(*NONSYS) ACCPTH(*YES)SAVDLO DLO(*ALL) FLR(*ANY)SAV DEV(/QSYS.LIB/media-device-name.DEVD) +

OBJ((/*) (/QSYS.LIB *OMIT) +(/QDLS *OMIT))1 UPDHST(*YES)

STRSBS SBSD(controlling-subsystem)1The command omits QSYS.LIB file system because the SAVSYS command and the SAVLIB LIB(*NONSYS) commandboth save it. The command omits the QDLS file system because the SAVDLO command saves it.

Performing a complete save using the GO SAVE checklist on page 7 provides you with step-by-stepinstructions on how to save your entire system with menu option 21 of the GO SAVE command.


Performing a complete save using the GO SAVE checklistUse this checklist to perform a complete save operation.

Use the following checklist for menu options 21, 22, and 23 of the GO SAVE command. Whenappropriate, select the option that you require. If you choose to, you can print system information duringthe procedure. The Printing system information topic contains detailed instructions on how to printsystem information if you do not want the Save menu option command to print your system informationautomatically.

Some of the steps in this checklist might not apply to your system configuration. See Identify optionalfeatures that affect your backup for help to determine whether you use optional features in yourenvironment. If you are still unsure how your system is configured, contact your system administrator.

Attention: If you are using the Hardware Management Console (HMC), you must back up the HMC inaddition to using the GO SAVE: Option 21 to obtain a complete save of your system. See Backing up andrestoring the HMC.

If you need to restore the entire POWER blade server, you must back up the Virtual I/O Server, whichalso contains Integrated Virtualization Manager, in addition to using the GO SAVE: Option 21 command.Virtual I/O Server must be restored on the blade server before you can restore any IBM i client logicalpartitions. For saving and restoring Virtual I/O Server, see the PowerVM Editions Operations Guide.1. If you are using software encryption for backup tapes and saving system data (GO SAVE option 21

or 22), set the save/restore master key before you perform the save operation. The save/restoremaster key is a special purpose master key used to encrypt all the other master keys when savingthem in a SAVSYS or GO SAVE operation. For the instructions, see Loading and setting thesave/restore master key.

2. Sign on with a user profile that has *SAVSYS and *JOBCTL special authorities, and also has sufficientauthority to list different types of system resources. (The QSECOFR user profile contains all of theseauthorities.) This ensures that you have the authority that you need to place the system in thenecessary state and to save everything.

3. If you want to exclude virtual images from a full-system save, use one of the following strategies.Virtual images can significantly increase the time it takes to complete an Option 21 save operation,even if the image catalog entries do not contain data:v Use the Change Attribute (CHGATR) command to mark the image catalog directory as

nonsavable. For example:CHGATR OBJ(/MYINFO) ATR(*ALWSAV) VALUE(*NO)

v Use the Load Image Catalog (LODIMGCLG) command to make the image catalog ready. Imagecatalogs with a ready status are omitted from the save operation.

v In an attended save, you can specify to omit the image catalog directories on the Save Object(SAV) command.

4. If you have independent auxiliary storage pools (ASPs), make them available if you want them to beincluded in an Option 21 or 23 save operation.

Note: If your system includes independent ASPs that are geographically mirrored, it isrecommended that you eliminate them from this GO SAVE option by making them unavailable. Youmust save independent ASPs that are geographically mirrored separate from this GO SAVEoperation.

If the geographically mirrored ASPs remain available during the GO SAVE operation, geographicmirroring is suspended when the system becomes restricted. When you resume mirroring after thesave, a complete synchronization is required. Synchronization can be a lengthy process.


http://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?topic=/iphai_p5/backingupthehmc.htmhttp://publib.boulder.ibm.com/infocenter/systems/scope/hw/index.jsp?topic=/iphai_p5/backingupthehmc.htm

5. If you are operating in a clustered environment and want to save independent ASPs without causinga failover, or you want to save the cluster environment for a node, you must end the device clusterresource group and end clustering before you end subsystems.Use the End Cluster Resource Group (ENDCRG) command and the End Cluster Node(ENDCLUNOD) command.

6. If you have OptiConnect controllers, vary them off before the save operation. You must vary offOptiConnect controllers before ending subsystems and performing a save of the entire system, orbefore any save that ends the QSOC subsystem. If you do not vary off OptiConnect controllersbefore ending subsystems, they go into a failed status, the system marks them as damaged, and thesystem does not save them.

7. If you have WebSphere MQ for IBM i (5724-H72), you need to quiesce WebSphere MQ before yousave the system. For information about WebSphere MQ documentation, see WebSphere MQ

(www.ibm.com/software/integration/wmq/library/library53.html).8. If you plan to run the save procedure immediately, make sure that no jobs are running on thesystem, type the Work with Active Jobs (WRKACTJOB) command.If you plan to schedule the save procedure to run later, send a message to all users informing themwhen the system will be unavailable.

9. To perform an attended save of your system, go to step 11.10. To perform an unattended save operation, continue with the following steps. An unattended save

operation prevents your save operation from stopping because of unanswered messages:a. Display the reply list sequence numbers to find what numbers are available for use:

WRKRPYLE

b. If MSGID(CPA3708) is not already in your reply list, add it. For xxxx, substitute an unusedsequence number from 1 through 9999:ADDRPYLE SEQNBR(xxxx) +

MSGID(CPA3708) +RPY(G)

c. If you are using virtual media for your save media, specify automatic load in the reply list,MSGID(OPT149F), to avoid receiving a message that interrupts the unattended save operation. Ifnecessary, virtual media will use the autoload feature to create additional images with the samecapacity as the last image you loaded, provided the disk storage is available.

d. Change your job to use the reply list and to notify you of any break messages that are sent:CHGJOB INQMSGRPY(*SYSRPYL) BRKMSG(*NOTIFY)

Note: You can also set up a default so that whenever you select menu options 21, 22, or 23, thesystem will always use the reply list. To set up the default, select menu option 20 from the Savemenu. Specify Yes on the Use system reply list option.

11. Type GO SAVE at a command prompt to display the Save menu.12. Select the option (21, 22, or 23) from the Save menu and press the Enter key.

A prompt display describes the function of the menu option that you selected.13. After reading the Specify Command Defaults prompt display, press the Enter key to continue.


http://www.ibm.com/software/integration/wmq/library/library53.html

14. Type your choices for the Devices prompt. You can specify as many as four tape media device names.If you specify more than one device, the system automatically switches to the next tape device whenthe current tape is full. You can select only one DVD-RAM optical media device, tape media librarydevice, or virtual tape device.The first device for options 21 and 22 must be your alternate IPL device. If you are creating media toinstall on another system, the device must be compatible with the alternate IPL device for thatsystem. This ensures that the system can read the SAVSYS media if you need to restore yourLicensed Internal Code and the operating system.

15. Type your choice for the Prompt for commands prompt. Specify N (No) if you want to run anunattended save operation. Specify Y (Yes) if you want to change the defaults on the SAVxxcommands.

16. Type your choice for the Check for active files prompt. Specify Y (Yes) if you want the system to warnyou if active files exist on the save media. The warning you receive gives the following choices:v Cancel the save operation.v Insert new media and try the command again.v Initialize the current media and try the command again.

Note: If you use DVD-RAM optical media for your save, the system sends inquiry messages to theQSYSOPR message queue when it encounters identical active files. The system sends the inquiry

Specify Command Defaults

Type choices, press Enter.

Devices . . . . . . . . . . . TAP01 Names______________________________

Prompt for commands . . . . . Y Y=Yes, N=No

Check for active files . . . . Y Y=Yes, N=No

Message queue delivery . . . . *BREAK *BREAK, *NOTIFY

Start time . . . . . . . . . . *CURRENT *CURRENT, time

Start date . . . . . . . . . . *CURRENT *CURRENT, date

Vary off network servers . . . *ALL *ALL, *NONE

More...F3=Exit F12=Cancel

Specify Command Defaults

Type choices, press Enter.

Unmount file systems . . . . . Y Y=Yes, N=No

Print system information . . . N Y=Yes, N=No

Use system reply list . . . . N Y=Yes, N=No

Spooled file data . . . . . . *NONE *NONE, *ALL

End TCP/IP wait time . . . . . 300 *NONE, 1-9999 seconds

Print joblog . . . . . . . . . Y Y=Yes, N=No


||||||||||||||||||||||||

||||||||||||||||

message for each identical active file that it finds.Specify N (No) if you want the system to write over any active files on the save media withoutwarning you.

17. Type your choice for the Message queue delivery prompt. Specify *NOTIFY if you want to do anunattended save operation. This prevents communications messages from stopping the saveoperation. If you specify *NOTIFY, severity 99 messages that are not associated with the saveoperation are sent to the QSYSOPR message queue without interrupting the save process. Forexample, messages that request that a new volume be loaded interrupt the save operation becausethey are associated with the job. You cannot continue until you reply to these messages.Specify *BREAK if you want to be interrupted for severity 99 messages that require a reply.

18. Type your choices for the Start time and Start date prompts. To start the save operation immediately,specify *CURRENT for both prompts. You can schedule the start of the save operation up to 7 daysfrom the current job date and time.

Note:

a. The system uses the Delay Job (DLYJOB) command to schedule the save operation. Yourworkstation will be unavailable from the time you request the menu option until the saveoperation is completed.

b. Make sure that your workstation is in a secure location. Your workstation remains signed on,waiting for the job to start. If the system request function is used to cancel the job, yourworkstation displays the Save menu. The workstation remains signed on with your user profileand your authority.

c. Make sure that the value for the QINACTITV system value is *NONE. If the value forQINACTITV is other than *NONE, the workstation will vary off in the amount of time specified.If you changed the value to *NONE, write the old value down.

d. If you specify a delayed start and want your save operation to run unattended, be sure you havedone the following:v Set up the system reply list.v Specified *NONE on QINACTITV system value.v Specified *NOTIFY on message queue delivery.v Specify *NOTIFY for any break messages.v Responded N to the Prompt for commands prompt.v Responded N to Check for active files.

19. Type your choice for the Vary off network servers prompt. If you use integrated servers, you canoptionally vary off the network server descriptions before beginning the save procedure. Examples ofnetwork servers include Windows or VMware using Integrated Server Support (5770-SS1 Option 29)or running an IBM i partition hosting an IBM i, Linux, or AIX guest partition.Select one of the following options to specify which hosted network servers need to be varied offbefore starting the save operation and varied on after completing the save operation:

*NONEDoes not vary off network servers. No data is saved for the network servers because thesystem is in a restricted state. Saving the individual objects requires an active connection tothe system.

*ALL Varies off all network servers before starting the save operation. The save operation takesless time but the network server data is not saved in a format that allows restoration ofindividual objects. You can only restore all of the data from the network servers.

20. Type your choice for the Unmount file system prompt. Specify Y (Yes) if you want to allow alldynamically mounted file systems to be unmounted. This step enables you to save user-defined filesystems (UDFSs) and their associated objects.

Note: After the save operation is completed, the system attempts to remount the file systems.


|||

|

Specify N (No) if you do not want all dynamically mounted file systems to be unmounted. The filesystem attributes for the UDFS are saved for all UDFSs that are saved when mounted. To rebuildthese mounted file UDFSs during a restore, you must specify the RBDMFS(*UDFS) parameter on theRST command.

21. Type your choice for the Print system information prompt. Specify Y (Yes) if you want to print thesystem information. The system information might be useful for disaster recovery. The "Printingsystem information" topic explains how to print your system information manually without usingthe automatic GO SAVE command menu option function.

22. Type your choice for the Use system reply list prompt. Specify Y (Yes) if you want to use the systemreply list when the system sends an inquiry message.

23. Type your choice for the Spooled file data prompt. Specify whether this backup should save spooledfile data for output queues that are saved. The possible choices are:

*NONENo spooled file data is saved.

*ALL For each output queue that is saved, all available spooled file data on the output queue issaved.

Note: Saving spooled files might require more save media and will take additional time.24. Type your choice for the End TCP/IP wait time prompt. Specify the number of seconds to delay the

job to allow TCP/IP processing to end before ending all subsystems. Specify *NONE to end allsubsystems without ending TCP/IP processing first.

25. Type your choice for the Print joblog prompt. Specify Y (Yes) if you want to print the joblog when themenu operation ends.

26. Press the Enter key. If you chose a later start date or time, your display shows a message that tellswhen the save operation will start. You cannot use the display until the save operation is completed.The input-inhibited indicator might appear. You have completed the steps for setting up the saveoperation.If you did not choose a later start date or time, continue with step 27. If the value for QSYSOPRmessage queue delivery is *BREAK with a severity level of 60 or lower, you must respond to theEnd Subsystem (ENDSBS) messages. This is true even if you plan to run an unattended saveoperation specifying a start date and time of *CURRENT.

27. If you responded Y to the system prompt, Prompt for commands, the End Subsystem displayappears after TCP has ended. Type any changes and press the Enter key. While the system is endingsubsystems, you see the following messages. You must respond to them if the QSYSOPR messagequeue is set to *BREAK with a severity level of 60 or lower. Each message appears at least twice.Press the Enter key to respond to each message.a. CPF0994 ENDSBS SBS(*ALL) command being processed

b. CPF0968 System ended to restricted condition

If you responded N to the Prompt for commands prompt, skip to step 29.28. When the system is ready to perform each major step in the save operation, you are shown the

prompt display for that step. The time between prompt displays might be quite long.

Note: If independent ASPs are available, you will see additional prompts for options 21 and 23, asdescribed in the Saving independent ASPs topic.For option 21 (Entire system) these prompt displays appear:ENDSBS SBS(*ALL) OPTION(*IMMED)SAVSYSSAVLIB LIB(*NONSYS) ACCPTH(*YES)SAVDLO DLO(*ALL) FLR(*ANY)SAV DEV(/QSYS.LIB/media-device-name.DEVD) +


||||

||||

OBJ((/*) (/QSYS.LIB *OMIT) +(/QDLS *OMIT)) +

UPDHST(*YES)STRSBS SBSD(controlling-subsystem)

For option 22 (System data only) these prompt displays appear:ENDSBS SBS(*ALL) OPTION(*IMMED)SAVSYSSAVLIB LIB(*IBM) ACCPTH(*YES)SAV DEV(/QSYS.LIB/media-device-name.DEVD) +

OBJ((/QIBM/ProdData) +(/QOpenSys/QIBM/ProdData)) +


For option 23 (All user data) these prompt displays appear:ENDSBS SBS(*ALL) OPTION(*IMMED)SAVSECDTASAVCFGSAVLIB LIB(*ALLUSR) ACCPTH(*YES)SAVDLO DLO(*ALL) FLR(*ANY)SAV DEV(/QSYS.LIB/media-device-name.DEVD) +

OBJ((/*) (/QSYS.LIB *OMIT) +(/QDLS *OMIT) +(/QIBM/ProdData *OMIT) +(/QOpenSys/QIBM/ProdData *OMIT)) +


Type your changes at each prompt display and press the Enter key.29. When the system sends a message that asks you to load the next volume, load the next media and

respond to the message. For example, if the message is the following, load the next volume and thenenter R to try again (C cancels the operation):Device was not ready or next volume wasnot loaded (C R)

Attention: If an unrecoverable media error occurs during the SAVLIB procedure, see Recoveringfrom a media error during a SAVLIB operation.

30. Change the QINACTITV system value back to its original value. You wrote this value down in step18 c.

31. When the save operation is completed, print the job log. It contains information about the saveoperation. Use it to verify that the operation saved all objects. Type one of the following:DSPJOBLOG * *PRINT

OrSIGNOFF *LIST

You have completed the save operation. Make sure that you mark all of your media and store it in asafe, accessible place.

32. If you ended clustering before running the save operation, restart clustering on the save node from anode where clustering is already active.For more information, see the online help for Cluster Resource Services, or see IBM i Clusterstechnology.

33. Restart the device cluster resource group to enable resiliency.

Optional features that affect your backupOptional features that affect your backup might include user-defined files, virtual storage, encryptionkeys, independent disk pools, and network servers.


Are you using user-defined file systemsA user-defined file system (UDFS) is a file system that a user creates and manages. To determine if youhave any UDFS on your system, use one of the following methods.

Using System i Navigator:

Using System i Navigator, expand your_system > File Systems > Integrated File System > Root > dev >QASPxx or select the name of an independent disk pool. If UDFS objects exist, they appear in the rightpane.

Using the character-based interface:

Perform the following steps to see if you have user-defined file systems on the system.1. At a command line, specify wrklnk '/dev' .2. On the Work with Object Links display, select option 5 (Display) to display the contents of the dev

directory.3. Locate object links beginning with QASPxx or the name of an independent disk pool, and select

Option 5 to display the UDFS within the auxiliary storage pool (ASP).

Are you using software encryption for tapesIf you are using software encryption for backup tapes and saving system data (GO SAVE option 21 or22), set the save/restore master key before you perform the save operation. For the instructions, see theLoading and setting the save/restore master key topic.

Do you use virtual storageVirtual media simulates tape, CD, or DVD images that are stored directly on your system disk units. Todetermine if you store virtual images in image catalogs, do the following:1. At a command line, specify WRKIMGCLG.

Note: The Work with Image Catalogs (WRKIMGCLG) window displays the name of the imagecatalog, the status, and the virtual type.

Do you use independent disk poolsAn independent disk pool is a collection of disk units that can be brought online or taken offlineindependent of the rest of the storage on a system. If you have the necessary authority, you can checkwhether independent disk pools are configured on your system. Using System i Navigator, expandyour_system > Configuration and Service > Hardware > Disk Units > Disk pools folder. Independentdisk pools are numbered 33 255.

Have you configured independent disk pools to switch betweensystems in a clusterA System i cluster is a collection or group of one or more systems or logical partitions that work togetheras a single system. If you have the required authority, you can check to see if your independent disk poolis switchable between systems in a cluster.1. Using System i Navigator, expand your_system > Configuration and Service > Hardware > Disk

Units > Disk pools folder.2. Independent disk pool are numbered somewhere between 33 and 255. Right-click the independent

disk pool and select Properties.3. On the Disk Pool Properties page the General tab displays the field Switchable: Yes if you have

configured your independent disk pool to switch between systems.


Do you use WebSphere MQ for IBM i on this systemThe WebSphere MQ for IBM i (5724-H72) licensed program provides application programming servicesthat enable you to code indirect program-to-program communications that use message queues. Thisenables programs to communicate with each other across all supported platforms.

To check whether you have installed WebSphere MQ, use one of the following methods:


Using System i Navigator, expand your_system > Configuration and Service > Software > InstalledProducts.


1. At a command line, specify GO LICPGM.2. Specify option 10 (Display installed licensed programs) to display installed licensed programs.

If WebSphere MQ is installed, WebSphere MQ for IBM i appears in the Description column forlicensed program 5724-H72.If WebSphere MQ is installed, the Work with Queue Managers (WRKMQM) command lets you see ifyou have configured any queue managers.

Do you use OptiConnect controllersOptiConnect is the system area network that provides high-speed interconnectivity between multiplesystems in a local environment.

To check whether you have installed OptiConnect, use one of the following methods:


Using System i Navigator, expand your_system > Configuration and Service > Software > InstalledProducts. OptiConnect is option 23 of product 5770-SS1, IBM i - OptiConnect.


1. At a command line, specify GO LICPGM.2. Specify option 10 to display installed licensed programs.3. If OptiConnect is installed, OptiConnect appears under the Description column for licensed program

5770-SS1.

Do you use network serversSeveral solutions are available that enable you to run other operating systems on your System i product.Examples include integrated server solutions that run an x86-based Linux or Windows operating system,and Linux or AIX running in a logical partition.

Do you use the Hardware Management ConsoleIf you have a System i5 model 5xx, your system might be equipped with a Hardware ManagementConsole (HMC). An HMC is required if you use Capacity on Demand or logical partitions.

Printing system informationPrinting the system information provides valuable information about your system that will be usefulduring a system recovery. It is especially useful if you cannot use your SAVSYS media to recover andmust use your distribution media.


Printing this information requires *ALLOBJ, *IOSYSCFG, and *JOBCTL authority and produces manyspooled file listings. You might not need to print this information every time you perform a backup.However, you should print it whenever important information about your system changes.1. Print your current disk configuration. This is essential if you plan to do a model upgrade and you

are using mirrored protection. This information is also vital if you need to recover an independentASP. Do the following:a. Sign on with a user profile that has *SERVICE special authority.b. Type STRSST on a command line and press the Enter key.c. Specify the service tools user ID and service tools password. These are case-sensitive.d. Select option 3 Work with disk units on the System Service Tools (SST) display.e. Select option 1 Display disk configuration on the Work with Disk Units display.f. Select option 3 Display disk configuration protection on the Display Disk Configuration display.g. Print the displays there might be several using the PRINT key for each display.h. Press F3 until you see the Exit System Service Tools display.i. On the Exit System Service Tools display, press the Enter key.

2. If you are operating in a clustered environment, print the cluster configuration information. Use thefollowing commands to print cluster information:a. Display Cluster Information DSPCLUINF DETAIL(*FULL) OUTPUT(*PRINT)b. Display Cluster Resource Group DSPCRGINF CLUSTER(cluster-name) CRG(*LIST)

OUTPUT(*PRINT)3. If you have independent ASPs configured, record the relationship between the independent ASP

name and number. You can find this information in System i Navigator. In the Disk Units folder,select Disk Pools.

4. Sign on with a user profile that has *ALLOBJ special authority, such as the security officer. Thesystem lists information only if you have the correct authority. If you sign on as a user with less than*ALLOBJ authority, some of the listings in these steps might not be complete. You must also beenrolled in the system directory before you can print a list of all the folders on the system.

5. If you use the history log or if you have a requirement to keep it, do the following:a. Display the system log QHST. This automatically brings it up to date. Type:

DSPLOG LOG(QHST) OUTPUT(*PRINT)

b. Display all copies of the system log:WRKF FILE(QSYS/QHST*)

Look at the list to verify that you saved all copies of the log that you might need later.

Note: The history (QHST) log contains information such as date created, and the last change dateand time. To get more information about the history (QHST) log, select option 8 (Display filedescription) on the Work with Files display.

c. To prevent confusion about the date of the log, select the Delete option on the Work with Filesdisplay. Delete all but the current copies of the system log. This step improves the performance ofthe SAVSYS command.

6. Print the system information. You can do this by two different methods:a. Using the GO SAVE command, on the Specify Command Defaults display, select Y at the Print

system information prompt.b. Use the PRTSYSINF command.The following table describes the spooled files that the system creates. The PRTSYSINF commanddoes not create empty spooled files. If some objects or types of information do not exist on yoursystem, you might not have all of the files listed below.


Table 1. Spooled files created by the system

Spooled File Name User Data Description of Contents

QPEZBCKUP DSPBCKUPL List of all user libraries

QPEZBCKUP DSPBCKUPL List of all folders

QSYSPRT DSPSYSVAL Current settings for all system values

QDSPNET DSPNETA Current settings for all network attributes

QSYSPRT DSPCFGL Configuration lists

QSYSPRT DSPEDTD User-defined edit descriptions ( a separate spooled file for each)

QSYSPRT DSPPTF Details of all fixes that are installed on your system

QPRTRPYL WRKRPYLE All reply list entries

QSYSPRT DSPRCYAP Settings for access path recovery times

QSYSPRT DSPSRVA Settings for service attributes

QSYSPRT DSPNWSSTG Network server storage spaces information

QSYSPRT DSPPWRSCD Power on/off schedule

QSYSPRT DSPHDWRSC Hardware configuration reports (a separate spooled file for eachresource type, such as *CMN or *LWS)

QSYSPRT WRKOPTCFG Optical device descriptions (if your system has an optical deviceand optical support is started when you run the command)

QSYSPRT DSPRJECFG Remote job entry configurations

QPDSTSRV DSPDSTSRV SNADS configuration

QPRTSBSD DSPSBSD Subsystem descriptions (a separate spooled file for each subsystemdescription on your system)

QSYSPRT DSPSFWRSC Installed licensed programs (Software Resources List)

QPRTOBJD DSPOBJD A list of all the journals on your system

QPDSPJNA WRKJRNA The journal attributes for each journal that is not in the QUSRSYSlibrary (a separate file for each journal). Typically, journals in theQUSRSYS library are IBM-supplied journals. If you have your ownjournals in the QUSRSYS library, you need to manually printinformation about those journals.

QSYSPRT CHGCLNUP Settings for automatic cleanup

QPUSRPRF DSPUSRPRF Current values for the QSECOFR user profile

QPRTJOBD DSPJOBD Current values for the QDFTJOBD job description

QPJOBLOG PRTSYSINF The job log for this job1

1 On your system, this spooled file might be in the QEZJOBLOG output queue.

7. Print a list of directories in the root (/) directory.DSPLNK OBJ(/*) OUTPUT(*PRINT)

8. Print any IBM-supplied objects that you have modified, such as the QSYSPRT print file.9. If you maintain a CL program that contains your configuration information, use the Retrieve

Configuration Source (RTVCFGSRC) command to ensure that the CL program is current.RTVCFGSRC CFGD(*ALL) CFGTYPE(*ALL) +

SRCFILE(QGPL/QCLSRC) +SRCMBR(SYSCFG)

10. Print these spooled files. Keep this information with your backup log or your save system media forfuture reference. If you choose not to print the lists, use the Copy Spooled File (CPYSPLF) command


to copy them to database files. See Save spooled files for information about how to do this. Makesure that the database files are in a library that is saved when you perform the Save menu option.

Save considerations when checking out objectsThis topic provides information about the save considerations if you have checked out objects.

If you use IBM i Navigator or the Check Out Objects (CHKOUT) command to check out objects to aspecific user, you should check these objects back in before performing the save. When an object ischecked out to a user, other users can read the object, but they cannot update the object. If an objectremains checked out during a save that specifies update history UPDHST(*YES), message CPFA09E issent for the object, because the update history function is unable to change the attributes for the object.

Tape write error recoveryTape write error recovery refers to an attempt to recover from a write media error and continue a save onanother volume.

In order to rewrite the data that was sent to the tape drive but was never written to the media because itwas still in the drive buffer when the media error occurred, a large amount of data needs to be tracked inmain store. The amount of data that needs to be tracked can become very large and consume significantmemory resource. The newer tape devices contain a large data buffer (128 MB or larger) that along withdata compaction on the order of 3:1 can result in over 384 MB of data that needs to be tracked to be ableto recover from media errors.

You might encounter performance problems if you use tape write error recovery because of the memoryrequired to track data plus some limits for how much data can actually be tracked for each tape drive.Because of the potential save performance impacts, tape write error recovery is not enabled by default.Tape write error recovery needs to be enabled if you want to use it.

Note: You cannot use software encryption when tape write error recovery is enabled.

Enabling and disabling tape write error recovery

Tape write error recovery can be enabled by creating a data area in either library QTEMP or QUSRSYSwith the same name as the device description to be used for the save operations. The data area needs tobe created as TYPE(*CHAR) with a length of at least 128 bytes. Change the character at position 20 to aY to enable tape write error recovery or N to disable write error recovery. Creating the data area inlibrary QTEMP will cause tape write error recovery to only be used for saves done by the job creating thedata area in its QTEMP library. Creating the data area in library QUSRSYS will cause the tape write errorrecovery setting to be used by all saves that use the device for which the data area is created. Theoperating system first checks for a data area in QTEMP, so tape write error recovery can still be enabledor disabled for a particular job even if a data area exists in library QUSRSYS.

Example: Enabling Tape Write Error RecoveryCRTDTAARA DTAARA(QTEMP/TAPMLB01) TYPE(*CHAR) LEN(128)CHGDTAARA DTAARA(QTEMP/TAPMLB01 (20 1)) VALUE(Y)

Example: Disabling Tape Write Error RecoveryCHGDTAARA DTAARA(QTEMP/TAPMLB01 (20 1)) VALUE(N)

ObjectConnect functionObjectConnect is a set of control language (CL) commands for moving objects between systems easilyand efficiently.


ObjectConnect is included with the IBM i operating system. You install it by selecting it on the InstallLicensed Program display.

When you use an ObjectConnect command, the system moves the object directly to the target systemwithout using save files or distribution queues. ObjectConnect provides better performance than othermethods for moving objects between systems, and ObjectConnect does not require additional disk spaceto store an intermediate copy of the object that is being moved.

ObjectConnect commands are closely related to the save and restore commands. The ObjectConnectcommands support most of the same parameters. Table 2 shows a list of the ObjectConnect commandsand the associated IBM i save and restore commands. Using the ObjectConnect commands on page 20describes the functions that are performed by each command. The online command help describes theparamete