fbackup question

[Mel_12]

Hi All,

I always get this message about unable to read a volume header on my flog file after every fbackup session. Here is the messages prescisely:

Backup begin:
Tue Feb 10 23:30:00 EST 2004
Backup end:
Wed Feb 11 00:38:16 EST 2004
23:30:00 2004
fbackup(3205): unable to read a volume header
fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t1d0BEST

The backup log itself lists all the files and directories that were backed up. I even performed a small restore of one file and it was ok. Why do I keep getting the fbackup(3205) unable to read a volume header before it begins writing to the volume?

Thanks
Mel

[Robert-Jan Goossens]

Hi Mel,

These messages simply tell you that this is the first time this tape
has been written to by fbackup(1M). fbackup(1M) writes the volume header
on the tape the first time it writes to it.

Regards,
Robert-Jan

[Mel_12]

Robert,

I think you might be right with your findings. Our new tape drive required different tape than we fed our defunct drive.I guess I will verify this when we get to the point where we would re-use a tape that has already been written. We keep 4 sets of weekly full backup tapes.

Thanks
Mel

[Robert Kerr]

Often means the tape is new or previously used by a different backup utility.

[Michael Tully]

This is *the* standard message given by fbackup each and every time when it attempts to write to a tape that has not been used previously by fbackup, or has been written over by another backup tool. Once your cycle of tapes has started again, your message log will display that the tape has been used (1) time previously.