Fbackup warning

[Chris Watson]

Hi Everyone,

I use fbackup configured through sam for automated backups from 10.20 to DDS3.

I used to get an email that listed which files had a warning on them, but for sometime now I just get a short email stating the following;

"Full backup completed with warnings on cxxxxxxx : Fri May 11 03:33:01 BST 2001 .
For more information see the logfiles /var/sam/log/br_index.full
and /var/sam/log/br_log."

Neither of the files above tell me which files caused the warning, and as I say, they used to be listed in the email..

I read in the forums the following message;

"From :Mark Vollmers May 04, 2001 18:01 PM GMT [ unassigned ]

Ron-

Do you run the fbackup command from the prompt or do you have SAM set up an automated backup? We run ours through SAM and root gets mail listing all the errors (like x file was open and not backed up or that it was tested three times before successful). This might help show if there is an actual error (file not backing up) vs. just a warning.

Mark "

I was wondering if anybody give me some input on how to get back to the position of knowing which files caused the warnings? I know I can get this running from the command line, but this is very inconvenient. By the way, I only have a problem with open file every three or four days, this doesn't happen all the time!

Regards

Chris

[Thierry Poels_1]

hi,
a logfile might be in /var/tmp or in root's mailbox. Don't know for sure; personnaly I don't like the SAM backup. I like to have things in control :) SAM doesn't keep logfiles for each tape, etc. so I use my own scripts which generate and keep more logs.

The warning can be caused by :
-new tape (fbackup could not find a fbackup header)
-file in use at first try/tries

probably no problem, but you should check the details anyway

good luck,
Thierry.

[Mark Vollmers]

Chris-

I know what you mean about the email having warnings. Normally, when the backup is completed, I have gotten email saying that the backup was successful, and that file xxxx was active during attemp 1, trying again, etc. It also gives warnings for no headers, etc. The line that you gave is the first few lines, but the warning info should be below it. I don't know why they are not showing up, but I agree with Thierry that they are probably just the volume header or active files. If it was serious, I think that it would abort backup.

If it is possible with your system setup, try to run an interactive backup through sam. pick all the same folders and run it. A window should pop up that will show the files. It should list header warnings in the beginning, so you could see if that it the problem. To see the file that was not backed up, take the full log file (br_index.full) from a sucessful backup and compare it to a backup with warnings to see the differences. If a file is not backup up, I think it will be missing in the log and should show up.

Mark

[Chris Watson]

Mark,

Thanks for your response. I am confident that all the warnings relate to files in use, but it would be nice if the system told me, when using the automated backup, which files were in use.

I suspect that a bundle patch applied at some point has revised the br_backup script, and removed this feature, which gave the list of filenames that had a warning on the end of the email.

The script that does the backup for sam is called br_backup, but it is long a bit long and arduous to figure at what point this info has been dropped off in the script.

If I do an interactive backup, I do indeed see the files that had warnings, intermingled with the ones that didn't. But, I of course want to see this in the email I get when the backup is finished.

Would you be able to post the version of br_backup that is on your system, and I will diff it with mine.

Cheers

Chris

[Mark Vollmers]

Chris-

Not a problem at all. I have attached the file. I just quick skimmed it, and there is a spot that says "if you need to email results to user..." this might be an area to look at. There are a couple other mail commands, but I don't know exactly what is doing what. I added two lines at the end of the script to auto-eject the tape when finished with backup, just so you know. Other than that, this should be the file that was pulled off the cd during installation. Hope it helps. Good luck!

Mark

[Chris Watson]

Mark,

I can't see your attachment, but further rummaging in HPRC has revealed a patch issued on 7th May 2001 that purports to fix the problem.

"Document Id : PHCO_22268

JAGad09989) Backup messages from fbackup are not being mailed to the user."

Thatnks to Mark and Thierry for your assistance. I will now try this patch.

Have a nice weekend.

Chris

[Mark Vollmers]

Chris-

Sorry about that. Hopefully the patch will help, but in case you need it.

Mark

[Chris Watson]

ACtually, the patch I refered to has not solved the problem, so I have now logged a call with HPRC.

Chris