[Bacula-users] Bad interaction between cancel duplicates and rerun faile

So I've got a full backup job that takes more than a day to complete. To keep a second full backup from getting started while the first one is still completing I've set the following in the Job definitions:
Allow Duplicate Jobs = no
Cancel Queued Duplicates = yes

However to handle network connection issues or clients being missing when their scheduled backup times comes around I have this setting in the Job definitions as well:
Rerun Failed Levels = yes

It seems that the duplicate job handling marks the level as failed, so that when the first backup finishes, the next backup that wants to run should be an incremental, but gets upgraded to a full because of the duplicate jobs that were canceled.

Anyone know a way around this?

--
Jon Schewe | http://mtu.net/~jpschewe

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bad interaction between cancel duplicates and rerun failed jobs