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.
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. 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).
> 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
I have been thinking - is there a way to ask Bacula
why it says:
"No prior or suitable Full backup found in catalog"
Considering there is a prior Full backup, that leaves
only "suitable Full backup" as a possible reason. IOW:
what is considered "suitable"?
--
George
------------------------------------------------------------------------------
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
