On Dec 20, 2007 10:04 AM, Conny Brunnkvist <[EMAIL PROTECTED]> wrote: > Hi, I've had a problem haunt me a couple of times as I add clients: > > after a new client/job is added, when the first initial job is run, it > is naturally upgraded from Inc to Full. So far, so good. But the > problem is that for large jobs, that take more time than one Inc-cycle > to finish, the next Inc job gets immediately upgraded to Full (- > because there is no *completed* full job yet) as well, and placed in > the job queue waiting for MaxClientJobs. > > And when the initial job is finished, the "next" Full job(-s) in the > queue start, and so on and so on... > > Is there any way to avoid that, other than keeping an eye on the > bconsole, manually Cancelling the pending job stack? Or is it a known > bug, fixed in CVS? :o) > > //conny >
You need to play with your priority settings for each client/job, etc. Say for instance you have all regular scheduled Full's to run on Sunday's and Incrementals to run daily except Sunday. Set your incrementals to run with a priority of say 20 and your Full's to run with a priority of 30. No incrementals will run on Sunday when the actual Full's run so they won't interfere and during the week when you setup a new client, when it runs that first Full backup which is needed cause how can an incremental run without having existing full backup, it's priority will be set lower so the incrementals should queue up and complete first before the Full kicks in and takes over, taking a longer time to backup. -Drew ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
