topic Re: check_tape_recovery in Operating System - HP-UX

check_tape_recovery

DIERICKX_1 — Wed, 12 Sep 2007 04:31:22 GMT

Hello,

I have HP-UX servers 9000 :
One is rp7420 and the other one is rp4440.

I have installed patchs HP-UX 11i V1

I can make ignite bande with the command make_tape_recovery.

But i haven't the command check-tape-recovery

So i can't garanty to the client that my bande ignit is really OK.

Is anybody knows which patch has this command or how can i vezrify and check my ignite bande ?

Re: check_tape_recovery

Torsten. — Wed, 12 Sep 2007 04:33:28 GMT

For PA-RISC based backup do this:

# mt -f /dev/rmt/?mn rew
# mt -f /dev/rmt/?mn fsf 1
# tar -tvf /dev/rmt/?mn

So you can check the contents of the archive.

Re: check_tape_recovery

Ludovic Derlyn — Wed, 12 Sep 2007 04:41:59 GMT

hi,

check also log in /var/opt/ignite/recovery/

Regards
L-DERLYN

Re: check_tape_recovery

whiteknight — Wed, 12 Sep 2007 04:43:04 GMT

Hi,

These are the steps to follow to verify whether your Ignite
make_recovery tape is good:

1. Check the log generated during the Ignite backup:

/var/opt/ignite/logs/makrec.logxx

2. Boot from the tape and interrupt the boot process before
non-interactive recovery commences, and then abort the install.
This will verify whether the first image on the tape is bootable.

Note: There is a command shipped with Ignite, copy_boot_tape(1m)
that could also be of use to pull the LIF and the archive
off of a make_recovery tape.

You can use lifls(1) or lifcp(1) to examine the boot LIF
contents and pax(1) or tar(1) to examine the archive.

3. The second image on the tape is the tar archive of the OS and
possibly other files (depending on the options to make_recovery).

a) Skip over the first image with mt command using the
appropriate tape device file;

mt -f /dev/rmt/0mn rew

mt -f /dev/rmt/0mn fsf 1

b) Verify the contents of the tar image with the tar
command using the appropriate device file;

tar tvf /dev/rmt/0m

WK
please assign points

Re: check_tape_recovery

wittie — Wed, 12 Sep 2007 06:41:51 GMT

If make_tape_recovery was run locally, look up the log files at

/var/opt/ignite/recovery//

If it was run from the Ignite-UX server, look up log files at

/var/opt/ignite/recovery/clients/0x{LLA}/recovery/

Check the recovery.log and flist for warnings and errors.

Checking boot volume on tape (LIF header)
# /opt/ignite/bin/copy_boot_tape -u /dev/rmt/0mn -b -d /tmp
# /usr/bin/lifls -l /tmp/bootimage

Checking the tar archive on the tape
# /usr/bin/mt -t /dev/rmt/0mn rew
# /usr/bin/mt -t /dev/rmt/0mn fsf 1
# /usr/bin/tar tvf /dev/rmt/0m
Note: 0m not 0mn

Extracting single files from the tar archive
# /usr/bin/mt -t /dev/rmt/0mn rew
# /usr/bin/mt -t /dev/rmt/0mn fsf 1
# /usr/bin/tar xvf /dev/rmt/0m filename1 filename2

Re: check_tape_recovery

DIERICKX_1 — Wed, 12 Sep 2007 06:52:17 GMT

I will try the solutions proposed when i will do a new bande ignite this month

I was nonetheless surprise that nobody talks about this command check_tape_recovery.
An expert HP consultant told me that this command existed

Re: check_tape_recovery

James R. Ferguson — Wed, 12 Sep 2007 06:52:19 GMT

Hi:

If your Ignite release isn't up-to-date, then perhaps this is the reason for the missing command. You can refresh your Ignite binaries from here:

http://www.docs.hp.com/en/IUX/download.html

I noticed that you posted "check-tape-recovery" with hyphen characters instead of the correct command with underscores: 'check_tape_recovery'. Is that your problem?

Regards!

...JRF...