create recovery tape from Ignite-UX server

[kholikt]

I have do a make_net_recovery from the client. Now I want to actually create a self-contained recovery tape. I follow the following instruction.

Creating a Bootable Archive Tape
================================

The following instructions explain how to create a self-contained
recovery tape for a recovery configuration already stored on an Ignite-UX
server via network system recovery (see make_net_recovery(1m)). It is
important that the archive fit onto a single tape.

Throughout these instructions, the following assumptions are made:

- The hostname of the machine the archive was created for is "sys1".
- The archive was created at "1999-03-12,09:00".
- The archive will fit onto a single tape.

There are only two steps required to build this tape:

- First, a LIF file must be constructed. It will contain the
Ignite-UX tools and environment, the config files produced for the
recovery archive, and the scripts used during recovery. The LIF is
produced via the make_medialif command.

- Second, the LIF and the archive itself must be written to a tape.


Step 1 - Build the LIF
----------------------

First, use make_medialif to build the LIF file:

cd /var/opt/ignite/clients/sys1/recovery/1999-03-12,09:00
/opt/ignite/bin/make_medialif -f system_cfg -f control_cfg -f archive_cfg -C "1999-03-12,09:00 sys1 recovery image" -l /var/tmp/my_lif -a -r

Replace with the "uname -r" value on the machine where the
archive was created. You can also get this value by looking at
the "release" keyword contained in the system_cfg file.


Now modify the LIF file to set it up for use on the tape:

/opt/ignite/bin/instl_adm -d -F /var/tmp/my_lif > /var/tmp/cfg

Edit the /var/tmp/cfg file and add the following lines to the end of
the file:

control_from_server=FALSE
run_ui=TRUE


OR, if you just want the recovery to proceed without any interaction, make
run_ui FALSE and specify to allow warnings, as in the following:

control_from_server=FALSE
run_ui=FALSE
env_vars += "INST_ALLOW_WARNINGS=10"

Then, issue the following command:

/opt/ignite/bin/instl_adm -F /var/tmp/my_lif -f /var/tmp/cfg


Step 2 - Write the tape
-----------------------

First, figure out which tape device file you can use to write the tape.
The device file must match the tape drive type you will use when
actually recovering the system. For example, a tape created with a
DDS-1/no compression device file will work in any DDS drive. Also, the
tape device file must be the no-rewind type. For the rest of this
example, assume that /dev/rmt/c1t0d0DDS1n is a no-rewind DDS-1/no
compression device file.

Now it's just a matter of rewinding the tape, writing out the
LIF, writing out the archive and then rewinding again:

mt -t /dev/rmt/c1t0d0DDS1n rew
dd if=/var/tmp/my_lif of=/dev/rmt/c1t0d0DDS1n obs=2k
dd if=/var/opt/ignite/recovery/archives/sys1/1999-03-12,09:00
of=/dev/rmt/c1t0d0DDS1n obs=10k
mt -t /dev/rmt/c1t0d0DDS1n rew

In this example, the archive is retrieved from the standard location on
the Ignite-UX server for this host. If you have chosen to put the
archive elsewhere, refer to that location instead.


The problem is when I tried to read the content of the tape I will get the Tar: blocksize = 4
directory checksum error

I used the following command to read the content of my tape.
mt -f /dev/rmt/c3t0d0DDSn fsf 1
tar -tvf /dev/rmt/c3t0d0DDS

[Tom Geudens]

Hi,
It would seem that you already read through the threads on "how to verify an ignite backup on tape" http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xfa73abe92dabd5118ff10090279cd0f9,00.html

Did you check /var/opt/ignite/logs/makrec.logxx
for errors ?
The "directory checksum error" often indicates a physical error on the tape. I would try to clean the tapedrive, create another tape and try again (if you haven't done that already).

Regards,
Tom