Hello,
sob., 25 sie 2018 o 13:40 George Anchev <stu...@anchev.net> napisał(a):

> On Sat, 25 Aug 2018 00:00:07 +0200 Radosław
> Korzeniewski wrote:
>
> > Where? You should be more detailed if you want help.
> > I do not see your configuration and environment.
>
> Sorry, I thought it was clear as from my earlier
> message as your reply sounded like we were on the
> same line. Anyway I don't mind clarifying:
>
> I have added:
>
> Ignore FileSet Changes = yes
>
> in the fileset of the remote host and rebooted the
> machine running the DIR service.


This is an sql which checks for prior full backup level:

"SELECT StartTime, Job FROM Job WHERE JobStatus IN ('T','W') AND Type='%c'
AND "
"Level='%c' AND Name='%s' AND ClientId=%s AND FileSetId=%s "
"ORDER BY StartTime DESC LIMIT 1"

so, to find that a valid level full backup exist in catalog all the above
values should be met (in the above query the parameter Type=B and Level=F).
You have to check if in your situation the query return a single row when
you substitute all other required parameters. When this query return no
data then you should check why. It is plausible that you've changed not
only fileset but a client or job name, i.e. The other possible causes is a
parameter "Maximum Full Interval" which forces full backup when lat full
backup was executed too long ago.

Happy digging.

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to