From: Lamp Zy <la...@gm...> - 2010-10-07 20:54:53
|
On 10/07/2010 01:34 PM, Phil Stracchino wrote: > On 10/07/10 13:40, Lamp Zy wrote: >> Hi, >> >> It will be great (at least for me :-) ) when Bacula looks for previous >> Full backup on a brand new client to also check if a Full backup is >> currently running. >> >> We do Incr. backups M-F at night and they use tapes from IncrTapes pool. >> Full backups use tapes from the FullTapes pool. When I add a new client >> sometimes I run the Full backup manually to avoid Bacula changing tapes >> in the middle of the night. >> >> The problem is that when my manually ran Full backup takes longer then I >> expected and overlaps with the regularly scheduled Incr backups. Then >> Bacula runs the Incr. backup for my new system and because it can't find >> a previous Full backup it changes it from Incr to Full. >> >> But, the Full backup is already running. It just hasn't finished yet. >> So, at the end, I end up with two Full backups for the same system. > > Peter, > This is a solved problem. The following two existing directives added > to your JobDefs or Job resource will take care of this for you: > > Allow Duplicate Jobs = no > Cancel Queued Duplicates = yes > Thanks a lot Phil. -- Peter |