> I have not made any changes to the Fileset. I have not purged any > volume containing the last full backup of this client. In fact I was > able to do a small file restore from the last Full backup > successfully that tells me the last full backup is good. > > In my client-dir.conf file I have the following entry. I am not sure > if this should matter? > > rerun failed levels = yes
Yes, that could be the difference depending on your other settings. How often do you schedule the running of your jobs and how long does the FULL take to run? See the following bug report: http://bugs.bacula.org/view.php?id=1882 In the following example scenario, you can get the incorrect behavior that you describe. From my bug report: Given these options Allow Duplicate Jobs = no Cancel Lower Level Duplicates = yes Cancel Queued Duplicates = yes Rerun failed levels = yes And this job workflow: April 16th 5am - Full runs for Job X April 17th 5am - Job X runs again and is canceled as expected April 17th 3pm - Original job X finishes successfully April 18th 5am - Job X runs again and a Full is run again I was able to track down the issue in the code that is causing this but I did not have time to come up with a decent fix for testing. At the time, I decided not to use the rerun failed levels option. If I ever get a chance at some point, I may take a look at this again and try and submit a patch for Kern to look at. --tom ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
