Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Problems

grace white
Advisor

Backup Problems

Hi

Have had several issue's with my backups of late and have checked the permissions on /var/adm/fbackupfiles and recreate my graph file but i still get the following error's.


Daily backup started
Fri Sep 5 01:00:42 BST 2003
===========================================

fbackup(1421): no history is available for graph file /var/backup/graph_daily (below level 0)
fbackup(1004): session begins on Fri Sep 5 01:00:42 2003
fbackup(3205): WARNING: unable to read a volume header
fbackup(3024): writing volume 1 to the output file /dev/rmt/0mb
fbackup(1030): warnings encountered during backup
Outcome stored in log file /var/backup/backup_daily.log

======BACKUP FAILED - error code 4==========

Daily backup completed


can any one advise me how to cure this i have even tried new tapes.

Thanks
Grace
UNIX/ORACLE DBA
4 REPLIES
Leif Halvarsson_2
Honored Contributor

Re: Backup Problems

Hi,
Check this thread:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x128f38dfa974d711abdc0090277a778c,00.html

It seems not be an error. If it is a new media there is no header on the media before it have been used the first time.
Thierry Poels_1
Honored Contributor

Re: Backup Problems

Hi,

1421 no history available....
--> there never is history BELOW level 0

3205 Warning: unable to read a volume header
--> new tapes cannot have a previous fbackup volume header

1030 warnings encountered...
---> yep: "unable to read volume header" (and maybe some "file in use" errors)

error code 4
---> backup (probably) OK, but had warnings

best regards,
Thierry.
All unix flavours are exactly the same . . . . . . . . . . for end users anyway.
Chris Wilshaw
Honored Contributor

Re: Backup Problems

An exit code of 4 indicates that a WARNING message has been generated. Normally, these are not an indication of a critical failure with the backups (they relate to the volume header error that you've seen on new tapes, and files that were not backed up because they were in use or removed while the backup was running).

You just need to change your backup script so that if an exit code of 4 is received, the script ends with a message like

"BACKUP COMPLETED WITH WARNINGS"

rather than

"BACKUP FAILED"

eg:

fbackup
STATUS=$?

case $? in

0)
echo "BACKUP COMPLETED OK"
;;
4)
echo "BACKUP COMPLETED WITH WARNINGS"
;;
*)
echo "BACKUP FAILED - error code $STATUS"
;;

esac
Chris Wilshaw
Honored Contributor

Re: Backup Problems

Oops.

My last post should read

case $STATUS in