Bacula-users

Re: [Bacula-users] Bacula accurate issues

2016-08-25 12:09:50
Subject: Re: [Bacula-users] Bacula accurate issues
From: Marvin Müller <rsdumm AT gmail DOT com>
To: bacula-users AT lists.sourceforge DOT net
Date: Thu, 25 Aug 2016 18:08:34 +0200
And an additional update:

The issue seems to be resolved. I upgraded director and fd to the very latest version and run a new full backup. Now, incremental backups with accurate options do not include all files anymore.
I'm not totally sure if the update to the latest version was really necessary, but maybe my steps help somebody with a similar problem.

Thanks for all input received!

Marvin

On Wed, Aug 24, 2016 at 9:34 PM, Marvin Müller <rsdumm AT gmail DOT com> wrote:
Some additional input:
- Disabling accurate mode results in a "resonable" list of files from the estimate command.
- Changing accurate options does not change the files displayed with estimate. Even specifing a size-only check (accurate = s) results in the estimate list containing all files.
- This issue seems present will all of my Ubuntu bacula clients.

Thanks
Marvin

On Wed, Aug 24, 2016 at 7:55 PM, Marvin Müller <rsdumm AT gmail DOT com> wrote:
Hi list,

I'm using Bacula 7.0.5 on Ubuntu 16.04. I configured daily incremental backups in accurate mode, with accurate options "mcs". Since upgrading to Ubuntu 16.04 and Bacula 7.0.5 I experience really huge incremental backups.

Estimate gives me 1,943,557 files that will be backed up on next incremental backup. One example from estimate output:

-rw-r--r--   1 root     root            1371 2015-12-13 12:06:43  /etc/rsyslog.conf

While stat /etc/rsyslog.conf results in:

  File: '/etc/rsyslog.conf'
  Size: 1371           Blocks: 8          IO Blocks: 4096   regular file
Device: 801h/2049d       Inode: 13909238    Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access    : 2016-08-07 09:34:50.309697861 +0200
Modify: 2015-09-01 08:56:48.000000000 +0200
Change   : 2015-12-13 12:06:43.977985007 +0100
 Birth    : -

I interpret option "accurate = mcs" as: "A file will be backed up, if mtime, ctime or size has changed since the last backup." As one can see from the above stat output none of the three has changed. I therefore do not understand why this file (and several thousand other files) get backed up every night.

My FileSet config looks like this:

FileSet {
        Name = "FileSet_Alles_Linux"
        Ignore FileSet Changes = yes
        Include {
                Options {
                        signature = MD5
                        accurate = mcs
                        _onefs_ = no
                        compression = gzip
                        noatime = yes
                        xattrsupport = yes
                }
 
                File = /
        }
 
        Exclude {
                File = /sys
                File = /var/lib/bacula
                File = /proc
                File = /dev
                File = /tmp
                File = /.journal
                File = /.fsck
                File = /srv/bacula
                File = /var/spool/squid
        }
}

The job is running as an incremental job and is not upgraded during runtime.

Any help is highly appreciated. If you need any further information, let me know!

Thanks
Marvin


------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>