On Mon, 27 Aug 2018 16:36:53 +0200 Radosław Korzeniewski wrote: > 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?
No records show (for any of the 2 clients). > What do you mean by "there is no difference (...)" > as both jobs has a different clientid at least, so > there are differences, right? A difference would be: The sql query for client-local: show 1 record. The sql query for client-remote: show 0 records. Considering the query shows 1 record for each job, I say "there is no difference", i.e. the reason is not the lack of a Full job in client-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. As I mentioned earlier I have updated only the file paths in the filesets (for both clients) and added the "Ignore FileSet Changes = yes". Absolutely nothing else was changed in the config files. > 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 never used "Max Full Interval" in my configs. Now that I read the docs: "If this directive is not present, or specified as 0, then the age of the previous Full backup is not considered." So I think this can be excluded as a possibility too. > 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. None of those were changed. FWIW: I have no problem running a full job for the remote client and then test an estimate again. However I was interested to learn if I am missing something essential which may be new for Bacula 9 or if there is a bug. -- 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
