On Sunday 2021-05-23 11:53:25 Joseph Zatarski wrote:
> In response to Bill, Phil, and Josip, I have checked the logs to be
> sure and the job is not being upgraded to full. I can't say for
> certain that the files haven't been touched by anything, but I'll be
> checking some attributes and doing s
On 5/22/21 10:57 PM, bacula-users-requ...@lists.sourceforge.net wrote:
Message: 7
Date: Sat, 22 May 2021 21:14:20 +
From: Bill Arlofski
To:bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] noticing an occasional incremental backup
act like full
Message-ID:<92e818f8-173d-8
On Sunday 2021-05-23 14:31:51 Bill Arlofski via Bacula-users wrote:
> On Sunday, May 23, 2021 8:25 AM, Bill Arlofski wrote:
> > Check this out:
> > 8<
> > 23-May 08:12 speedy-dir JobId 6: The FileSet "Full Set" was modified
> > on 2021-05-23 08:12:32, this is after the last successful backu
On Sunday 2021-05-23 14:25:37 Bill Arlofski via Bacula-users wrote:
> Right, good point! And when a job (typically set to Level = Incremental)
> is first run, this will always happen too. :)
>
>
> Oh! And I just remembered that I had made an internal Bacula Enterprise
> feature request some time
On Sunday, May 23, 2021 8:25 AM, Bill Arlofski wrote:
>
> Check this out:
> 8<
> 23-May 08:12 speedy-dir JobId 6: The FileSet "Full Set" was modified on
> 2021-05-23 08:12:32, this is after the last
> successful backup on 2021-05-22 17:35:16.
>
> 23-May 08:12 speedy-dir JobId 6: No prior o
On 5/23/21 3:50 AM, Josip Deanovic wrote:
>
> There is another option.
>
> Option 4:
> -
> If no valid full backup for the job could be found in the catalog, the
> backup job will be upgraded from incremental or differential to full
> backup. The message would be the same as the one describ
On Saturday 2021-05-22 21:14:20 Bill Arlofski via Bacula-users wrote:
> Hello Joe,
>
> I can think of three things that can cause this to happen, and at least
> two of them will show some evidence in the job log
>
>
> Option 1:
> -
> You have edited the Fileset, and the "IgnoreFilesetCha
