Alan Brown wrote:
> On Mon, 28 Jul 2008, Frank Sweetser wrote:
> 
>> It's possible to almost get into that situation, but Bacula will detect and
>> prevent it.  Whenever an incremental or differential job runs, it checks the
>> catalogue for a matching full backup.  If it doesn't find a matching full
>> backup, the current job is upgraded to a full backup.
> 
> This behaviour is flawed for large backups. If repeat failed levels is
> enabled, then if an incremental is scheduled and the full is still running
> the increental will turn into a full - same with the next incremental.
> 
> This easily gets into a cycle of endless full backups.

I have hit the same problem in my environment. Allthough not a perfect 
solution I set the concurrency of the client fd to 1 and set the Max 
Wait Time to 23 hours for the jobs. This makes sure I dont hit any 
endless loops of full backups.

-- 
Jesper

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users