>>>>> On Wed, 21 Jul 2010 10:36:41 +0100, Mister IT Guru said:
> 
> Please excuse the attached txt, but putting it on pastebin doesn't last 
> forever
> 
> In this setup, if I update the file set, the backup begins again as a 
> FULL backup. This why would this be the case?
> 
> Ran TESTBASE, to create the basejob - no errors
> Ran TESTJOB, to see if anything else will be backed up - it ran very 
> fast, as hardly anything had changed
> I edited the fileset to add in another directory, and it ran the whole 
> thing as a full backup instead of an incremental, telling me that no 
> suitable prior/previous backup had be taken, which meant taking down 
> files that are in the basejob.
> 
> This is very undesirable, because a lot of my remote machines have over 
> 500G of data, and I dread to think that if the file set is edited, that 
> they will all come down the wire as a full

You can avoid this with the Ignore FileSet Changes = yes option in the
fileset.

BUT BEWARE: it will not back up files from the added directory that are older
than the last backup (that is the meaning of an incremental backup).

You can probably avoid this by using the Accurate Job/Fileset options, but I
don't know if you can add that for an existing Full backup.

__Martin

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users