On Thu, Jun 30, 2005 at 11:57:04AM +1000, Jesus Salvo Jr. wrote:
> I have a job that I just where I only ever wanted incremental level done.
>
> Reason is that, the fileset that is associated with the job only keeps the
> last N days of file to disk. That is, there is a cron job that deletes the
> old files in the fileset and puts new files in.
>
> Now of course, when bacula runs the job for the first time, it will first
> make
> a full backup ... but will then only make incremental backups for that job.
>
> Question, is there a side-effect with this kind of job with bacula ?
> Will the catalog grow bigger and bigger because it tries to keep the last
> known full backup for the job, etc ... ?
I'd probably not try to use only incremental backups. Recently a tape
broke that contained the full backup. And without a full backup... well,
you can imagine. :)
My suggestion would be:
Include {
File = "|find /backup/this/directory -mtime -7"
}
Untested though... but I would assume it creates a list of files that
have been altered in the last seven days and make a backup of them. Of
course this would be a full backup all the time.
Cheers
Christoph
--
~
~
~
".signature" [Modified] 3 lines --100%-- 3,41 All
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
