Hello,
Could you please add a "bacula-users <bacula-users@lists.sourceforge.net>"
list to conversation as this is a bacula-users discussion. Thanks.
pon., 27 sie 2018 o 16:06 George Anchev <stu...@anchev.net> napisał(a):
> This:
>
> SELECT StartTime, Job FROM Job WHERE JobStatus IN
> ('T','W') AND Type='B' AND Level='F' AND Name='...'
>
> works fine for the local job (for which incremental
> estimates work fine) and for the remote job (for which
> the incremental estimate goes to Full). Both queries
> return a single record for each job. Adding:
>
> AND ClientId='...' AND FileSetId='...'
>
> results in no records for any of the 2 jobs.
>
So this is a main reason why you experiencing a such behavior. You know
that a fileset has changed, so what records it return when you add "AND
ClientId='...'" to your query?
> To my mind it seems there is no difference between the
> records for two full jobs and that should not be a
> reason for the wrong estimate.
What do you mean by "there is no difference (...)" as both jobs has a
different clientid at least, so there are differences, right?
> Of course: Please feel
> free to correct me as I may be wrong.
>
> FWIW: bat also shows the two full jobs.
>
> > It is plausible that you've changed not only fileset
> > but a client or job name,
>
> I have not done that for any client (neither local,
> nor remote).
>
As you can see above there are a four main parameters which show if there
is a suitable full level backup available: Job Status, Job Name, ClientId,
FilesetId. They all have to match, so you have to check which one makes a
problem. Assuming you have correctly setup a parameter "Ignore FileSet
Changes = yes" then you can ignore a FilesetId in this query.
>
> > The other possible causes is a parameter "Maximum
> > Full Interval" which forces full backup when lat
> > full backup was executed too long ago.
>
> That is not the case because the full job has a
> timestamp 2018-07-15_17.39.48_31 and:
>
> >> File Retention = 60 days
> >> Job Retention = 6 months
>
>
No, it is not a retention. The MFI parameter instruct Bacula to upgrade any
level to Full if the last full was successful more then time interval set.
The job message in case of MRI will be the same as for changed Fileset, but
it cant be ignored with an other fancy parameter.
I have been thinking - is there a way to ask Bacula
> why it says:
>
> "No prior or suitable Full backup found in catalog"
>
>
I do not know. You can just query catalog for this.
> Considering there is a prior Full backup, that leaves
> only "suitable Full backup" as a possible reason. IOW:
> what is considered "suitable"?
>
It is very easy and the above sql query should answer your question. To
recap: the proper job status, the same job type and job name, the same
client (clientid) and the same fileset name and content verified by a MD5
checksum. So if your client name was: client1 and now it is a Client1 then
for Bacula they are two different names. If you changed a Fileset name in
the same way as a client before or you changed a single character in your
Fileset content then MD5 will change. If any of your job's parameters won't
match then Bacula will consider it "unsuitable" for
incremental/differential backup level and will upgrade it to full. The same
when a time interval set at MFI parameter will pass.
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
