Hi.
Brice Figureau wrote:
Hi,
First: I'm (still) happily running 1.36.1, and the more I use Bacula, the better I find it.
Great. I'm sure Kern likes to read stuff like this. :-)
...Following the good advice to have 'Rerun Failed Levels = yes' in my Job definition along with a a 'Run Before Job' that check if the host is up and running, I encountered the following problem.
I had a FD that was shutdown for a long time, thus each of its jobs were failing as shown by this SQL request:
...I added the 'Run Before Job' on 3/31/2005, and the Error code, changed from E (error) to f (failed).
Two days ago, the backup was a Full backup, but the host was down. Yesterday the backup was an Incremental backup and this particular FD was up and running, I expected it to upgrade its backup to full, but no:
...After reading the code, I found that the problem was indeed the following:
Is it a design limitation of the Run Before Job or is it a bug ? I can file a bug report if necessary.
I'd do that. I guess it is a bug caused by a design limitation :-) but, even without reading the source, I suspect that it might be easily fixed and would make bacula behave the way it should.
Does anyone have a workaround (besides removing my 'Run Before Job') ? And finally how can I fix this and force an upgrade to Full for this FD ?
Simply start the job manually, either like 'run job=pierre' and other settings as needed, or through the dialog following a simple 'run' command.
Thanks for your answer,
Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
