check_recovery

[manu_15]

Hi All,

How check_recovery works...whether it compare the tape contents with the current system Or it compare the make_recovery log with the current system...ie. whether the tape should be in the drive for running check_recovery..

Please confirm..

Thanks in advance

[Ermin Borovac]

If you run make_recovery with -C option it will create /var/opt/ignite/recovery/makrec.last file containing names, mtimes and checksums of all files included in the archive. check_recovery command compares information found in this file with files on the system.

Having said that, you should know that make_recovery has been obsoleted and as far as I know it's not included in the latest Ignite-UX version. It's replacement is make_tape_recovery, however, this command doesn't (as yet) have support for check_recovery.

[Joseph Loo]

hi,

man check_recovery should tell u exactly what u need to know.

it "compare the current system to the System Recovery status file created by the last invocation of make_recovery".

however, only with option C in make_recovery which creates the System Recovery status file allows this comparison.

do take note that make_recovery command is replace by make_tape_recovery. however, there is currently no similar command to check_recovery for make_tape_recovery.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=11989

regards.

[Patrick Wallek]

Don't bother with check_recovery. My rule of thumb is, if you think you might need to make a new make_tape_recovery tape, then you probably do.

If you were to create a tape with the '-C' option to make_recovery (make_recovery itself is obsolete and doesn't exist in the latest version of Ignite), it would create a status file when the tape is created. Then when check_recovery is run, it references the status file to check the system status. Using the '-C' can add significant time to the tape creation process. You do not need the tape in the drive to run check_recovery.

For more information check the make_recovery man page and the check_recovery man page.