On Friday 05 June 2009 16:36:16 Silver Salonen wrote:
> On Thursday 04 June 2009 10:53:03 Christian Gaul wrote:
> > Silver Salonen schrieb:
> > > On Thursday 04 June 2009 10:34:36 Christian Gaul wrote:
> > >
> > >> Silver Salonen schrieb:
> > >>
> > >>> Hi.
> > >>>
> > >>> I'm trying to run incremental job of a restored fileset (having
> > >>> mtimeonly=yes). When I check its estimate, it shows correctly only new
> > >>>
> > > files
> > >
> > >>> that have been created/modified since restoration. But when I run the
> > >>>
> > > actual
> > >
> > >>> job, all the files are included in backup.
> > >>>
> > >>> The server is 3.0.0 on FreeBSD, client is 3.0.1 on Windows XP.
> > >>>
> > >>> May it be because all the folders' (but not files') mtime is the date
of
> > >>> restoration? And I wonder what is the latter caused by?
> > >>>
> > >>>
> > >>>
> > >> Since you modified the fileset to add mtimeonly=yes, did you also add
> > >> Ignore FileSet Changes=yes?
> > >>
> > >> If not, your next backup will default to a Full because the fileset
> > >> doesnt match to the one your last Full was made with.
> > >>
> > >
> > > Yes, I also have "Ignore FileSet Changes=yes", sorry I didn't mention
it.
> And
> > > if I didn't have it, estimate would show full too, wouldn't it?
> > >
> > >
> > I dont know if estimate honors that or just takes what you give it. I
> > personally only use estimate when making new filesets (to see if my
> > excludes work correctly). And since using estimate with LVM Snapshots
> > doesnt work anyways because they are not mounted for an estimate job,
> > most of my filesets would show 0 files anyways. Sorry i cant help with
that.
>
> I suppose estimate does honor the option ("Ignore FileSet Changes=yes"),
> because the problem is not in estimate job's files, but rather in actual
job's
> files - the actual job just wants to back up all the files, but it should
not.
>
> It seems that actual job (or the client of the job) doesn't honor the
> mtimeonly=yes - it worked OK with my FreeBSD-client when I tested the
similar
> situation.
>
> --
> Silver
I submitted a bug report for that:
http://bugs.bacula.org:80/view.php?id=1318
--
Silver
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
