Hello,
I just noticed that you are running MariaDB. Please be aware that Bacula does not support MariaDB and we are not yet ready to do so. If MariaDB is plug compatible with MySQL, which we do support, that would be fine, and it started out that way, but recently I wanted to see if Bacula could support MariaDB and on Ubuntu 16.04, it turned out to be a nightmare to switch from MySQL to MariaDB and back again -- that is to say almost impossible without totally wiping out all information in the database. Worse, MariaDB has/had lock conflict bug that caused it to fail. The MariaDB programmers have now found and fixed the bug, but I have not followed in which version it will be fixed. Bottom line: If you are running MariaDB there may be some problems that come up if you are expecting it to be 100% compatible. To completely support MariaDB Bacula will need to define it as a new database type and review *all* of the SQL that we send to it to make sure all the SQL works by changing it where necessary. This is a huge amount of work. Best regards, Kern On 08/27/2018 10:11 PM, George Anchev via Bacula-users wrote: On Mon, 27 Aug 2018 18:29:17 +0200 Radosław Korzeniewski wrote:Until you show your queries as I done above I cannot judge here. :)Attached.To avoid potential misunderstandings: Incremental estimates for local* work fine. Incremental estimates for remote* fall back to Full. The <unrelated> incremental jobs also estimate fine but I have hidden them to avoid visual clutter. FWIW: I have no idea why FileSetId=64 exists (as well as many other older records in FileSet table which I have used in the past and don't exist any more). -- 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