In response to Arno Lehmann <[EMAIL PROTECTED]>: > > [Problem] > > Here's the problem...as incremental backups expire and are purged, bacula > > will > > often promote the next incremental to a "full" backup, since it correctly > > determines that there are no full backups for a particular client in the > > "Incremental" pool. Writing a full backup can be disruptive to both the > > client > > and backup server, as some backups are over 2TB, with clients on a slow > > network. > > I want to avoid unscheduled full backups as a result of promoted > > incrementals, > > and I don't want to be doing full backups every 2 weeks to satisfy the > > retention > > period of the "Incremental" pool. > > > > Is there anyway to avoid this behavior? > > Keep the incremental backups for more than a month. > > You need an unbroken chain of incrementals, i.e. from the last full > backup to the current date no incremental backup can be pruned.
Not exactly true. Differentials can be used to "consolidate" incrementals. Assuming you make incrementals 6 days a week, and Sunday is for fulls and differentials, set retention on your incrementals to 6 days, differentials to 3 weeks. Then you'll always have enough data to perform an incremental without building a new full. That gives you the standard "decreasing granularity with increasing age" scheme that most people want. -- Bill Moran Collaborative Fusion Inc. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
