Re: IBM System Storage TS3100 Tape library; unnecessary tape verification by restoring object?

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Assuming you are not initializing the tape every time you use it, the 
system keeps track of the reads/writes and all errors by tape.  You can 
find those stats in SST

Start a service tool
Product Activity Log
Work with removable media lifetime statistics

If you initialize tapes on every use, you reset the statistics on that 
tape name, so it's best if you use the expiration dates on the tape and 
files to determine the next use of the tape.

Given this information, my vote would be no, those steps are not needed, 
you are spending more time verifying things than you need.


Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 11/14/2011 2:21 PM, elehti@xxxxxxxxxxxxxxxxxx wrote:
> Am I doing some unnecessary, over-the-top tape verification with our IBM
> System Storage TS3100 tape library?
> Are steps 5 and 6 actually needed so as to confirm that the tapes are
> readable and that data can be restored from them?
> Does the TS3100 tape unit have more than adequate verification
> algorithms in it that confirm that the data on tape is readable and
> restorable?
>
>
> Step 1:  GO BACKUP and save most user libraries and other objects to the
> LTO4 tapes.
> Step 2:  Seven libraries get saved  with these parms.  E.g.
>           SAVLIB     LIB(CRMSAT) DEV(TAP01) ENDOPT(*LEAVE) +
>               SAVACT(*SYNCLIB) SAVACTWAIT(360) +
>               SAVACTMSGQ(QSYSOPR) ACCPTH(*YES)
>
> Step 3: Save some of the IFS folders:  e.g.
>          SAV DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/WWW')) OUTPUT(*PRINT)
>
>
> Step 4:  Rewind and DSPTAP
> Step 5: DLTF a file from library VERIFYBKUP and get ready to restore
> this file from tape
> Step 6:  RSTOBJ from tape the file that step 5 deleted.
>
> Step 7:  CHKTAP     DEV(TAP01) ENDOPT(*UNLOAD)  to unload this tape and
> mount next tape for tomorrow