WARNING During fbackup

[Vivek Shrivastava_1]

Hi,

I ecived some warnng during the fbackup. please find below the output during fbackup:

#/usr/sbin/fbackup -g /tmp/graph -f /dev/rmt/0m
fbackup(1417): cannot open the dates file /var/adm/fbackupfiles/dates for readig
fbackup(1004): session begins on Fri Jun 18 10:19:34 2004
fbackup(3205): WARNING: unable to read a volume header
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(3055): total file blocks read for backup: 9525933
fbackup(3056): total blocks written to output file /dev/rmt/0m: 9639333
fbackup(1030): warnings encountered during backup
#

Please suggest, what should i do? is backup okay?

thanks

[Sridhar Bhaskarla · Accepted solution]

Hi,

The word "WARNING" is little inappropriate for this message. fbackup has the ability to read the tape and see if it was used before with fbackup. If you continuously use that tape with fbackup, it will tell how many times it used before unless you overwrite the header with mediainit or by some other backuptools.

In your case, looks like the tape is either fresh or was not used for fbackup before so fbackup gave you the information that it couldn't read the header.

-Sri

[Vivek Shrivastava_1]

Thanks.

[Sam McKnight]

Another word about warnings in fbackup. When fbackup starts, it makes a list of files on the system. Then, it attempts to back up each file in the list. During the backup, some of the temporary files in the list that had been generated by the operating system may have been deleted already by the operating system. fbackup then will give a warning that the file was not found, and the file's name will be included. Such files usually are easy to identify. I often have several warnings of this type when I do the regularly scheduled fbackup at 2:00 a.m.