No, because the end time of Full job #1 occurred after the end time of 
the failed job #2.  Bacula doesn't see any failed jobs occurring after 
the end time of successful job #1 which is all it cares about - at least 
in our patched version.


--tom

> Wouldn't this changed behavior run into the problem that cancelled
> duplicates are still seen as failed jobs and therefore jobs would be
> upgraded still?
>
> Eg:
>
>  1. Full starts
>  2. Incr is queued, upgraded to Full and cancelled.
>  3. Full ends
>  4. Incr is queued, checks that Full job no. 1 finished OK, but then
>     checks that Incr->Full job no. 2 failed - thus it's still upgraded
>     to Full and started.
>
> --
> Silver


------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users