[pkg-bacula-devel] Bug#1112458: Bug#1112458: bacula-bscan: bscan compiled with only PostgreSQL support
Sven Hartge
sven at svenhartge.de
Fri Aug 29 17:57:59 BST 2025
On 29.08.25 17:21, Benoit via pkg-bacula-devel wrote:
> I came to the situation where I lost my bacula MariaDB database (InnoDB index corruption repair unsuccessfull, dump and re-insert resulting in empty table) last successfull dump already rotated away.
>
> So I wanted to re-populate the database with bscan but bscan complains it an not connect to the PostgreSQL Database.
>
> There is a -D option to specify a 'driver' but no matter how I try to spell MySQL or MariaDB, I always get the
> error it is trying to connect Postgress.
>
> Google revealed, there should be different packages of bscan compiled for the corresponding database, like there are for bacula-sd
>
> Debian only provides one flavour - Postgress which is useless for recovery with a MySQL database.
> ii bacula-common 15.0.3-3
> ii bacula-common-pgsql 15.0.3-3
> ii bacula-sd 15.0.3-3
> ii libc6 2.41-12
> ii libstdc++6 14.2.0-19
By installing just "bacula-bscan", apt choses the first database
dependency automatically, which is for PostgreSQL.
To get a MySQL-capable bscan, you need to manually install
"bacula-common-mysql". Then the correct driver will be available and
recovering a MySQL DB will work.
Grüße,
Sven.
More information about the pkg-bacula-devel
mailing list