topic Re: DAT tape problem in Operating System - HP-UX

DAT tape problem

ouazir — Sat, 11 Jul 2009 05:24:47 GMT

i want to identifier the problem that i got
when i attempt to test the contente of my DAT tape,
the command used for backup is
fbackup -fv /dev/rmt/0mb -i /dir

for test i am using the follwing

#frecover -f /dev/rmt/0mb -xNv
frecover(2105): did not find expected file marker
frecover(5409): unable to read volume header
frecover(5418): not an fbackup volume; unable to read volume header
frecover(2105): did not find expected file marker
frecover(5412): Do you wish to try to salvage this volume? (^[yY]/^[nN])
what is this message mean ?
thanks for evry one .

Re: DAT tape problem

SoorajCleris — Sat, 11 Jul 2009 05:47:25 GMT

Hi,

This message shows that this tape has nothing to do with fbackup. This may be a tape which used to take back up with other utility like tar or cpio .

Simply you will not be able to use the date with fbackup/frecover.

Regards,
Sooraj U

Re: DAT tape problem

SoorajCleris — Sat, 11 Jul 2009 06:17:06 GMT

Ok.. I didnt see that you have used the command to fbackup to take the backup..

May be this tape is a bad one so frecover is unable to read the index or may be DDS drive problem!!!

Try using tar/cpio and confirm that drive and tapes are OK.

Thanks,
Sooraj

Re: DAT tape problem

ouazir — Sat, 11 Jul 2009 06:59:49 GMT

thanks for your reply, i would like to tell you that DDS device (DAT 160) is new it have never be used, of cours i will confirm that the DDS have not a problem by this follwing test :
=> I will take a backup with cpio or tar command and with a new tape
I will send you the result when i will get it.

Re: DAT tape problem

Duncan Edmonstone — Sat, 11 Jul 2009 08:04:47 GMT

is this a typo:

fbackup -fv /dev/rmt/0mb -i /dir

cos for me, this will backup /dir to a file called "v" in the current directory (or actually might just produce an error)

I would have expected the fbackup to be:

fbackup -vf /dev/rmt/0mb -i /dir

Looking at the man page for fbackup - the -f has to be followed by the device you're backing up to.

HTH

Duncan

Re: DAT tape problem

ouazir — Sat, 11 Jul 2009 08:36:58 GMT

sory i am using
fbackup -v -f /dev/rmt/0mb -i /dir
and not -vf!

Re: DAT tape problem

Bill Hassell — Sun, 12 Jul 2009 01:57:34 GMT

> frecover(2105): did not find expected file marker
> frecover(5409): unable to read volume header
frecover(5418): not an fbackup volume; unable to read volume header
> frecover(2105): did not find expected file marker
> frecover(5412): Do you wish to try to salvage this volume? (^[yY]/^[nN])
> what is this message mean ?

It means that the tape you are reading was never recorded by fbackup. This is not a tape drive problem. The data on the tape is not from fbackup.

Re: DAT tape problem

ouazir — Sun, 12 Jul 2009 05:32:51 GMT

>It means that the tape you are reading was never recorded by fbackup.
i am using fbackup only for copy the data form my locale storage to DDS tape,the script that i writing for take a backup is the follwing :
#!/bin/sh
log=/backapp/applproto/sauvegard.log
###Liberation de l'espace disque
###***********************************************
/usr/bin/find /backapp/applproto/ -mtime +4 -type d -exec /sbin/rm -rf {} \;
###***********************************************
##""""""""""""""""""""""""""""""""""""""""""
jour=`date '+%d.%m.%y'`
mkdir /backapp/applproto/$jour
##""""""""""""""""""""""""""""""""""""""""""
d=`date`
/sbin/tar cf - /applproto|/usr/contrib/bin/gzip|split -b 5000m - /backapp/applpr
oto/$jour/applproto.$jour.tar.gz
mt -t /dev/rmt/0mb rewind
fbackup -f /dev/rmt/0m -i /backapp/applproto/$jour
mt -f /dev/rmt/0mb rewind
mt -f /dev/rmt/0mb offl
what's wrong

Re: DAT tape problem

Bill Hassell — Sun, 12 Jul 2009 17:42:00 GMT

> what's wrong?

What were the error messages from fbackup? Your script does not save the output from fbackup into a log file. Add this to your fbackup command (see -v to add more details?:

fbackup -v -f /dev/rmt/0m -i /backapp/applproto/$jour >> /var/adm/fbackup.log 2>&1

Note that this log is cumulative -- it have the output from each fbackup session.

Now your script runs 2 rewind commands -- for fbackup, this is unnecessary as fbackup always rewinds the tape at the start and end. But you can leave the rewinds in place if you want. The offline command will eject the tape. That's where the problem may have occurred. Someone may have removed the tape and put something else in its place.

The only way tp verify that fbackup is not working is to run the commands manually. Save something small like /var/tmp or /var/adm, then immediately run frecover to read the header and the table of contents:

fbackup -vf /dev/rmt/0m -i /var/tmp
frecover -V - -f /dev/rmt/0m
frecover -I - -f /dev/rmt/0m

The first frecover will show the tape label or header, and the second shows the table of contents.