> "Graham Sparks" <gmjs AT hotmail.co DOT uk> kirjoitti viestiss?
> news:SNT109-W401DEA1ED7C90A15A91F1B814F0 AT phx DOT gbl...
> > Hello,
> >
> > I'm a fairly new Bacula user (all daemons running on same
> machine-Ubuntu804 and a FD on Windows XP Home client). I've set up a Full
> backup of a drive on the client that ran on Saturday and have an incremental
> backup of the same fileset done on Monday. Having noticed that the file size
> was large for the two day's worth of data, I excluded the Windows swap file
> from the fileset.
> >
> > Today's incremental however wouldn't run. Bacula insisted on running a
> new full backup.
> >
>
> What did you do here? Did you let it run, or did you cancel it? I assume you
> cancelled it... see below.
>
> > I'm aware that this is because I have changed the fileset, but read about
> an option (Ignore FileSet Changes = yes) that is supposed to ignore that fact
> and continue to perform incrementals. After adding this and reloading the
> configuration, Bacula still won't perform an incremental backup.
> >
> > Is there a reason why it still refuses to run an incremental backup (I
> deleted the JobID for the failed promoted Full backup with the delete JobIB
> command)?
> >
> > Have a try if restarting the director helps.
> >
> > Reload should be enough, but recently I noticed that 3.0.3 didn't
> recognize fileset option changes reliably after reload.
> >
> > --
> > TiN
>
> I performed as restart (and a separate start/stop) but it's the same.
>
> I've tested it with a smaller job and it seems to be the case that the
> IgnoreFileSetChanges option only takes effect if present in the FileSet
> definition when the original Full backup runs (adding it in afterwards
> doesn't make a difference).
>
> Many thanks for the reply though!
>
>
> One thing that still came into my mind: did you cancel the forced-full backup
> that had started after changing the fileset, when you didn't want it to run
> as full backup again? If so, the reason probably is that the previous full
> backup didn't complete succesfully (because it was canceled). Then the
> behaviour isn't only because of the fileset change anymore, but because of
> the non-succesful previous full backup, which requires the next one to be
> forced to be a full one, whether there were fileset changes or not. For more
> information about this, see the explanation under the "Level" directive of
> the "Job Resource" in the documentation.
>
> Btw, when asking this kind of questions in the future, pls. tell which
> version of Bacula you have. I guess you have got it from some Ubuntu repo,
> and maybe it wasn't the latest released Bacula. Then the Real Gurus (not me)
> here might immediatedly be able to say "oh yes, that was a bug that was fixed
> in x.y"
>
Here's my understanding of why it didn't work as you expect... when you add
the Ignore Fileset Changes parameter you're end result is to change the
fileset. The way bacula detects fileset changes is by simply hashing the
fileset. Perhaps it would be nice if bacula excluded the Ignore Fileset
changes part, but I've learned to work around this by simply adding that
value in on every fileset or add it in when ready to do a full backup anyway.
Bob
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
