SAM fbackup

[E. Wong]

I use SAM fbackup option for backing up my HP9000 server running 10.20.

I started to notice in the log, the following message:

br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Thu Mar 14 03:00:40 2002
fbackup(3203): volume 1 has been used 27 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(9999): Interrupted system call
fbackup(9999): Interrupted system call
fbackup(2004): reader 0: 1st read error, firstread=32768, n=0
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=65536, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 0: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call
fbackup(2004): reader 1: 1st read error, firstread=32768, n=0
fbackup(9999): Interrupted system call

Is this an indication that I need to modify some Kernel values?

Any help will be appreciated

[Helen French]

Hi,

There can be a hardware error. Check this out:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=8754e5490fe767ab7d/screen=ckiDisplayDocument?docId=200000041137806

HTH,
Shiju

[Frank Slootweg]

As far as I know, this happens if a file (to be backed up) can not be (physically) read. I thought it always mentioned the filename or filenumber (see fbackup's index).

Are you sure it did not report a filename? Any information in the mentioned /var/sam/log/br_log file?