On 31.12.18 20:24, Kern Sibbald wrote: > Yes, MariaDB is supposed to be MySQL compatible, but it is not really. > The first time that I installed MariaDB over MySQL (with lots of > problems -- best to remove MySQL and the DB first), I ran the Bacula > regression tests and MariaDB failed with a false detection of a lock > deadlock, which I reported. It took awhile, but the project did fix the > problem so it *might* now run Bacula with no problems. That is to be seen.
I've been running Bacula on Debian for my Universities IT department since Bacula 1.x, at first with Postgres, then with MySQL and then with MariaDB once Debian switched to it. Currently there are 350 Clients with ~30,000 jobs and ~6000,000,000 Files in the database, at a size of ~200GiB. (Which reminds me to run dbcheck again, since its the new year and everything.) So far I've never seen any problems with Bacula and the database. (Yes, I do have a separate DB server with 128GiB RAM to run this on.) I don't know how Postgres would work and how much resources it would need (I have no doubt it would work perfectly now.) but I remember in the very early days, we had massive problems with Postgres, as the Vacuum process would soon take up all resources, never finish and block the backup all together. Which is why we switched to MySQL back then. Grüße, Sven.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
