make_recovery_tape issue

[james gould]

Found out that the root disk of system has a bad block on it as reported in the syslog file. Have a make_recovery_tape that was created but finished with warnings about a few files, none important because of I/O errors which are I think related to the disk error. I am going to use the tape to boot to another drive, and just want to make sure that everything is fine. Again it finished with -1 and warnings but looks like everything else is fine.

[Patrick Wallek]

You method sounds OK to me. Testing the restore to a different drive is a good way to do this.

[james gould]

Ok, just wanted to check and see if someone else had run into this and that the tape should be good. I know I have to test it out but just want to make sure that I am not missing anything.

[Clifford Chi]

Hi James,

Do you mind to check your "/var/opt/ignite/log/makrec.log1" file? This log file consists of all "make_recovery" session that you have conducted before.

Look for the date where your make_recovery tape was created and observe it. Whether an Ignite tape is created successfully or not, you shall see at the end of the session has a line stated the tape is created successfully or not.

If I/O error reported in the log for archiving vg00 content, I doubt the tape was created successfully.

Read test for Ignite tape:

# mt -t /dev/rmt/0mn fsf 1
# tar -tvf /dev/rmt/0mn <--- this will list out what are files being backup (in fact, you redirect the output to a file and compare with your "/var/opt/ignite/log/makrec.log2" that consists your archive content log for last make_recovery session.)

[james gould]

Did not find any logs in /var/opt/ignite/logs
as described.

The question that I have is if the make recovery completed without aborting i.e. it ran to completion, can it still be used to boot a system back up. If certain files not related to booting are not on the tape will the system still boot?

[Deoncia Grayson_1]

I agree with Patrick, testing the tape on a different drive seems like a great idea and work from that point on recovering whatever files you are missing. It should work fine as long as you're not missing any system files.

[Clifford Chi]

Hi James,

I was assuming you are using "make_recovery" since you don't find any log files in /var/opt/ignite/logs.

So, are you using "make_tape_recovery"? If so, look at the following logfiles:

1. /var/opt/ignite/recovery//recovery.log ( where reflects the date and time stamp the ignite created ) And the same, at the end of the log, look for the statement whether the tape created successfully or not.

2. /var/opt/ignite/recovery//flist ( archive content )

Note: there is a directory called "latest" in "/var/opt/ignite/recovery" which is link to the last ignite tape creation date.