make_recovery error

[Elton Witbooi]

Hi all,

I am trying to make an ignite tape using the ignite-ux "make_recovery" command. The complete command reads as "make_recovery -A -v -C -d /dev/rmt/0m".
The process starts off well but terminates within a minute with the following message: "Call to system failed. errno=0 Cleanup"
Is there anyone who can help?

[Paula J Frazer-Campbell]

Hi
You are using an older version of ignite, download and install the latest version.

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

/opt/ignite/bin/make_tape_recovery -x inc_entire=vg00 -I -v -a /dev
rmt/

Will cover your entire vg00


HTH

Paula

[harry d brown jr]

Elton

Read this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x041b8ffa98a2d5118ff10090279cd0f9,00.html

The author claims it was resolved after a reboot. I have no idea as to why, but what the hell, its worth a shot, even though it's brutal.

live free or die
harry

[Clemens van Everdingen]

Hi,

Even with later versions you are still able to use make_recovery.

I would check the /var/opt/ignite/logs/ directory for logging.
for example: makrec.log and see if something is more explained than the error itself.

Might have something to do with lvm problems.
Might be important to solve these problems first.

C.

[Martin Burnett_2]

Hello Elton,

The errno=0 is non-specific and very early in the make_recovery process. It is just testing an exit status (waitpid). My guess is the real cause of your problem is the /dev/rmt/0m. This is an invalid device for make_recovery to use. If you run lssf you would see something like:

# lssf /dev/rmt/0m
stape card instance 1 SCSI target 0 SCSI LUN 0 at&t best density available at address 8/16/5.0.0 /dev/rmt/0m

Note that this device is NOT a no-rewind device that is required by make_recovery (make_tape_recovery).

# lssf /dev/rmt/0mn
stape card instance 1 SCSI target 0 SCSI LUN 0 at&t no rewind best density available at address 8/16/5.0.0 /dev/rmt/0mn

This is because make_recovery works in 2 distinct steps.

1. It copies the LIF onto the tape using dd which allows you to boot from the tape.

2. It then creates the archive on the tape for restoring the system.

If a "rewind" device is used then the LIF would be applied, the tape would rewind and the archive would then overwrite the LIF making the tape unusable.

Try your command again using a no rewind device. I do agree with Paula that you should upgrade and use the make_tape_recovery command simply because there are other enhancements and features available.

Thanks for participating in the forums.

Martin