[Bacula-users] question on re-running of failed levels

Before I submit this as a possible bug, I just wanted to see if perhaps 
it is the expected behavior for Bacula.

We have a few long running jobs that take > 24 hours to do a Full 
backup.  Because of this, we have the following set:

Allow Duplicate Jobs = no
Cancel Lower Level Duplicates = yes
Cancel Queued Duplicates = yes

In addition, we also have Rerun Failed Levels set to 'yes' since 
sometimes are computers are not accessible when a Differential or Full runs.

So, what I have seen happen recently is the following scenario:

April 16th 5am - Full runs for Job X
April 17th 5am - Job X runs again and is canceled
April 17th 3pm - Original job X finishes successfully
April 18th 5am - Job X runs again and does a Full again

The April 18th job should only run an Incremental but it appears that 
because we have Allow Duplicate Jobs set to 'yes', it sees the April 
17th 5am failure and decides that it needs to rerun the Full even though 
the April 16th 5am job did successfully finish after the April 17th 5am 
failure/cancellation.

Given these settings, should one expect it to see that successful job 
and not rerun the Full?  Has anyone else seen this behavior?

FYI, we are running Bacula 5.2.6 on the director/storage side and 5.0.3 
on this particular client.

thanks,


--tom


------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users