We recently upgraded Bacula from v9.4 to v9.6 as part of a Ubuntu 18.04 to
Ubuntu 20.04 upgrade, and immediately we started noticing hundreds of
database connections left open in a read state. As I write this we have
400+ PostgreSQL connections open to the bacula database, all idle, here is
a rando
I gave up trying to get backblaze to work and switched to Wasabi with
s3fs-fuse. It was really easy to setup, and so far has been quite fast and
reliable. The price is very similar too.
On Sat, Jun 8, 2019, 5:36 PM sruckh--- via Bacula-users <
bacula-users@lists.sourceforge.net> wrote:
> I have
So I managed to make some progress after bumping up the debug verbosity in
bacula-sd...
1. I didn't have "Plugin Directory = "/opt/bacula/plugins" defined in my
bacula-sd.conf Storage directive, so the cloud plugin was never loaded and
therefore the device could not be loaded.
2. My bacula-dir.con
Currently we have Bacula setup to copy jobs to a separate storage pool that
is on a remote SSHFS mount, which is working fairly well. However now that
Bacula (v9.4.2) offers its cloud plugin we would prefer to copy the jobs to
the cloud instead. When running the copy job we receive the following er
We have some jobs that backup SQL databases, so immediately after the
backup is complete we have a "AfterJob" that restores it to a test system,
then we run a DiskToCatalog verify job. However the restore fails with a
Block checksum mismatch and immediately after the verify job succeeds.
The backu
