check_recovery

[mvr]

Every Monday I create recovery tape with the command make _recovery -A
When I execute command check_recovery I get next error:
check_recovery
/var/opt/ignite/recovery/makrec.last: No such file or directory
check_recovery(601): The make_recovery status file does not exist because
the file was removed or the last invocation of make_recovery was without
the -C option.

How can I "tell" command to look on the tape instead of directory.

Thanky in advance.

Miro

[Patrick Wallek]

You can't!

In order for check_recovery to work, you must run make_recovery with the '-C' option.

Be aware though, that if / when you upgrade version of Ignite/UX and upgrade to the make_tape_recovery command, which you should, the check_recovery command will not be available as there is not mechanism in make_tape_recovery that is similar to the '-C' option of make_recovery.

[James R. Ferguson]

Hi:

You can't. The concept of 'check_recovery' was that 'make_recovery' logged the files and their timestamps and when 'check_recovery' was run, the timestamps of files on the disk were compared in an effort to deduce what had changed.

'check_recovery' is deprecated. In fact, you should use 'make_tape_recovery' in lieu of 'make_recovery'. This is well documented on the Ignite site. I suggest you obtain a current copy of Ignite and being using 'make_tape_recovery':

http://www.software.hp.com/products/IUX/index.html

Regards!

...JRF...

[mvr]

Thank you ....

[Steven E. Protter · Accepted solution]

Here's a good make_tape_recovery script that cron can run.

attached....

I don't seem to have a check command handy. I know I've done it. I'll get back to you.

Steve

[Jeff Schussele]

Hi Miro,

As noted the check_recovery only works with make_recovery -C.

The easiest way to check the tape is as follows:

#mt rew #rewind the tape
#mt fsf 1 #move the tape one file space forward
#tar tvf /dev/rmt/0mn #List the contents of tape via tar

If all the system files start displaying the tape is readable.
NOTE: This does NOT guarantee that the tape is bootable. The only way I know to check this is to actually try to boot it on the system or at least a comparable test system.

Rgds,
Jeff

[Brian M Rawlings]

Miro: you can also 'test' the LIF portion of the make_recovery tape for readability, although this will not prove that it's bootable. To test the first record on the make_recovery tape, use the following syntax:

dd if=/dev/rmt/0mn of=/dev/null bs=2k (substitute your tape name if different than 0mn)

If no error, the boot part of the tape is readable.

Jeff's idea about booting it on another test system is good too. When the tape boots, however, it might automatically begin the restore process without waiting for input. To avoid this, make sure to use the '-i' (interactive) switch on the make_recovery command, to prevent the recovery process from trashing the boot disk on the test box.

Regards, --bmr

[fg_1]

Here is a script that we use to create a make_recovery bootable tape.

We do use the -C option and thus allowing us to run check_recovery on the tape.

Use as you want, modify if you wish.

Gl

Frank G.

[Patrick Wallek]

Frank,

The check_recovery does NOT run against the tape you created, it runs on the server to see if it thinks you need to run another make_recovery tape.

[fg_1]

Thank you for the correction patrick. My error.