On Mon, Jul 20, 2020 at 4:56 PM Gary R. Schmidt <g...@mcleod-schmidt.id.au> wrote:
> Bacula can only be built with support for one database, if you want to use > MySQL you will either have to ask the distribution maintainers to produce > one, or build Bacula yourself from source. > Has this always been the case? If so, why is there a "dbdriver" parameter in the director configuration at all, if it cannot actually be used? I could certainly buy that the Fedora package maintainer decided to switch from MySQL (which has always worked in every previous Fedora distribution since I started using Bacula back with version 5) to PostgreSQL; this sort of thing happens in Fedora. I did verify that the Bacula 9.4 packaged for Fedora 31 seems to be set for MySQL, because if I try to specify "dbdriver = postgresql" on my old 9.4/F31 box, then I get the converse error: 20-Jul 17:05 bacula-dir JobId 0: Warning: Dbdriver field within director config file "postgresql" mismatched with the Database argument "MySQL" passed during Bacula compilation. Assuming this is all correct: I think there is nearly zero chance of getting the Fedora people to produce a different package; Fedora is notoriously short of package maintainers. So I could either compile 9.6 from source, or downgrade to the Fedora 31 version that worked with MySQL. I have the additional issue to deal with that my Storage server is on a Raspbian system which of course isn't going to get new Bacula versions until the next OS upgrade, but I have found that generally different minor versions work together just fine as long as it's the same major version. I realize it's not guaranteed unless DIR = SD >= FD. Thanks for setting me straight, one way or the other I can move forward now. --Greg
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
