Steve Thompson wrote:
> All versions since 1.38, at least up to 2.2.8.
> 
> I have observed that if the director is not running at the time that a 
> full backup is scheduled, then the next backup to be performed when the 
> director next schedules the job is not a full but an incremental (that is, 
> the missing full is not detected). If the backup retention is less than 
> twice the interval between fulls, this eventually leads to the database 
> containing only incrementals and no fulls. Is this the as-designed 
> behavior? It certainly doesn't seem correct.

You're almost right.

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.

-- 
Frank Sweetser fs at wpi.edu  |  For every problem, there is a solution that
WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
     GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

-------------------------------------------------------------------------
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