On Tuesday 02 June 2009 22:15:47 Martin Simmons wrote:
> >>>>> On Tue, 2 Jun 2009 10:54:24 +0300, Silver Salonen said:
> > 
> > Hello.
> > 
> > Currently I see this behavior in Bacula 3.0.0 (on FreeBSD):
> > 
> > I backup a directory (having 6 files), then remove the original directory 
and 
> > restore it from backup. When I run an incremental backup of the same 
directory 
> > then, all the files are getting backed up again, although they should be 
> > exactly the same as they were before removing/restoring. Is there any 
> > parameter of files that is not restored and that causes them to be backed 
up 
> > again?
> > 
> > Is this behavior inevitable with Bacula?
> 
> Unfortunately, restoring a file will set its ctime to the current time and
> there is not much you can do about that.
> 
> By default, Bacula uses the ctime and mtime to detect changes for 
incremental
> backups.  You could set the mtimeonly=yes fileset option, but that would 
cause
> you to lose incremental backups of files where the permissions have been
> changed or someone has manipulated the mtime to be in the past.

Ah, thanks a lot! That's it.. I think relying on mtime only isn't so bad on 
these few cases.. and the option could be then removed after the next full 
backup, if there will be one :)

-- 
Silver

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users