fbackup warning

[Mihails Nikitins]

I got the following warning during fbackup.

fbackup(1004): session begins on Fri Dec 22 14:17:18 2000
fbackup(3309): WARNING: unable to read a volume header
fbackup(3024): writing volume 1 to the output file 1.1.1.1:/dev/rmt/0m
fbackup(1030): warnings encountered during backup: 4

This case has been discussed at

http://my1.itrc.hp.com/cm/QuestionAnswer/1,1150,0xf8a783667c40d4118feb0090279cd0f9,00.html

Q.

I did not get any information about the file(s) causing the error. I run fbackup in non-verbose mode creating index file.

fbackup -0i / -I indices/$DATE.index.log -f 10.10.2.201:/dev/rmt/0m

What diagnostic messages I should search?

Thanks in advance! Merry X-mas!

[Victor BERRIDGE]

try to see with fuser or lsof who is on the directory or file system you are trying to backup.
Good luck
Merry christmas

Victor

[James R. Ferguson]

Hi:

If you run your fbackup with the (v)erbose option (-v) and redirect the output to a log file, you will be able to search for warnings and errors. Thus, something like:

# fbackup... > /tmp/fbackup.log 2>&1

The most common reasons for an exit code of <4> are the lack of a volume header, as for instance with a new tape; or an attempt to copy a file that is actively changing.

You can verify an fbackup tape by doing a "no=recovery" 'frecover', as:

# frecover -N -r -v -f /dev/rmt/0m > /tmp/frecover.log 2&>1

The reason for doing the 'frecover' lies in the fact that if the file's modification timestamp has changed while the file was being written to tape, fbackup writes a "BAD" status flag to the file's trailer, and re-reads the file, writing the file to tape again. This process will be repeated times as specified in the fbackup configuration file. The default is five times. An 'frecover' of the tape will report these events.

Using the -v option during 'fbackup', and parsing the output log for errors and warnings allows the quickest determination of success and comfort for you. This is my standard choice.

...JRF...

[Darrel Louis]

Two things to check:
# Check the .rhosts files
# Check Network traffic.

fbackup -f : /dev/rmt/0m -v -i / # fbackup -i /
-f host_name:/dev_name_of_backup_device


man fbackup:
There is slightly different behavior if remote devices are used. A device on the remote machine can be specified in the form machine:device.
fbackup creates a server process from /usr/sbin/rmt on the remote
machine to access the tape device. If /usr/sbin/rmt does not exist on the remote system, fbackup creates a server process from /etc/rmt on the remote machine to access the tape device. Only half-inch 9-track magnetic tapes or DDS-format tapes can be remote devices. The fast search marks capability is not used
when remote DDS-format devices are used

[CHRIS_ANORUO · Accepted solution]

Regarding error fbackup messages " fbackup warnings encountered during backup: 4 "
"fbackup exit code 4" it's not error level but it's just only warning because your system is not upto date with the latest patches relating to your system hardware.
Use this link to check out the write up:
http://europe-support.external.hp.com/cki/bin/doc.pl/sid=879e601c00b4520b3e/screen=ckiDisplayDocument?docId=200000047385470

Or Document Id #: KBRC00000427

Cheers and Happy New Year In Advance!