make_tape_recovery warning during backup ???

[guru4hp]

Hi Guys,
I have one questing regarding backup of system with make_tape_recovery. Well I have make a script who is executed one @ week with cron job, and I have noticed that I have some warnings in log file...

Here are that log ...

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Archive created and rewind the tape to beginning of tape.

* Cleaning up old configuration file directories
* Creating local directories for configuration files and archive.

======= 01/15/08 22:00:01 MET Started /opt/ignite/bin/make_tape_recovery.
(Tue Jan 15 22:00:01 MET 2008)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/net_recovery (opt) $Revision: 10.834 $ $Date: 2006/06/14
13:47:40 $

* Testing for necessary pax patch.
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c0t6d0 /dev/dsk/c0t5d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /tmp 2
/dev/vg00/lvol5 /home 2
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
/dev/vg00/lvolswap2
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2008-01-15,22:00/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2008-01-15,22:00/archive_cfg -g
/var/opt/ignite/recovery/2008-01-15,22:00/flist -n 2008-01-15,22:00 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
* Writing boot LIF to tape
142396+0 records in
142396+0 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2008-01-15,22:00 -m t -w
/var/opt/ignite/recovery/2008-01-15,22:00/recovery.log -u -R -g
/var/opt/ignite/recovery/2008-01-15,22:00/flist -a 46221980

* Preparing to create a system archive.

* Archiving contents of DS31b via tar image to local device/dev/rmt/0mn.
pax: Ready for volume 2
pax: Type "go" when ready to proceed (or "quit" to abort):
pax: Unable to prompt user: /dev/tty is unavailable.
WARNING: The pax command returned a non-zero exit status (exit status 1).
* Creation of system archive complete.


======= 01/15/08 23:20:52 MET make_tape_recovery completed with warnings

I need to have a valid backup to process with resizing of /opt partition, and on this server in /opt is installed database (yes I know, but customer did it alone that).

From this warnings, I assume that he is maybe waiting for another tape, am I right ? (he did not have adequate space on tape to do backup)

Current LVM info is:
LVM Volumegroup and Filesystem Quick Overview

================================================================
Volumegroup Informations for vg00 (VGID 6d110c6245123470)
PESize=32 MaxPE=4384 MaxPV=16 CurPV=2 MaxDiskSize=140288 MB
----------------------------------------------------------------
Total capacity in Volumegroup vg00 : 279936 MB
Allocated capacity in Volumegroup vg00 : 180288 MB
Unallocated capac. in Volumegroup vg00 : 99648 MB
Filesystemcapacity in Volumegroup vg00 total : 81939 MB
Filesystemcapacity in Volumegroup vg00 used : 42495 MB
Filesystemcapacity in Volumegroup vg00 available : 39412 MB
================================================================

LVM Overview

Primary AlternateLog.Volume Size/PE Free/PE MinorNr Filesys LVSize Mirrors Mount Point Controller/Product/HW Path
c0t6d0 vg00/lvol1 4374 1557 000001 hfs 320 1 /stand SCSI/SCSI (ST3146707LC)-0/0/0/3/0.6.0
vg00/lvol2 000002 raw 4096 1 ***swap***
vg00/lvol3 000003 vxfs5 576 1 /
vg00/lvol4 000004 vxfs5 1024 1 /tmp
vg00/lvol5 000005 vxfs5 32 1 /home
vg00/lvol6 000006 vxfs5 40000 1 /opt
vg00/lvol7 000007 vxfs5 20000 1 /usr
vg00/lvol8 000008 vxfs5 20000 1 /var
vg00/lvolswap2 000009 raw 4096 1 ***swap***
c0t5d0 vg00/lvol1 4374 1557 000001 hfs 320 1 /stand SCSI/SCSI (ST3146707LC)-0/0/0/3/0.5.0
vg00/lvol2 000002 raw 4096 1 ***swap***
vg00/lvol3 000003 vxfs5 576 1 /
vg00/lvol4 000004 vxfs5 1024 1 /tmp
vg00/lvol5 000005 vxfs5 32 1 /home
vg00/lvol6 000006 vxfs5 40000 1 /opt
vg00/lvol7 000007 vxfs5 20000 1 /usr
vg00/lvol8 000008 vxfs5 20000 1 /var
vg00/lvolswap2 000009 raw 4096 1 ***swap***

Tnx for replays .. :) Cheers

[Tim Nelson]

What type of tape drive are you using ? Is it asking for tape 2 immediately ? if so you have a bad tape/drive.

Most HPUX Ignite archives are about 3-7GB depending on what extra you are including. Which would require at least DDS2or3 to get it on one tape.

Review what is included with the archive and maybe strip some non HPUX stuff off if there is any.

The smaller the footprint the more reliable the recovery.

[Torsten.]

Look at this:

pax: Ready for volume 2
pax: Type "go" when ready to proceed (or "quit" to abort):
pax: Unable to prompt user: /dev/tty is unavailable

Ignite is waiting for your "go" after you swapped the tape, but it was not able to ask you. Did you run the backup in backgroung or from script?

[guru4hp]

backup was done from script, who is runing once a time @ week.

after "backup", tape is rewind to the begining of tape.

Question: I need to overwrite old backup with new one on that tape, what I need to execute to get that ?

It is only one tape, I think DAT 72GB (C7438A
).

[Torsten.]

Question: I need to overwrite old backup with new one on that tape, what I need to execute to get that ?


Ignite was asking you for a **second** tape!

If you write to the same, you will destroy the boot header and part 1 of your backup by overwriting with part 2.

Be careful!

[guru4hp]

:) I know that he will overwrite tape. :)
But it is strange that backup did not fit to one tape....

Customer did work on same tape backup for some time, they have only rewind tape to begining.

My questing is if they did rewind tape, backup will start from what point of tape, from begining or from the end of last backup ??
If it starts from begining of tape, it should be room for complete backup, if it starts from the end of last backup, he will not have space to make backup, and he will ask for another tape.

[Torsten. · Accepted solution]

ignite will **always** write from the beginning of the tape.

[guru4hp]

TNX :)
I know what was a problem. They have used 24GB tapes, not 72GB ... and that is reason why make_tape_recovery asked for another tape during backup.

They will do another backup with large tapes.

Cheers

[Torsten.]

Sounds reasonable.

Tell them they should cycle the tapes.
One for each day - 7 for a week.

If they use only 1 tape, it is dangerous.

Consider murphy's law!

The day will come and you will need the tape and the tape will be bad ...

[guru4hp]

Heah :) murphy's law :)
Anything can happend :)

[Bill Hassell]

It is important to understand that if *any* backup program asks for another tape, you cannot use the same tape. If you do, the *entire* backup is worthless! The beginning of the backup was erased and the middle of the backup was written to the beginning of the tape. Anytime a second tape is requested, the backup is worthless unless an operator is watching and can put in a second tape.

[guru4hp]

Thanks to everyone for answers. Backup with make_tape_recovery went fine with no errors and warnings.
Some software, like EMC Networker can use same tape to put another backup on it, after the end of last data writen of last backup. That is why I have question regarding usage of tape with make_tape_recovery.

[guru4hp]

Problem solved :) Tnx to everyone for replays...