mksysb failures

[cichkid]

In running of a mksysb file I have recieved the following error message:

Backing up 29094 files..............................
317 of 29094 files (1%)..............................
318 of 29094 files (1%)...........................backup: 0511-449 An error occurred accessing ./var/applogs/was/ffdc/mohr1_on_node2_exception_03.07.16_20.50.23.log: A file or directory in the path name does not exist.
...
6225 of 29094 files (21%)...........................
0512-003 mksysb may not have been able to archive some files.

This leads me to beleive that the file existed at the begining of the mksysb but was not present at the time that the file was to be backed up. Is this correct?

Is there a way to know if the mksysb is still valid, without the failed file?

 

[Tony48]

You are reading it correctly.
At the beginning, mksysb creates a list of files
to be archived.

Later, 'cat's the filelist to the backup command...
...which is complaining about the missing file.

As to whether it is a good backup...
...It really depends on whether the file that
disappeared is important... otherwise, assuming
no other error messages were output, it should be good.

-tony

 

[ProbablyDown]

I would test the mksysb by doing the following:

1) Data Verification
# tctl -f /dev/rmt0 rewind
# restore -s4 -Tqvf /dev/rmt0.1 > /tmp/mksysb.log

This will show you that the data saveset is good

2) boot Verification

Shut down system and boot from the mksysb tape. Do not restore any of the data from the tape. Make sure the PROMPT field in the bosinst.data file is set to YES otherwise it will automagically start the restore...

That will tell you that the boot saveset is good.