Hello,
pon., 27 sie 2018 o 17:59 George Anchev via Bacula-users <
bacula-users@lists.sourceforge.net> napisał(a):

> 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).
>

Something is not done correctly. This is how I check this kind of
"interesting cases":

bacula=# select clientid from client where name='bacula-devel-fd';
 clientid
----------
        1
(1 row)

bacula=# select * from fileset where fileset='Full Set';
 filesetid | fileset  |          md5           |     createtime
-----------+----------+------------------------+---------------------
         1 | Full Set | cxZEhH/BvX+AMx+bok5A6B | 2018-04-26 13:06:08
         2 | Full Set | M/gtx//iQ5l+ETJ4a+/UKB | 2018-04-26 13:07:13
         5 | Full Set | d84U+GFlTDhELgdZg2J5UB | 2018-05-16 09:57:56
         8 | Full Set | E8Axaz/D4//jZ8o1D7+IXC | 2018-06-15 11:42:08
        11 | Full Set | xT/Gq40YV5wwg5+Q4E+WIB | 2018-07-20 14:15:00
        14 | Full Set | bwZTa6/iIBASo8l3M4+cKB | 2018-08-02 11:01:44
(6 rows)

bacula=# SELECT StartTime, Job FROM Job WHERE JobStatus IN ('T','W') AND
Type='B' AND
Level='F' AND Name='BackupClient1' AND ClientId=1 AND FileSetId=14
ORDER BY StartTime DESC LIMIT 1;
 starttime | job
-----------+-----
(0 rows)

bacula=# SELECT StartTime, Job FROM Job WHERE JobStatus IN ('T','W') AND
Type='B' AND
Level='F' AND Name='BackupClient1' AND ClientId=1 AND FileSetId=11
ORDER BY StartTime DESC LIMIT 1;
      starttime      |                 job
---------------------+--------------------------------------
 2018-07-31 12:35:47 | BackupClient1.2018-07-31_12.35.44_09
(1 row)

as you can see the BackupClient1 job has multiple fileset definitions, but
the last one (filesetid=14) has no full backup level available in catalog,
but the previous one with fileset=11 is available. This is virtually the
same case you should have in your catalog. If I execute estimate or backup
job with level=incremental it will be upgraded to full by Bacula
automatically. When I remove a filesetid=11 from above sql query it return
the job record for 'BackupClient1.2018-07-31_12.35.44_09'. You should
expect the same behavior in your Bacula installation. Check this again.

> 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.
>

Until you show your queries as I done above I cannot judge here. :)


>
> > 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.
>

If you change a Fileset contents then MD5 is changing too.


>
> 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.
>

I think nothing changed in this area on 9.x release, but Kern should have a
final word.

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