>>>>> On Thu, 10 Jul 2008 08:24:40 -0700 (PDT), Hemant Shah said:
> 
> --- On Thu, 7/10/08, Martin Simmons <martin AT lispworks DOT com> wrote:
> 
> > From: Martin Simmons <martin AT lispworks DOT com>
> > 
> > The bls output shows the ctime that was recorded on the
> > volume, which should
> > be the ctime from the filesystem when the file was backed
> > up.  By default, a
> > file will be included in an incr/diff if its either is
> > mtime or ctime are
> > newer than the last full backup of the job.
> > 
> > I suggest checking with
> > 
> > stat /mnt/online_docs/src/bind/bind-9.2.1.tar.gz
> 
> root@lidp11 ~]# stat /apex/online_docs/src/bind/bind-9.2.1.tar.gz
>  File: `/apex/online_docs/src/bind/bind-9.2.1.tar.gz'
>  Size: 5021044         Blocks: 9832       IO Block: 8192   regular file
> Device: 15h/21d Inode: 663370      Links: 1
> Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
> Access: 2008-07-06 22:09:42.847997000 -0500
> Modify: 2002-08-28 10:43:22.000000000 -0500
> Change: 2008-07-06 14:00:44.104163000 -0500
> 
> The ctime is the time of incremental backup and is also the time in bls
> listing for incremental backup.

OK, so that explains why it gets backed up.

Are you using the keepatime option in the fileset?

__Martin

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users