On 07/11/2011 10:29 AM, hymie! wrote: > However, I might suggest that, since Incremental/Differential backups > depend on having a Full backup already completed, you have your > priorities backwards. The Full backups, imho, should be given the higher > priority than the incrementals.
Maybe I didn't word my email correctly. Let me try to explain again. Currently all my machines (about 50 of them) are set to fire off their Full backups the first of the month. I also have bacula configured to not allow duplicate jobs. If my Full backups take a week to run (in some cases I have machines that take days to run a Full backup), the incrementals for all the jobs that are sitting in the queue will get cancelled due to not allowing duplicate jobs. Because of this, there is a gap between when the Full backup was scheuled and when it actually finishes. In other words.. if I have a job sitting in the queue for a few days because other jobs are running, I still want incremetals of that machine to run while the Full is still waiting to get done. Does that make sense? ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
