> Sven Hartge <s...@svenhartge.de> kirjoitti 27.5.2018 kello 16.13:
>
> Um 16:40 Uhr am 26.05.18 schrieb Dan Langille:
>
>>> On May 23, 2018, at 1:02 PM, Chris Wilkinson <winstonia...@gmail.com> wrote:
>
>>> This will seem a dumb question to the experienced Bacula user. I would
>>> prefer to use mysql rather than the default sqlite. During installation
>>> (Debian Stretch repo, Bacula v7.4.4) I said no to configuring sqlite
>>> expecting to be offered the opportunity to configure mysql instead.
>>> That didn't happen. I have created an empty bacula database with the
>>> appropriate user/permissions but can't figure out how to make Bacula
>>> populate it or connect.
>
>> That sounds like a Debian packaging problem.
>
> Full disclosure: I am part of the Debian team packaging Bacula, so my
> opinion is biased.
>
> I don't think this is a problem with the packages per se.
>
> If you install the correct meta packages for the MySQL variant of Bacula
> it will install the needed database and tables in it.
>
> But if you opt out of configuring a database and then later change the
> database backend, the system does nothing, as per your selection.
>
> This is clearly stated as caveat on the README.Debian file present:
>
> ,----
> | CHANGING DATABASE BACKEND
> | =========================
> |
> | This is NOT RECOMMENDED and NOT SUPPORTED FOR LIVE DATA.
> |
> | Your current database IS NOT transferred to the new database
> | backend. The new database backend will have an EMPTY database. Your
> | /etc/bacula/bacula-dir.conf file WILL NOT be automatically adapted to
> | function with the new database backend, YOU need to do the necessary
> | changes to the Catalog{} section YOURSELF.
> |
> | If you want to go ahead anyway, you change the database backend by
> | installing a different bacula-director-DBTYPE package. This will pull
> | in the needed dependencies for the new database backend and remove the
> | ones from the old one.
> `----
>
> One nitpick one might have about the Debian Stretch meta-packages of
> Bacula 7.4.4 is its default database dependency being SQLite3.
>
> This has since been rectified in the Buster and Stretch-Backports packages
> which select PostgreSQL as default database if you install the
> bacula-server meta-package.
>
> Grüße,
> Sven.
> MySQL (MariaDB) is certainly better than SQLite, but then PostGreSQL is also certainly myriads better that MySQL (MariaDB)… When I was using MariaDB I ended up tuning it with ”mysql tuner” and adding a gigantic amount of RAM to it and tweaking with the parameters. No matter what, jobs failed occasionally with database lockups and other failures. With PostGres everything works fine just out of the box. My database size is about 8 Gigabytes and media size 8 Terabyres. br. jarif
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ 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
