Unit 3. Save/Restore

  • View
    53

  • Download
    0

Embed Size (px)

DESCRIPTION

Unit 3. Save/Restore. 3.1 OS/400 save and restore concepts 3.2 Save data offline3 3.3 Restoring data to system 3.4 Automatic Backup by scheduling. Unit Objectives. OS/400 Save/Restore Facility. Tape Fundamentals. Purposes of Tape on iSeries. Tape Labels. Tape Menu. - PowerPoint PPT Presentation

Text of Unit 3. Save/Restore

  • Unit 3. Save/Restore3.1 OS/400 save and restore concepts3.2 Save data offline33.3 Restoring data to system3.4 Automatic Backup by scheduling

  • Unit Objectives

  • OS/400 Save/Restore Facility

  • Tape Fundamentals

  • Purposes of Tape on iSeries

  • Tape Labels

  • Tape Menu

  • Tape Preparation(INZTAP)

  • Displaying a Tape (DSPTAP)

  • Contents of Tape - *LABELS Format

  • Contents of Tape - *SAVRST Format

  • Duplicate Tape (DUPTAP) commandThe Duplicate Tape (DUPTAP) command copies the contents of one tape to another tape.You must have two tape drives or a tape media library device with two tape resources to use this command.

  • Tape message(1/2)When you using tape do something ,maybe receive the message about tape:For example: Message ID . . . . . . . . . : CPF6718 Message . . . . : Cannot allocate device tap01. Cause . . . . . : The device could not be allocated when trying to open the device file to do the command function. The device may be varied off, in use by another job, or in use by an open file in this job. Recovery . . . : Use the Work with Configuration Status WRKCFGSTS) command specifying the *DEV value for the CFGTYP parameter to verify that the device is varied on and to determine what job is using the device. Try the command again when the device is available.

  • Tape message(2/2) Message ID . . . . . . . . . : CPF6760 Message . . . . : Device tap01 not ready. Cause . . . . . : -- The tape may not be loaded. -- The tape may have been a cleaning cartridge. -- If the device is a tape media library device, then the cartridge may not have loaded successfully. Recovery . . . : Do one of the following: -- If the device is a reel tape drive, make sure the tape is loaded and the online light is on. -- If the tape device is a 1/4 inch cartridge tape drive, unload and reload the cartridge. -- If the device is a tape media library device and the cartridge was not a cleaning cartridge, attempt the command again. -- If the tape device is a 1/2 inch cartridge tape drive or an 8 millimeter cartridge drive, ensure the tape is loaded and the tape drive is ready. If the problem continues, start problem analysis (ANZPRB command). Technical description . .

  • 3.2 Saving Data offline

  • Information That Can Be Saved and Restored

  • Save Menu ++++++++++++

  • Save Commands

  • Saving the System and User Data

  • Menu Options

  • Save Storage(SAVSTG) vs Save System(SAVSYS)SAVSYS : Required Restricted State can save:SAVSTG : Required Restricted State Copies DASD track by track. Can Only restore entire system. Cant restore single object.

    OS/400 system objects. Licensed internal code. Optionally, the system configuration. System resource management objects. Security objects. All PTFs.Can Not Saved: IBM licensed programs. Optional parts of OS/400. Folders. Libraries QGPL and QUSRSYS. Any user libraries.

  • You Cannot Save

  • When an Object Is Saved

  • Save Considerations

  • Save File ExampleCRTSAVF FILE(LYSAVF) or CLRSAVF FILE(LYSAVF)SAVLIB LIB(LY) DEV(*SAVF) SAVF(LYSAVF)DSPSAVF FILE(LYSAVF)SAVSAFDTA SAVF(LYSAVF) DEV(TAP02)*:If the library which include save file LYSAVF does not exit in the library list,you must specify the library. For example:LIBA/LYSAVF

  • Display Job Log or Display History Log to see if saving is successfulDSPLOGDSPJOBLOGNote:If you want know why an object was not saved ,you must use DSPJOBLOG

  • SAVLIB and several important parameters

  • Use optimum block (USEOPTBLK) Specifies whether or not the optimum block size is used for the save operation. The possible values are: *YES : The optimum block size supported by the device is used for save commands. If the block size that is used is larger than a block size that is supported by all device types, then: o Performance may improve. o The tape file that is created is only compatible with a device that supports the block size used. Commands such as Duplicate Tape (DUPTAP) do not duplicate files unless the files are being duplicated to a device which supports the same block size that was used. o The value for the DTACPR parameter is ignored. If the target release value that is specified is earlier than V3R7M0 then the block size supported by all device types is used. *NO :The optimum block size supported by the device is not used. Save commands use the default block size supported by all device types. The tape volume can be duplicated to any media format using the Duplicate Tape (DUPTAP) command.

  • Target release (TGTRLS) Specifies the release of the operating system on which you intend to restore and use the object. When specifying the target-release value, the format VxRxMx is used to specify the release, where Vx is the version, Rx is the release, and Mx is the modification level. For example, V2R3M0 is version 2, release 3,modification level 0. To specify that an object be saved for distribution to a system at a different release level than the system on which the save operation is to occur, the procedure differs for program or non-program objects and by the release level on which a program object is created. If, for example, you are saving an object for distribution to a target system running on an earlier release, you have the following choices: *CURRENT :The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed. *PRV :The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed. target-release :specify the release in the format VxRxMx. The object can be restored to a system with the specified release or with any subsequent release of the operating system installed. Valid values depend on the current version, release, and modification level, and they change with each new release. Press F4 to see a list of valid target release values. Notes: 1. If LIB(*NONSYS), LIB(*ALLUSR), or LIB(*IBM) is specified, only the current release can be the target release 2. Not all objects can be targeted to another release. To find out which objects are supported, see the chart in the Backup and Recovery book, SC41-5304. .

  • Save access paths (ACCPTH) Specifies whether the logical file access paths that are dependent on the physical files being saved are also saved. The access paths are saved only in the case of the following: o All members on which the access paths are built are included in this save operation. o The access paths are not invalid or damaged at the time of the save. The system checks to ensure the integrity of the access paths. Any discrepancies found by the system will result in the access paths being rebuilt. Informational messages are sent indicating the number of logical file access paths saved with each physical file. All physical files on which an access path is built must be in the same library. This parameter does not save logical file objects; it only controls the saving of the access paths. More information on the restoring of saved access paths is in the Backup and Recovery book, SC41-5304. The possible values are: *NO : only those objects specified on the command are saved. No logical file access paths are saved. *YES : The specified physical files and all eligible logical file access paths over them are savedData compression (DTACPR) Specifies whether data compression is used. The possible values are: *DEV : If the save is to tape and the target device supports compression, hardware compression is performed. Otherwise, no data compression is performed. Note: