Backup/Recover procedure

[John McDen]

I installed ignite B.3.6.82 on HP-UX Ver. 11.0 and I need help with the backup procedure and restore procedures.

Thanks in advance and this forum has been a great help to me since I am new to HP.

[someone_4 · Accepted solution]

Hi there I just did this yesterday and did my first backup today and tested the recovery process. Here are the notes that I have compiled on this issue so far.

To find your tape drive
# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.0.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t0d0BESTn
/dev/rmt/0mb /dev/rmt/c0t0d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t0d0DDS
/dev/rmt/0mnb /dev/rmt/c0t0d0DDSb
/dev/rmt/c0t0d0BEST /dev/rmt/c0t0d0DDSn
/dev/rmt/c0t0d0BESTb /dev/rmt/c0t0d0DDSnb

Now that you properly used ioscan it appears that your tape drive is ready - assuming you have a tape inserted in the drive. Note that you have both a long name e.g. c0t0doBEST and simply a 0m. Both of these are equivalent and typically you use the 'short' name. The suffixs:

0m - Rewind on close
0mn - Norewind on close; you can append several sessions to the tape
0mb - Rewind 'Berkeley' style
Omnb - No rewind, 'Berkeley' style

use the 0mnb if you are doing any sort of multiple sessions to the same tape.

Test 1 - put a tape in the drive and do mt -t /dev/rmt0m rewind

Test 2 - write something on the tape, say a tar file

tar cf /dev/rmt/0m somefile_or_dir

Test 3 - Try it with make_tape_recovery

# to back up entire vg00
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -x inc_entire=vg00


-a tape_drive
Specifies the tape drive device file that will be used for
archiving by make_tape_recovery. Default is /dev/rmt/0mn
(This option is equivalent to -d option in make_recovery)
unless the /var/opt/ignite/recovery/default file exists on the system.

-I Cause the system recovery process to be interactive when
booting from the tape. By default, when the systems boots
from the recovery tape it will give you 10 seconds to
interrupt the automatic recovery process in order to
interactively make modifications. When the -I option is
specified, booting from the tape will always present the
interactive menus. Using this option is useful when you
know you need to make configuration changes during the

-v Display verbose progress messages while creating the system
recovery archive. Includes information such as which volume
groups/disks will be included in the system recovery archive.

-x inc_entire=/dev/dsk/|vg_name
Includes all file systems contained on the specified disk or
volume group. Use a block device file of the format
/dev/dsk/ when specifying a whole-disk (non-LVM) file
system. Use the volume group name (such as vg00) when you
want all file systems that are part of that LVM volume group
to be included in the archive.

To recover interup the boot process
at the promt enter
#sea
look for the patch to tape drive
#boot alt (path number)
the follow the promts and wait.

there you go. Anf if I am missing something please let me know.

Richard

[someone_4]

Note:

This

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


should be this:

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



########

Extra notes on tape compression.

The amount of data that can be copied to a tape is highly dependent upon the data.
The best compression will be achieved for strings of repetitive data.

You will obtain the most-for-the-money by using the 'BEST' device files. Normally these are already linked to '/dev/rmt/?m'. You can verify that you are using the best density (compression) by comparing the minor numbers of the device files for "?m" with "c?t?d?BEST" and noting identical values. For example, 0x030000 for /dev/rmt/0m as well as for /dev/rmt/c3t0d0BEST would denote equivalent devices. You can also verify that compression is available by doing an 'lssf ', as for instance, 'lssf /dev/rmt/0m'.

The presence of 'sparse' files (common for databases) can consume considerable amounts of tape storage. You can be mislead when evaluating space requirements with 'ls' or 'bdf'. Whereas 'ls' shows the apparent file size (which for sparse files will be smaller than actual); 'du' will return the actual file size (in 512-byte blocks).


I did not write all of this but it is all info that I have gatered from others on the forum. Most of it is exact copy past from what the memebers said. So if the info looks familar it is probably yours. And thanks.


Richard

[Sanjay_6]

Hi John,

Try the ignite ux faq,

http://www.software.hp.com/products/IUX/iux_faq

And the ignite ux admin guide,

http://www.software.hp.com/products/IUX/docs/sysadm.html

Hope this helps.

regds

[John McDen]

How do I read the contents of the tape, backed up by ignite utility make_tape_recovery ?

[James R. Ferguson]

Hi John:

To read and/or extract the contents of the make_tape_recovery tape, do this the following:

# mt -t /dev/rmt/0mn fsf 1
# tar -xvf /dev/rmt/0m

This example assumes tape 0m and that your want to extract from the tape. Change the 'tar' options to '-tvf' to simply report the tape's contents.

Note the no-rewind option with the 'mt' command to skip over the LIF written on the tape by Ignite.

Regards!

...JRF...