[Bacula-users] cancelled duplicate job shows up as failed

Hello.

I'm using directive "Allow Higher Duplicates = no" in 5.0, but I find its 
behaviour a bit false in case "Rerun Failed Levels = yes" is set - cancelled 
duplicate job makes the same level to be ran again. The problematic in this 
behaviour is this use-case:
1) a full job is ran
2) another full job is ran - it's cancelled as duplicate
3) the 1st full job finishes successfully
4) if you run incremental now, it will be upgraded to full, because of the 
cancelled duplicate job

The problem is reported in http://bugs.bacula.org/view.php?id=1507, but as 
Kern explains there, it's not so trivial fixing this.

Maybe the community has any good ideas for this?

PS. Using "Max Full Interval" with "Rerun Failed Levels = no" could help 
somewhat, but I guess it doesn't fix the same loop-hole for level 
differential, ie. it could still mess up a bit of GFS rotation.

-- 
Silver

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users