make_recovery can't contact server

[Ed Hon]

I upgraded to Ignite/UX 3.2. When I ran make_recovery -A -i -v -d /dev/rmt/0mn , the message "Can't contact server 10.214.129.1" popped out, but make_recovery continued. I found KBRC00003003, which said to check tftp is running. I did and it was. Any ideas? Is my make_recovery tape any good?

[Rick Garland]

I wouldn't trust the make_recovery tape unless it is verified. And even then, I would have my doubts.

Check the /etc/hosts file. Is there an entry for the loopback and the IP of the server itself?

[Ed Hon]

Yes, both the server and the loopback entries are in /etc/hosts:

10.64.116.2 hpsym hpsym.
127.0.0.1 localhost loopback

[Ed Hon]

HP Support says the lab knows about this problem. They suggested going to make_tape_recovery, which doesn't have this problem. I did, and it doesn't.

[James R. Ferguson]

Hi Ed:

I've seen the same error with make_recovery in its 3.2 version. I've switched to the new make_tape_recovery and find it far superior. It offers more configuration possibilities and collects and formats its logs in a far superior fashion to its predecessor, in my opinion.

Regards!

...JRF...

[Mark Mitchell]

verify ignite
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