topic Re: fbackup error-codes in Operating System - HP-UX

fbackup error-codes

Danny Engelbarts — Wed, 13 Sep 2000 08:42:48 GMT

Hi there,

I'm creating a simple filter script for checking fbackup results and need a list of error-codes, such as tape full, write error etc.

Thanks!

Re: fbackup error-codes

James R. Ferguson — Wed, 13 Sep 2000 08:47:37 GMT

Danny:

From document #KBRC00000151.

"fbackup returns the folowing error values:

0 upon normal completion
1 if it is interrupted but allowed to save its state for possible restart
2 if any error conditions prevent the sessions from completing.
4 if any warning conditions are encountered.

If warnings occur, then the operator should verify the fbackup logs to justify the sanity of the backup taken.

The most common cause of an exit code of 4 is the use of a new tape. When fbackup begins on a new tape, it recognizes this and gives a warning as it generates the proper tape headers. In this case, the exit code 4 can generally be assumed to be a success."

...JRF...

Re: fbackup error-codes

James R. Ferguson — Wed, 13 Sep 2000 08:56:18 GMT

Danny:

And here's some more information; see document #KBRC00000427. For instance, error code 137 indicates a kill from the fbackup process and most probably means that the tape is full.

...JRF...

Re: fbackup error-codes

R.Suresh — Wed, 13 Sep 2000 08:59:21 GMT

Hi,

use Simply

#fbackup > fbackup.log

Thanks & Regards
R.Suresh
r_sures@yahoo.com

Re: fbackup error-codes

Danny Engelbarts — Wed, 13 Sep 2000 09:20:58 GMT

Thanks, but i may not have made myself perfectly clear, the purpose is to collect the fbackup results from some 20 machines at one central point.

The script i use is similar to the br_backup script of SAM i.e. it creates the backup and sends the output from fbackup to a specified e-mail address.

The filter i made scans this e-mail for the specific error codes like #3003 (tape full).

What i would like is a list of these codes.

Greetz Danny.

Re: fbackup error-codes

Stefan Farrelly — Wed, 13 Sep 2000 09:31:13 GMT

Dont know of a master list for fbackup but heres a few we commonly get;

fbackup(3013): WRITE ERROR while writing data record, at media record
(Media error or it also could mean tape is full)
fbackup(3038): output file /dev/rmt/1m is not a valid device file for backup (no tape)
fbackup(3032): could not open output file /dev/rmt/4m (no tape)
fbackup(3003): normal EOT (Tape is full)
fbackup(3040): output file /dev/rmt/1m encountered an I/O error (no tape)

Re: fbackup error-codes

Danny Engelbarts — Wed, 13 Sep 2000 09:39:24 GMT

Thanks to you all, i found a complete list of the codes, through the second document Stefan mentioned, by using;

dumpmsg /usr/lib/nls/C/fbackup.cat | more

Greetz Danny.