version 6 release 1 - ibm - united states€¦ · system i systems management recovering your...

System i

Systems managementRecovering your systemVersion 6 Release 1

SC41-5304-09

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

This edition applies to version 6, release 1, modification 0 of IBM i5/OS (product number 5761-SS1) and to allsubsequent releases and modifications until otherwise indicated in new editions. This version does not run on allreduced instruction set computer (RISC) models nor does it run on CISC models.

This edition replaces SC41-5304-08.

Copyright International Business Machines Corporation 1997, 2008.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

Whats new for V6R1 . . . . . . . . xvii

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

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

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 . . . . . 14Have you configured independent disk pools toswitch between systems in a cluster . . . . . 14Do you use WebSphere MQ, V6 on this system 14Do you use OptiConnect controllers . . . . . 14Do you use network servers . . . . . . . . 15Do you use the Hardware Management Console 15

Printing system information . . . . . . . . . 15Save considerations when checking out objects . . 18Tape write error recovery . . . . . . . . . . 18ObjectConnect function . . . . . . . . . . 19

Components of ObjectConnect . . . . . . . 19Setting up your system to use ObjectConnect . . 20How the system runs an ObjectConnectcommand . . . . . . . . . . . . . . 20Using the ObjectConnect commands . . . . . 21Investigating ObjectConnect problems . . . . 22CPFAD84 error codes . . . . . . . . . . 23

Part 2. Recovering information onyour system. . . . . . . . . . . . 25

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

Reclaiming storage . . . . . . . . . . . 44Reclaiming object links . . . . . . . . . . 45Controlling restoration of security-sensitive objects 46

QALWOBJRST system value. . . . . . . . 46Setting the QALWOBJRST system value to allowcomplete recovery . . . . . . . . . . . 47Setting the QALWOBJRST system value torestrict restore operations . . . . . . . . . 47QVFYOBJRST system value . . . . . . . . 48Setting the QVFYOBJRST system value to allowcomplete recovery . . . . . . . . . . . 49Setting the QVFYOBJRST system value to restrictrestore operations . . . . . . . . . . . 49

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

Recovering from an error while restoring libraries 53Recovering from an error while restoringdocument library objects . . . . . . . . . 54

Performing a normal initial program load . . . . 55Parallel restore operations . . . . . . . . . 56Restore operation output file information . . . . 57Field descriptions for restore output file . . . . . 59

Chapter 3. Selecting the appropriaterecovery strategy . . . . . . . . . . 65Some common recovery terminology . . . . . . 65Recovery procedure for a power failure . . . . . 66Recovery procedure for a system failure . . . . . 67Recovery procedure for a program failure or humanerror. . . . . . . . . . . . . . . . . 67Recovering the vital product data information if thepartition does not IPL in A-mode or B-mode . . . 67Choosing the recovery procedure for a disk failureor disk errors . . . . . . . . . . . . . . 68

Checklist 1: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 70Checklist 2: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 71Checklist 3: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 72Checklist 4: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 73Checklist 5: Actions for load-source disk unitfailure . . . . . . . . . . . . . . . 77Checklist 6: Actions for non-load source disk unitfailure or disk units in basic user auxiliarystorage pool disk failure . . . . . . . . . 81Checklist 7: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 82Checklist 8: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 83

Copyright IBM Corp. 1997, 2008 iii

||

||

||||

|||

Checklist 9: Actions for non-load source disk unitfailure . . . . . . . . . . . . . . . 84Checklist 10: Actions for non-load source diskunit failure . . . . . . . . . . . . . 88Checklist 11: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 92Checklist 12: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 93Checklist 13: Actions for a failure in a basicauxiliary storage pool disk unit. . . . . . . 95Checklist 14: Actions for non-load source diskunit failure . . . . . . . . . . . . . 97Checklist 15: Actions for non-load source diskunit failure . . . . . . . . . . . . . 98Checklist 16: Actions for non-load source diskunit failure . . . . . . . . . . . . . 99Checklist 17: Actions for independent auxiliarystorage pool disk failure . . . . . . . . . 100Checklist 18: Actions for a failure in anindependent auxiliary storage pool disk unit . . 101Checklist 19: Actions for a failure in anindependent auxiliary storage pool disk unit . . 102Checklist 20: Recovering your entire systemafter a complete system loss . . . . . . . 104Checklist 21: Recovering your entire systemafter a complete system loss includingindependent auxiliary storage pools . . . . . 107Checklist 22: Restoring a logical partition toanother logical partition . . . . . . . . . 111Checklist 23: Actions for a failed cache card . . 113

Choosing the procedure to recover userinformation . . . . . . . . . . . . . . 114

Checklist 24: Recovering user information usingcommands . . . . . . . . . . . . . 116Checklist 25: Using option 21 from the restoremenu . . . . . . . . . . . . . . . 120Checklist 26: Using options 22 and 23 from therestore menu . . . . . . . . . . . . 122Checklist 27: Recovering user information usingtapes from Operational Assistant backup . . . 125

Chapter 4. Recovering the LicensedInternal Code . . . . . . . . . . . 131Preparing for loading the Licensed Internal Code 132

Task 1: Getting ready to load the LicensedInternal Code . . . . . . . . . . . . 132Task 2: Powering down the system . . . . . 133Task 3a: Preparing the system to perform aninitial program load (IPL) from an alternatedevice . . . . . . . . . . . . . . . 134Task 3b: Preparing a logical partition (LPAR) toperform an initial program load (IPL) from analternate device. . . . . . . . . . . . 134Task 4: Loading the Licensed Internal Codefrom media . . . . . . . . . . . . . 135

Loading the Licensed Internal Code . . . . . . 140Recovering the vital product data information ifthe partition does not IPL in A-mode or B-mode . 143Recovering your logical partition configuration . . 144Setting up your disk configuration after installingthe Licensed Internal Code . . . . . . . . . 146

Using System i Navigator to set up your diskconfiguration after installing Licensed InternalCode . . . . . . . . . . . . . . . . 147Recovering your disk configuration . . . . . . 150Starting your system after restoring the LicensedInternal Code . . . . . . . . . . . . . 153

Chapter 5. Restoring the operatingsystem . . . . . . . . . . . . . . 155Choosing the right procedure for restoring theoperating system . . . . . . . . . . . . 156Loading the operating system using a manualinitial program load . . . . . . . . . . . 156Tasks to restoring the operating system. . . . . 157

Task 1: Starting to restore the operating system 158Task 2: Selecting the installation options . . . 162Task 3: Selecting initial program load options 166Task 4: Setting major system options . . . . 167Task 5: Defining or changing the system atinitial program load (IPL) . . . . . . . . 168Task 6: Completing the initial program load . . 170

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

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

Using the Disk Configuration Error Reportdisplay . . . . . . . . . . . . . . 173Using the Main Storage Dump Occurred display 174

Restarting your system . . . . . . . . . . 175Task 1: Performing an attended initial programload . . . . . . . . . . . . . . . 175Task 2: Editing the rebuilding of access paths 177Task 3: Editing check pending constraints . . . 179Task 4: Recovering from damaged objects andunreadable sectors. . . . . . . . . . . 180

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

Task 1: Reclaiming storage . . . . . . . . 189Task 2: Restoring user profiles . . . . . . . 191Task 3: Restoring the configuration . . . . . 191Task 4: Recovering journals and journalreceivers in the QRCL library . . . . . . . 191Task 5: Restoring libraries to the systemauxiliary storage pool . . . . . . . . . 192Task 6: Restoring document library objects tothe system auxiliary storage pool . . . . . . 193Task 7: Restoring user-defined file systems tothe user auxiliary storage pool . . . . . . 194Task 8: Reclaiming document library objects . . 195Task 9: Recovering save files from the QRCLlibrary. . . . . . . . . . . . . . . 195

iv System i: Systems management Recovering your system

|||

Task 10: Associating journal receivers withjournals . . . . . . . . . . . . . . 196Task 11: Restoring object ownership . . . . . 197

Recovering an overflowed user auxiliary storagepool . . . . . . . . . . . . . . . . 198

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

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

Task 1: Restoring user profiles . . . . . . . 203Task 2: Determining the contents of the lostauxiliary storage pool . . . . . . . . . 203Task 3: Determining tasks to restore objects . . 204Task 4: Restoring libraries to a basic auxiliarystorage pool . . . . . . . . . . . . . 204Task 5: Restoring journals to a basic auxiliarystorage pool . . . . . . . . . . . . . 205Task 6: Restoring documents to a basic auxiliarystorage pool . . . . . . . . . . . . . 206Task 7: Restoring user-defined file systems to abasic auxiliary storage pool. . . . . . . . 206Task 8: Restoring journal receivers to a basicauxiliary storage pool . . . . . . . . . 207Task 9: Restoring save files to a basic auxiliarystorage pool . . . . . . . . . . . . . 207

Recovering an independent auxiliary storage pool 208Task 1: Restoring user profiles . . . . . . . 208Task 2: Determining tasks to restore objects toan independent auxiliary storage pool . . . . 208Task 3: Restoring libraries to the independentauxiliary storage pool . . . . . . . . . 209Task 4: Restoring user-defined file systems tothe independent auxiliary storage pool . . . . 210Task 5: Restoring authority for an independentauxiliary storage pool . . . . . . . . . 211

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

Task 1: Accessing dedicated service tools . . . 212Task 2: Deleting the auxiliary storage pool data 213Task 3: Removing the disk unit from theauxiliary storage pool configuration . . . . . 214

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

Chapter 9. Restoring specific types ofinformation . . . . . . . . . . . . 223Recovering system information . . . . . . . 223Sequence for restoring security information . . . 223Restoring user profiles . . . . . . . . . . 224

What happens when you restore user profiles 226What you should know about restoring userprofiles . . . . . . . . . . . . . . 227How the system establishes ownership forrestored objects . . . . . . . . . . . . 228

How the system establishes the authorizationlist for a restored object . . . . . . . . . 229How the system establishes the primary groupfor restored objects . . . . . . . . . . 229

Restoring object authorities . . . . . . . . . 229Overview of restoring authorities. . . . . . 230Restoring private authorities in a full-systemrecovery . . . . . . . . . . . . . . 230Restoring private authorities for selected objects 231Restoring authority on a system in anonrestricted state . . . . . . . . . . . 232Restoring authority on a system in a restrictedstate . . . . . . . . . . . . . . . 236Examples: How the system restores authority 236

Restoring authorities for independent auxiliarystorage pool data . . . . . . . . . . . . 239Restoring configuration objects . . . . . . . 242

Correcting problems with the system resourcemanagement information . . . . . . . . 243Recovering when you change the console type 245Recovering the System/36 environmentconfiguration . . . . . . . . . . . . 245

Restoring logical partitions . . . . . . . . . 246Restoring libraries . . . . . . . . . . . . 247

Restoring a library from a previous release . . 248Restoring multiple libraries . . . . . . . . 248Considerations and restrictions of the RestoreLibrary command . . . . . . . . . . . 249Restoring all libraries from a single saveoperation . . . . . . . . . . . . . . 249Restoring all libraries from multiple saveoperations . . . . . . . . . . . . . 250

Restoring objects . . . . . . . . . . . . 250Restoring journaled objects . . . . . . . . 251

Restoring user-defined file systems . . . . . . 254Restoring an unmounted user-defined filesystem . . . . . . . . . . . . . . 254Restoring an individual object from anunmounted user-defined file systems . . . . 254Restoring a mounted user-defined file system 255Restore actions for mounted user-defined filesystems . . . . . . . . . . . . . . 255

Restoring database files . . . . . . . . . . 256Comparing file attributes during a restoreoperation . . . . . . . . . . . . . . 257How the system matches file members during arestore operation . . . . . . . . . . . 260Restoring members to a file . . . . . . . 260Restoring logical files. . . . . . . . . . 261How the system restores access paths . . . . 262How the system restores files with sharedformats . . . . . . . . . . . . . . 265How the system restores files with referentialconstraints . . . . . . . . . . . . . 265How the system restores files with triggers . . 267Restoring SQL materialized query tables . . . 268Deleting a physical file . . . . . . . . . 269

Restoring journals and journal receivers . . . . 269Restoring journals . . . . . . . . . . . 270Deleting a journal . . . . . . . . . . . 270Restoring journal receivers . . . . . . . . 271

Contents v

|||||

|||||

||

Deleting a journal receiver . . . . . . . . 272How the system restores programs . . . . . . 273

Restoring programs to a different release . . . 275Restoring save file data . . . . . . . . . . 275Saving and restoring spooled files . . . . . . 276Restoring licensed programs . . . . . . . . 277Restoring documents and folders . . . . . . . 277

Restore Document Library command options 277Using multiple concurrent document libraryobject commands . . . . . . . . . . . 278Output from the Restore Document LibraryObject Command . . . . . . . . . . . 278Considerations and restrictions . . . . . . 279Restoring folders . . . . . . . . . . . 280Renaming documents when restoring . . . . 281How the system restores descriptive informationfor document library objects . . . . . . . 281How the system restores authority andownership for document library objects . . . 281When to run the Rename Directory Entrycommand . . . . . . . . . . . . . 282When to run the Rename Document LibraryObject command . . . . . . . . . . . 282

Restoring objects in directories . . . . . . . 282Completing recovery for integrated servers . . . 285

Restoring IXS or IXA-attached integratedWindows servers . . . . . . . . . . . 285Restoring iSCSI-attached integrated servers . . 285Recovery for save operation of network serverstorage spaces . . . . . . . . . . . . 286Recovery for save operation of data in QNTCfile system . . . . . . . . . . . . . 286Recovering AIX, i5/OS, or Linux in a logicalpartition . . . . . . . . . . . . . . 287Restoring Linux files . . . . . . . . . . 287

Recovering a Domino server . . . . . . . . 288Recovering an entire Domino server . . . . . 288Recovering Domino mail . . . . . . . . 289Recovering specific Domino databases . . . . 289Restoring changed objects to a Domino server 290

Restrictions when using the Restore command . . 293Restoring program temporary fixes (PTFs). . . . 295Restoring system information . . . . . . . . 296

Chapter 10. Restoring changedobjects and apply journaled changes . 297Task 1: Restoring changed objects . . . . . . 298

Restoring changed objects by library . . . . 298Restoring changed objects individually . . . . 298

Task 2: Restoring changed objects in directories . . 299Task 3: Determining whether you need to applyjournaled changes . . . . . . . . . . . . 300Task 4: Determining what journal receivers to use 300Task 5: Applying journaled changes for userjournals . . . . . . . . . . . . . . . 302Task 6: Applying journaled changes for theQAOSDIAJRN journal . . . . . . . . . . 304Task 7: Replaying journaled changes in a disasterrecovery . . . . . . . . . . . . . . . 305Task 8: Restoring changed documents and folders 305

Chapter 11. Mirrored protectionrecovery actions . . . . . . . . . . 307System actions for permanent errors. . . . . . 307Suspending mirrored units . . . . . . . . . 308Resuming mirrored units . . . . . . . . . 309Replacing a mirrored unit . . . . . . . . . 309

Using spare nonconfigured units forreplacement . . . . . . . . . . . . . 311Mirrored protection recovery actions performedby the service representative . . . . . . . 312Other recovery considerations for mirroredprotection . . . . . . . . . . . . . 313Mirrored protection disk-error handling . . . 314Missing disk units . . . . . . . . . . . 314Saving a unit . . . . . . . . . . . . 315Restoring a unit . . . . . . . . . . . 315Active mirrored load source failure . . . . . 316Unknown unit 1 status . . . . . . . . . 318Displaying incorrect Licensed Internal Codeinstallation . . . . . . . . . . . . . 319

Recovering remote load source mirroring . . . . 319Recovering after the remote load source hasfailed . . . . . . . . . . . . . . . 319Recovering after the local load source has failedon the system . . . . . . . . . . . . 319Using the recover mirrored load source function 321

Chapter 12. Restoring your systemusing Operational Assistant tapes . . 323Restoring your libraries . . . . . . . . . . 324Restoring libraries that you saved by using abackup list . . . . . . . . . . . . . . 326Restoring changed objects that you saved by usingOperational Assistant. . . . . . . . . . . 326

Chapter 13. Restoring the systemfrom the save storage media. . . . . 329Task 1: Powering down the system and loading theLicensed Internal Code . . . . . . . . . . 330Task 2: Restoring the save storage tapes . . . . 330Task 3: Responding to messages . . . . . . . 332Task 4: Completing the restore storage operation 333Task 5: Restoring additional information . . . . 335Task 6: Restoring program temporary fixes . . . 336Resuming the Restore Storage (RSTSTG) operation 336

Chapter 14. Restoring encryptedbackups and encrypted auxiliarystorage pools . . . . . . . . . . . 339Recovering from an encrypted backup usingsoftware encryption . . . . . . . . . . . 339Recovering from an encrypted backup using anencrypted tape . . . . . . . . . . . . . 340Backing up the Encryption Key Manager . . . . 341Restoring encrypted auxiliary storage pools . . . 342

Part 3. Release-to-release support 345

vi System i: Systems management Recovering your system

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

|||

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

Chapter 15. Release-to-releasesupport . . . . . . . . . . . . . . 347Current release to previous release support . . . 347

Creating the object for the previous release . . 348Saving the object for the previous release . . . 349Testing the object on the current release . . . 355Restoring and using the object on the previousrelease. . . . . . . . . . . . . . . 355Restrictions for current release to previousrelease support . . . . . . . . . . . . 355

Previous release to current release support . . . 355Considerations when moving systemcustomization information . . . . . . . . 356Restoring previous release user data to a newsystem . . . . . . . . . . . . . . 356Restrictions when going from previous releaseto current release . . . . . . . . . . . 373

Chapter 16. System synchronization:Planning and procedures . . . . . . 375Synchronization methods: Overview. . . . . . 376Moving changed objects . . . . . . . . . . 377

Saving changed objects . . . . . . . . . 378Restoring changed objects . . . . . . . . 379Problems when restoring changed objects . . . 380

Moving entire libraries . . . . . . . . . . 382Considerations for moving entire libraries . . . 383

Moving individual objects . . . . . . . . . 384Applying journaled changes . . . . . . . . 385Refreshing your new system . . . . . . . . 387Additional synchronization tips . . . . . . . 387

Part 4. Tips for merging two ormore i5/OS operating systems . . 389

Chapter 17. Tips for merging twosystems into a single system . . . . 391Guidelines for restoring information from thedevelopment system . . . . . . . . . . . 391

Part 5. Alternate Installation device 393

Chapter 18. Using an alternateinstallation device . . . . . . . . . 395Alternate installation device: Overview . . . . . 395Setting up an alternate installation device . . . . 395Disabling an alternate installation device . . . . 398Verifying and selecting an alternate installationdevice during a manual installation . . . . . . 399

Part 6. Disk configuration andprotection . . . . . . . . . . . . 403

Chapter 19. Configuring disks anddisk protection. . . . . . . . . . . 405Choosing the right procedure for configuring disks 405

Checklist 1: Configuring disks on a new system 406

Checklist 2: Adding disk units without deviceparity protection . . . . . . . . . . . 407Checklist 3: Adding disk units to an existinginput/output adapter . . . . . . . . . 408Checklist 4: Adding a new input/outputadapter . . . . . . . . . . . . . . 409Checklist 5: Moving disk units between nonmirrored auxiliary storage pools . . . . . . 410Checklist 6: Moving disk units betweenmirrored auxiliary storage pools . . . . . . 411Checklist 7: Deleting an auxiliary storage pool 413Checklist 8: Removing disk units without deviceparity protection . . . . . . . . . . . 414Checklist 9: Removing disk units that havedevice parity protection from an auxiliarystorage pools without mirrored protection . . . 415Checklist 10: Removing disk units that havedevice parity protection from an auxiliarystorage pool with mirrored protection . . . . 416Using system service tools and dedicatedservice tools . . . . . . . . . . . . . 417Displaying your disk configuration . . . . . 421

Chapter 20. Working with auxiliarystorage pools . . . . . . . . . . . 427Adding disk units to an existing auxiliary storagepool . . . . . . . . . . . . . . . . 427Creating an unencrypted auxiliary storage pool 430Creating an encrypted auxiliary storage pool . . . 432Changing the storage threshold for an auxiliarystorage pool . . . . . . . . . . . . . . 434Changing the storage threshold for the systemauxiliary storage pool . . . . . . . . . . 436Moving a disk unit to a different auxiliary storagepool . . . . . . . . . . . . . . . . 437Removing a disk unit from an auxiliary storagepool . . . . . . . . . . . . . . . . 439Deleting an auxiliary storage pool . . . . . . 441Calculating space requirements for an auxiliarystorage pool . . . . . . . . . . . . . . 442Displaying the objects in a user auxiliary storagepool . . . . . . . . . . . . . . . . 443Balancing an auxiliary storage pool . . . . . . 443

Capacity balancing . . . . . . . . . . 443Usage balancing . . . . . . . . . . . 444Hierarchical storage management balancing . . 444

Transferring objects between auxiliary storagepools . . . . . . . . . . . . . . . . 444

Transferring a library to a different auxiliarystorage pool . . . . . . . . . . . . . 445Transferring a folder to a different auxiliarystorage pool . . . . . . . . . . . . . 445Transferring journals and objects to a differentauxiliary storage pool . . . . . . . . . 446Creating objects in a library user auxiliarystorage pool . . . . . . . . . . . . . 447Placing journal receivers in a user auxiliarystorage pool . . . . . . . . . . . . . 448Moving journal receivers from an overflowedbasic user auxiliary storage pool . . . . . . 449Resetting a journal with a status of overflowed 449

Contents vii

||||

Working with nonlibrary user auxiliary storagepools . . . . . . . . . . . . . . . . 451

Creating objects in a nonlibrary user auxiliarystorage pool . . . . . . . . . . . . . 451Transferring an object to a nonlibrary auxiliarystorage pool . . . . . . . . . . . . . 452Transferring a journal to a nonlibrary userauxiliary storage pool . . . . . . . . . 452

Chapter 21. Working with deviceparity protection . . . . . . . . . . 455Starting device parity protection . . . . . . . 455

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

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

Removing disk units that have device parityprotection for System i while powered on . . . . 459Removing disk units that have device parityprotection for System i while powered off . . . . 461Removing disk units that have device parityprotection for a System i . . . . . . . . . 463Including a disk unit in device parity protection 465Excluding a disk unit from device parity protection 466Displaying device parity status . . . . . . . 467

Chapter 22. Working with mirroredprotection . . . . . . . . . . . . . 469Mirrored protection: Configuration rules . . . . 469Starting mirrored protection . . . . . . . . 469

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

Mirrored protection configuration errors . . . . 472Stopping mirrored protection . . . . . . . . 472

Chapter 23. Working with diskcompression. . . . . . . . . . . . 475Introduction to disk compression . . . . . . . 475

Restrictions and considerations . . . . . . 475Disk compression and capacity . . . . . . 476Disk unit full considerations . . . . . . . 477How the system responds to disk unit full 448reference code A6xx 0277 . . . . . . . . 478

SRC code A6xx 0277 . . . . . . . . . . . 479User action 1 . . . . . . . . . . . . 479User action 2 . . . . . . . . . . . . 480User action 3 . . . . . . . . . . . . 480User action 4 . . . . . . . . . . . . 480Examples of A6xx 0277 . . . . . . . . . 481

Starting disk compression . . . . . . . . . 481Stopping disk compression . . . . . . . . . 483Procedural sequences for configuring disks andprotection . . . . . . . . . . . . . . 485

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

Recovering from error codes . . . . . . . . 488Recovering from SRC 6xxx 7051 . . . . . . 489Recovering from SRC 6xxx 7052 . . . . . . 489

Chapter 24. Managing auxiliarystorage pools . . . . . . . . . . . 491Working with ASP trace and ASP balance . . . . 491

Capacity balance . . . . . . . . . . . 492Hierarchical storage management (HSM)balance . . . . . . . . . . . . . . 493Usage balance . . . . . . . . . . . . 493Auxiliary storage pool trace . . . . . . . 494

Determining adequate disk storage . . . . . . 494

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

Chapter 25. Examples: Techniquesand programming for backup andrecovery . . . . . . . . . . . . . 499Examples: Backup and recovery . . . . . . . 499

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

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

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

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

Section 7. Recovery plan for mobile site . . . . 517Mobile site setup plan . . . . . . . . . 518Communication disaster plan . . . . . . . 518Electrical service . . . . . . . . . . . 518

Section 8. Recovery plan for hot site . . . . . . 518Alternate-site system configuration . . . . . 519

Section 9. Restoring the entire system . . . . . 519Section 10. Rebuilding process. . . . . . . . 519Section 11. Testing the disaster recovery plan . . . 520Section 12. Disaster site rebuilding . . . . . . 521

Vendors . . . . . . . . . . . . . . 522Floor plan . . . . . . . . . . . . . 522

Section 13. Record of plan changes . . . . . . 522

viii System i: Systems management Recovering your system

Appendix C. Recovering your entiresystem . . . . . . . . . . . . . . 523

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

Appendix E. Notices . . . . . . . . 551

Programming interface information . . . . . . 553Trademarks . . . . . . . . . . . . . . 553Terms and conditions. . . . . . . . . . . 553

Bibliography. . . . . . . . . . . . 555

Index . . . . . . . . . . . . . . . 557

Contents ix

x System i: Systems management Recovering your system

Figures

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

systems . . . . . . . . . . . . . . 335. User ASP configuration before failure 1876. Basic user ASP configuration after restoring

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

storage. . . . . . . . . . . . . . 1908. User ASP configuration after recovering

isolated journal receiver . . . . . . . . 1929. Restore menufirst display . . . . . . . 217

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

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

nonrestricted state . . . . . . . . . . 23514. Expanded text for message CPF3845 . . . . 23515. Save data from an independent ASP and

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

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

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

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

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

20. Example of a database file with two members 25621. Restoring a copy of a file . . . . . . . 25722. Restoring database files with different

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

creation dates . . . . . . . . . . . 25924. Restoring access paths . . . . . . . . 26425. Restoring a referential constraint network 26626. An object with hard linksExample . . . . 28327. An object with a symbolic linkExample 28428. Sample recovery time line . . . . . . . 29729. Receiver directorySaving attached receivers 30130. Receiver directorySaving detached receivers 30131. How the system is saved with Operational

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

user data to a new system . . . . . . . 35833. Overview of synchronization process 37634. Display hardware resource listing . . . . . 42235. Program for retrieving journal entries 49936. Program for writing the RCVJRNE command

output to save media . . . . . . . . . 501

Copyright IBM Corp. 1997, 2008 xi

xii System i: Systems management Recovering your system

Tables

1. Spooled files created by the system . . . . 172. ObjectConnect and associated System i save

and restore commands . . . . . . . . . 193. Basic components of ObjectConnect . . . . 194. Relationship between save and restore

commands . . . . . . . . . . . . . 335. Restoring objects with ALWOBJDIF . . . . 356. Possible values for the OPTION parameter of

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

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

value. . . . . . . . . . . . . . . 479. Lock type needed for restore operation 50

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

disk media failure . . . . . . . . . . 6912. Recovery checklist for disk failureChecklist 1 7113. Recovery checklist for disk failureChecklist 2 7114. Recovery checklist for disk failureChecklist 3 7315. Recovery checklist for disk failureChecklist 4 7416. Recovery checklist for disk failureChecklist 5 7817. Recovery checklist for disk failureChecklist 6 8218. Recovery checklist for disk failureChecklist 7 8219. Recovery checklist for disk failureChecklist 8 8420. Recovery checklist for disk failureChecklist 9 8521. Recovery checklist for disk failureChecklist 10 8922. Recovery checklist for disk failureChecklist 11 9223. Recovery checklist for disk failureChecklist 12 9324. Recovery checklist for disk failureChecklist 13 9525. Recovery checklist for disk failureChecklist 14 9826. Recovery Checklist for disk failureChecklist

15 . . . . . . . . . . . . . . . . 9827. Recovery checklist for disk failureChecklist 16 9928. Recovery checklist for disk failureChecklist

17 . . . . . . . . . . . . . . . 10029. Recovery checklist for disk failureChecklist

18 . . . . . . . . . . . . . . . 10130. Recovery checklist for disk failureChecklist

19 . . . . . . . . . . . . . . . 10231. Recovery checklist for complete system

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

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

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

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

user information . . . . . . . . . . 11536. Checklist for recovering user information

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

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

using options 22 and 23 . . . . . . . . 122

39. Checklist for recovering user informationusing Operational Assistant backup tapes . . 126

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

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

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

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

for deleting . . . . . . . . . . . . 19945. Tasks for restoring basic ASP objects . . . . 20446. Example of restore order for independent

ASPs saved with GO SAVE: Option 21 or 23 . 20947. Tasks for restoring independent ASP objects 20948. Commands for changing system information 22349. How user profiles are restored . . . . . . 22550. Copying user profiles without affecting the

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

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

the PVTAUT parameter . . . . . . . . 23154. How configuration objects are restored 24255. Methods for restoring all librariessingle save

operation . . . . . . . . . . . . . 24956. Methods for restoring all librariesmultiple

save operations . . . . . . . . . . . 25057. Restoring a file network . . . . . . . . 26458. Restoring files that have trigger programs 26759. Save and restore spooled files . . . . . . 27660. Restoring objects that have hard links 28461. Using the RST Command for QSYS.LIB

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

commandExamples . . . . . . . . . 29563. Restore procedures for changed objects 29864. Handling messages when restoring storage 33365. Values for TGTRLS parameter . . . . . . 34766. Language support for the target release

parameter. . . . . . . . . . . . . 34867. Previous-release support by object type 35068. Comparison of synchronization methods 37769. Choosing the right disk procedure . . . . 40570. Configuring disks on a new systemTasks 40671. Adding disk units without device parity

protectionTasks . . . . . . . . . . 40872. Adding disk units to an existing IOATasks 40973. Adding a new IOATasks . . . . . . . 41074. Moving disk units between ASPsTasks 41175. Moving disk units between ASPs with

mirrored protectionTasks . . . . . . . 41276. Deleting an user ASPTasks. . . . . . . 41377. Removing disk units that do not have device

parity protectionTasks . . . . . . . . 414

Copyright IBM Corp. 1997, 2008 xiii

||

|||

|||

||

78. Removing disk units from an IOA and anon-mirrored ASPTasks . . . . . . . . 415

79. Removing disk units from an IOA and amirrored ASPTasks . . . . . . . . . 416

80. Word formats for SRC codes . . . . . . 47981. Adding a new I/O storage controller and

disk units . . . . . . . . . . . . . 485

82. Adding compressed disk units to an existingstorage controller . . . . . . . . . . 487

83. Moving disk units from the system ASP to auser ASP . . . . . . . . . . . . . 488

84. Checklist for testing the disaster recoveryplan . . . . . . . . . . . . . . 520

xiv System i: Systems management Recovering your system

Recovering your system

This topic provides general information about backup and recovery options for the System i

environment. It describes the options available on the system, compares and contrasts them, and tellswhere to find more information about them. You can order a printed version of the Recovering your systemPDF (SC41-5304; feature code 8007) with i5/OS software upgrade orders or new hardware orders.

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 System i.v Selecting the right recovery strategy.v Procedures for restoring information to your system.v Device parity protection procedures.v Mirrored protection procedures.

Copyright IBM Corp. 1997, 2008 xv

||||

xvi System i: Systems management Recovering your system

Whats new for V6R1

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

Backup and recovery PDF title change

In V6R1, the title of the Backup and recovery PDF changed to Recovering your system. Recovering your systemis available as both an i5/OS Information Center topic and as a printable PDF.

IPL-related enhancements

You can do an IPL-type D from a tape device attached by a Fibre Channel interface only when it isattached to an adapter without an input/output processor (IOP) on a POWER6 model. For other systemmodels and configurations, a tape device attached by a Fibre Channel interface needs to be set up as analternate installation device. For more information, see Alternate installation device: Overview on page395.

Recovering the vital product data information if the partition does not IPL in A-mode or B-mode onpage 67 documents the procedure for recovering vital product data (VPD) from the flexible serviceprocessor (FSP) during a scratch installation (IPL in D-mode).

Enhancements to how the system restores programs

The system creates *MODULE, *PGM, and *SRVPGM objects that take advantage of the latest hardwarefeatures of the system on which they are created or converted. New hardware features can be usedimmediately. See How the system restores programs on page 273.

The internal object format for program objects is different between i5/OS V6R1 and earlier releases. SeeRestoring programs to a different release on page 275.

File-level backup

You can use the SAV command to save individual files and directories on an integrated server, and theRST command to restore these files. This function is called file-level backup. For more information, see thefollowing topics:v Restoring Linux files on page 287.v Restoring iSCSI-attached integrated servers on page 285.v Restoring IXS or IXA-attached integrated Windows servers on page 285.

Deferred restores

You can restore physical and logical files in any order.

The Restore Library (RSTLIB) and Restore Object (RSTOBJ) commands have been enhanced with a newparameter to defer the restore of dependent database files whose based-on files are missing. Deferredobjects can be logical files or SQL materialized query tables (MQTs).

You can use the new Restore Deferred Objects (RSTDFROBJ) command to complete the restore ofdeferred objects, if the objects that they depend on are now available.

You can use the new Remove Defer ID (RMVDFRID) command to remove all deferred object informationthat is associated with a deferred restore.

Copyright IBM Corp. 1997, 2008 xvii

|

|

||

|

|||||

|||

|||

For more information about deferred restores, see the following topics:v Sequence for restoring related objects on page 37.v Deferring the restore of dependent objects on page 38.v Verifying whether objects are restored successfully on page 50.v Task 5: Restoring libraries to the system auxiliary storage pool on page 192.v Restoring logical files on page 261.v Restoring SQL materialized query tables on page 268.

Journaled libraries

You can save and restore journaled libraries, and recover journaled objects more quickly by replayingjournal entries. Use the Start Journal Library (STRJRNLIB) command to start journaling libraries. Use theApply Journaled Changes (APYJRNCHG) command to replay changes to libraries.

Journaling can start automatically for objects, such as database files, data areas, and data queues, that arecreated, moved into, or restored into a journaled library. The librarys inheritance rules determine whichobjects to start journaling automatically and with what journaling attributes.

For more information, see the following topics:v Restoring journaled objects on page 251.v Task 7: Replaying journaled changes in a disaster recovery on page 305.v Transferring a journal to a nonlibrary user auxiliary storage pool on page 452.

Restoring user-defined file systems

You can use the OBJ or PATTERN parameter on the SAV and RST commands to omit objects fromunmounted user-defined file systems (UDFSs).

Previously, you had to unmount a UDFS before performing a save operation if you wanted to save boththe UDFS information and the objects within the UDFS. If you saved a mounted UDFS, only the objectsin the UDFS were saved, but not the UDFS information. In this release, both the UDFS structure andobjects within the UDFS are saved. You can now restore both the UDFS information and the objects in theUDFS.

For more information, see the following topics:v Restoring an unmounted user-defined file system on page 254.v Restoring a mounted user-defined file system on page 255.v Restore actions for mounted user-defined file systems on page 255.

Restoring security objects

You can save and restore private authorities for an object by specifying the PVTAUT(*YES) parameter onthe save and restore commands.

When restoring all user profiles, if you want to omit Digital Certificate Manager (DCM) data, specify the*DCM value on the OMITSECDTA parameter on the Restore User Profiles (RSTUSRPRF) command. Toomit authority lists, specify the *AUTL value on the OMITSECDTA parameter. To omit function usageinformation, specify *FCNUSG on the OMITSECDTA parameter.

For more information, see these topics:v Restoring private authorities for selected objects on page 231.v Restoring user profiles on page 224.

xviii System i: Systems management Recovering your system

||

||

||||

Encrypted backups

You can encrypt backups to tape media to prevent the loss of personal customer information orconfidential data if the media is lost or stolen. There are two methods for performing encrypted backups:v Hardware encryption using an encrypting tape drive. You can use save/restore commands or Backup

Recovery and Media Services (BRMS) with the encrypting tape drive.v Software encryption using BRMS.You also can encrypt data in user auxiliary storage pools (ASPs) and independent ASPs.

For more information about restoring from an encrypted backup, see these topics:v Task 1: Starting to restore the operating system on page 158.v Recovering from an encrypted backup using software encryption on page 339.v Recovering from an encrypted backup using an encrypted tape on page 340.v Backing up the Encryption Key Manager on page 341.

Encrypted auxiliary storage pools

Disk encryption allows you to encrypt data that is stored in user auxiliary storage pools (ASPs) andindependent ASPs. Disk encryption protects data transmission to and from the disk drive, and preventstheft of data if the disk drive is stolen or resold to another customer. For more information, seeRestoring encrypted auxiliary storage pools on page 342 and Creating an encrypted auxiliary storagepool on page 432.

Restore output file

Several restore commands and the Restore Object List (QSRRSTO) API use the QASRRSTO (restore)output file. For more information, see Restore operation output file information on page 57.

Whats new as of 15 February 2008

The procedure for synchronizing a system in Additional synchronization tips on page 387 has beenupdated.

After you move data to a new system, you might need to restore external stored procedures. For moreinformation, see Restoring previous release user data to a new system on page 359.

Whats new as of 29 January 2008

Backing up and restoring an i5/OS client logical partition on a BladeCenter blade server worksdifferently than the typical procedure for backing up and restoring a logical partition. For moreinformation on these backup and recovery considerations, see these topics:v Restoring logical partitions on page 246v i5/OS client partition considerations

v i5/OS on POWER Blade Read-me First

How to see whats 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 whats new or changed this release, see the Memo to users.

Whats new for V6R1 xix

|

||

||

|

|||||

|

http://www.ibm.com/systems/i/os/i5os/v6r1/blades/readme.html

xx System i: Systems management Recovering your system

Part 1. Saving information on your system

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

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 . . . . . 14Have you configured independent disk pools toswitch between systems in a cluster . . . . . 14Do you use WebSphere MQ, V6 on this system 14Do you use OptiConnect controllers . . . . . 14Do you use network servers . . . . . . . . 15Do you use the Hardware Management Console 15

Printing system information . . . . . . . . . 15Save considerations when checking out objects . . 18Tape write error recovery . . . . . . . . . . 18ObjectConnect function . . . . . . . . . . 19

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

Save/Restore (SAVRST) command. . . . . 22Save/Restore Object (SAVRSTOBJ) command 22Save/Restore Change Objects (SAVRSTCHG)command . . . . . . . . . . . . . 22Save/Restore Library (SAVRSTLIB) command 22Save/Restore Document Library Object(SAVRSTDLO) command . . . . . . . . 22Save/Restore Configuration (SAVRSTCFG)command . . . . . . . . . . . . . 22

Investigating ObjectConnect problems . . . . 22CPFAD84 error codes . . . . . . . . . . 23

Source system-specific error codes fromCPFAD84 message . . . . . . . . . . 23Target system-specific error codes fromCPFAD84 message . . . . . . . . . . 23Source or target system error codes fromCPFAD84 message . . . . . . . . . . 24

Copyright IBM Corp. 1997, 2008 1

||

2 System i: Systems management Recovering your system

Chapter 1. Saving the system

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

You can browse the Backing up your system topic in i5/OS 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, 2008 3

The following information provides an overview and procedures on how to use menu options of the GOSAVE command:v Overview of the GO SAVE command menu options explains how to start the GO SAVE command and

provides more information about the various GO SAVE options.

Figure 1. Save commands and menu options


v Customize your GO SAVE backup instructions allows you to create a list of GO SAVE steps tailored toyour save environment.

v View entire GO SAVE checklist provides you with all of the steps for a GO SAVE operations. Some ofthe steps might not apply to your environment.

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

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. A single plus sign (+)indicates that the option places your system into a restricted state if you run it without prompting forcommands, which means that nothing else can be running on your system when the menu option isselected. If you do prompt for commands, you can skip the ENDSBS command that places the system inrestricted 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.

Chapter 1. Saving the system 5

||||||

||

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.

About this task

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

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 System iNavigator), 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)

ENDSBS 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 provides you with step-by-step instructionson 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.

About this task

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.

As an alternative to this checklist, use Customizing your GO SAVE backup to produce a set ofinstructions that is tailored to your save environment.

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 i5/OS client logicalpartitions. For saving and restoring Virtual I/O Server, see the Advanced POWER Virtualization OperationsGuide.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.


|||

|||||

|||||

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

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 themunavailable. You must save independent ASPs that are geographically mirrored separate fromthis GO SAVE operation.

If the geographically mirrored ASPs remain available during the GO SAVE operation,geographic mirroring is suspended when the system becomes restricted. When you resumemirroring after the save, a complete synchronization is required. Synchronization can be alengthy process.

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. For more information, see Networking for logical partitions.

7. If you have IBM WebSphere MQ for Multiplatforms, V6 (5724-H72), you need to quiesce WebSphereMQ, V6 before you save 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 the

system, 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:


||

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

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 theSave menu. 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.

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.

Specify Command Defaults

Type choices, press Enter.

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

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

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

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

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

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

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

Specify Command Defaults

Type choice, press Enter.

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

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

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


|

||||

||||

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 theinquiry 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 choice for the Start time prompt. You can schedule the start of the save operation up to 24hours later. For example, assume that the current time is 4:30 p.m. on Friday. If you specify 2:30 forthe start time, the save operation begins at 2:30 a.m. on Saturday.

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 signedon, waiting for the job to start. If the system request function is used to cancel the job,your workstation displays the Save menu. The workstation remains signed on with youruser profile and 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 timespecified. 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 sureyou have done 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 running Windows or Linux operating systems using IBM ExtendedIntegrated Server Support for i5/OS, or running Linux or AIX in a 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 does not attempt to remount the filesystems.

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. Press the Enter key. If you chose a later start time, your display shows message CPI3716. The

message tells when the save operation was requested and when it will start. You cannot use thedisplay until the save operation is completed. The input-inhibited indicator might appear. You havecompleted the steps for setting up the save operation.If you did not choose a later start time, continue with step 25. If the value for QSYSOPR messagequeue delivery is *BREAK with a severity level of 60 or lower, you must respond to the EndSubsystem (ENDSBS) messages. This is true even if you plan to run an unattended save operationspecifying a start time of *CURRENT.

25. If you responded Y to the system prompt, Prompt for commands, the End Subsystem displayappears. Type any changes and press the Enter key. While the system is ending subsystems, you seethe following messages. You must respond to them if the QSYSOPR message queue is set to *BREAKwith a severity level of 60 or lower. Each message appears at least twice. Press the Enter key torespond 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 27.26. 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.27. 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.

28. Mount all other user-defined file systems at this point if you unmounted them for the saveoperation.

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

30. 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.


||

31. 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 i5/OS Clusterstechnology.

32. Restart the device cluster resource group to enable resiliency.33. When your independent ASP was saved, the Qdefault.UDFS was unmounted, if you chose to

unmount file systems. In order to use the independent ASP again, remount Qdefault.UDFS. Do thisstep for each independent ASP that you saved.MOUNT TYPE(*UDFS) MFS('/dev/iasp_name/Qdefault.UDFS') MNTOVRDIR('/iasp-name')

Optional features that affect your backup

Optional 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 systemsAbout this task

A 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 tapesAbout this task

If 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 storageAbout this task

Virtual 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 poolsAbout this task

An 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 clusterAbout this task

A 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, V6 on this systemAbout this task

The IBM WebSphere MQ for Multiplatforms, V6 (WebSphere MQ, V6), 5724-H72, licensed programprovides application programming services that enable you to code indirect program-to-programcommunications that use message queues. This enables programs to communicate with each otherindependently of their platforms, for example, between the z/OS and i5/OS operating systems.

To check whether you have installed WebSphere MQ, V6, 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, V6 is installed, 5724-H72 appears in the Description column for licensed program5761-SS1.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 controllersAbout this task

OptiConnect 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 5761-SS1, i5/OS - 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

5761-SS1.

Do you use network serversAbout this task

Several 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 ConsoleAbout this task

If 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.

About this task

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 using logical partitions, print the logical partition configuration information.a. From the primary partition, type STRSST on a command line and press Enter.


|

|

||

|

|

|

||

|

|

|||

b. If you are using SST, select option 5 Work with system partitions, and press Enter. If you areusing DST, select option 11 Work with system partitions, and press Enter.

c. From the Work With System Partitions menu, select option 1 Display partition information.d. To display all system I/O resources from the Display Partition Information menu, select option 5.e. At the Level of detail to display field, type *ALL to set the level of detail to ALL.f. Press F6 to print the system I/O configuration.g. Select option 1 and press Enter to print to a spooled file.h. Press F12 to return to the Display Partition Information menu.i. Select option 2 Display partition processing configuration.j. From the Display Partition Processing Configuration display, Press F6 to print the processing

configuration.k. Press F12 to return to Display Partition Information display.l. Select option 7 Display communications options.m. Press F6 to print communication configuration.n. Select option 1 and press Enter to print to a spooled file.o. Return to a command line and print these three spooled files.

3. 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)4. 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.

5. 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.

6. 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 (Displayfile description) 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.

7. 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 c

version 6 release 1 - ibm - united states€¦ · system i systems management recovering your...

Documents