Chapter 101.  Backup and Recovery2.  Introduction      *To backup is to copy some or all of a computer's software to 
       a storage location independent of the computer.3.    *To restore is to copy that remotely stored data back onto 
       the computer and be able to use it. 4.  Reasons to Backup	*Object failure: 		-Most common reason. 		-Objects deleted or damaged or corrupted.  	*System failure: 		-Less common. 		-Power lost or disk units fail etc. 5.  Reasons to Backup
       *Site movement: 		-Company moves from one computer to another. 		-Common for disaster recovery. 	*Efficiently save infrequently used 	 information: 		-Large objects take up disk space 
                 infrequently used. 		-Site loss. 		-Extremely rare. 		-Flood, fire, riots, etc 6.  Copy Vs. Save	*Copy command: 		-Two copies of the file. 		-Accessed at any time. 		-Could be lost if disk problem.	*Save command: 		-Data files cannot be accessed except by restore. 		-Object header updated. 		-Off-site security. 7.   6 Object Categories	*Operating objects: 		-MULIC/FULIC,		-Microcode. 8.   	*System objects: 		-OS/400 licensed program, 		-User profiles, 		-Private authorities, 		-Device configuration, 		-System and network values. 9.   *Support objects: 		-System libraries required  normal operation,		-Compiler, 		-Utilities. 10.  *Production objects: 		-Data files, 		-Data areas, 		-Job descriptions, 		-Program, 		-Objects running applications. 11.   *Development objects: 		-Source files. 	*End-user objects: 		-Data associated with applications. 12.  Backup Media	*In general, objects can be saved to: 		-Magnetic tape. 		-DASD (through a save file). 		-Diskette. 		-Another AS/400. 		-Optical Media. 		-Save file (object type *SAVF). 13.  Initialize Tape (INZTAP)	SEE TABLE() 14.  Initialize Diskette (INZDKT)	SEE TABLE() 15.  Save Command Menu	SEE TABLE() 16.  Save Command Menu	SEE TABLE() 17.  Save Command Menu 	SEE TABLE() 18.  System Auxiliary Storage	SEE TABLE() 19.  Save Storage	*Copies DASD track by track.	*Can Only restore entire system.	*Can't restore single object.20.  Save System	*Required – Restricted State.	*It will save:		-OS/400 system objects. 		-Licensed internal code. 		-Optionally, the system configuration. 		-System resource management objects. 		-Security objects. All PTFs. 21.   *Not Saved:		-IBM licensed programs. 		-Optional parts of OS/400. 		-Folders. 		-Libraries QGPL and QUSRSYS. 		-Any user libraries. 22.  SAVSYS Command	SEE TABLE() 23.  Save Configuration 	*Device configurations are: 		-Line descriptions. 		-Controller descriptions. 		-Device descriptions. 		-Mode descriptions. 		-Class-of-service descriptions. 		-Network interface descriptions. 		-Connection lists. 24.  		-Configuration lists. 		-System configuration. 		-Hardware resources. 		-Token ring adapter data25.  Save Configuration Screen	SEE TABLE() 26.  Save Configuration Screen 2	SEE TABLE() 27.  Save Security Data	*The items saved are: 		-User profiles. 		-Private authorities to objects. 		-Authorization lists. 28.  Save Security Data Screen 1	SEE TABLE() 29.  Save Security Data Screen 2	SEE TABLE() 30.  Save Library Screen 1	SEE TABLE() 31.  Save Library Screen 2	SEE TABLE() 32.  Save Library Screen 3	SEE TABLE() 33.  Libraries Save	*Libraries can be saved to: 		-Tape. 		-Diskette. Save File. 		-Optical Media—but only if the command 
                 parameter lib is not set to the generic 
                 values: 		     -Save-while-active feature *ALLUSR 		     -*IBM 		     -*NONSYS 34.  SAVLIB Cannot Save	*QSYS 	*QDOC 	*QSPL 	*QRPLOBJ 	*QTEMP 	*QSRV 	*QRECOVERY 35.  What Is Saved?	SEE TABLE() 36.  What Is Saved?	SEE TABLE() 37.  Save Changed Object Screen	SEE TABLE()  38.  Save Changed Object Screen	SEE TABLE() 39.  Save Changed Object Screen	SEE TABLE() 40.  Save Changed Object Screen	SEE TABLE()