FBACKUP Volume Counter reporting negative values

[Mel_12]

Hi,

The volume counter for our fbackup program is reporting -1 and I wonder what that means. Here is the ensuing log:

Backup begin:
Wed May 12 23:30:00 EDT 2004
Backup end:
Thu May 13 00:39:50 EDT 2004
23:30:00 2004
fbackup(3203): volume 1 has been used -1 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/c0t1d0BEST

Regards,
Mel

[Steven E. Protter]

I've seen that with new tapes and tapes where the label wasn't written.

Its not a problem. If the fbackup terminates normally it will set that data on the tape and it will be right next time.

SEP

[Mel_12]

Thanks SEP. I'll know for sure in the next cycle [4weeks]if the numbers increment positively.

Regards,
Mel

[Dani Seely]

Hey Mel,
We see this sort of message each time but haven't seen a '-1 time(s)' message. I have seen messages state '12 time(s)'. We don't make a habit of re-using tapes extensively, but sometimes we have no choice. Anyway, I think you're alright and the '-1' was due to a new tape being used. Can you confirm whether the tape you used was a new tape or was it a tape that has previously been used?

[Mel_12]

Hi Dani,

Not sure if this tape is brand new. It could have been a brand new tape which was attempted usage prior to my backup drive dieng. We subsequently acquired a brand new drive and this happens to be the first couple of weeks of usage. Again, I'll know for sure the next time around [4weeks]. Thanks for your input. On a side note, if your tape counter registers 12 and you seldom re-use tapes, I wonder why that is the case.

Cheers,
Mel

[Dani Seely]

Hey Mel,
Has it been for weeks yet? ;-}

Just checking in to see if there were any updates to this issue. I guess I need to clarify myself ... we don't make a habit of it, but sometimes the powers that be decline our funding requests for new tapes, so we have no choice.

Also, I have a suggestion for you ... since this is a new drive, have you tested a file restore yet? It sounds like you have a good tape rotation scheme, but with this new drive in place, you should do a file restore test BEFORE you NEED to do a restore. Better safe than sorry!

[Mel_12]

Hi Dani,

No, it's been only +- 10 days judging by my last post. Thank you for asking. I am now getting these messages which suggests to me that it may be that the fbackup routine is having a hard time reading the tape headers and maybe possibly assigning numbers randomly out of frustration.

Backup begin:
Fri May 14 23:30:00 EDT 2004
Backup end:
Sat May 15 00:39:04 EDT 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

I will notify the forum when the clock ticks 4 weeks or you could also remind me if I forget. Your suggestion to do a restore is noteworthy; although I performed a quick backup and restore on the day the drive was mounted using sam. I am going to do it once more with my fbackup native scripts.

Regards,
Mel

[Bill Hassell]

The message: unable to read a volume header does NOT mean fbackup is having problems. It indicates that fbackup could not find an fbackup label at the front of the tape. Put in a tar tape and that will be the message...fbackup is just indicating that whatever wrote on the tape previously, it wasn't fbackup. The error message is poorly written.