On 17/10/2017 02:01, Adam Weremczuk wrote:
Our Bacula db is now over 13GB in size and I feel at least half of it is
junk.
That is a microscopic database in Bacula terms, mine stabilised at
around 90Gb with a retention of 12 months, and there are many Bacula
systems with databases in the
On 16/10/17 16:01, Adam Weremczuk wrote:
Hi Radoslaw,
Our Bacula db is now over 13GB in size and I feel at least half of it
is junk.
Most likely it also suffers a performance penalty.
Switch to postgresql asap. You will breathe a LOT easier once you've
done that.
MySQL is good at what
Hi Radoslaw,
Our Bacula db is now over 13GB in size and I feel at least half of it is
junk.
Most likely it also suffers a performance penalty.
More reason for keeping it clean: backups, upgrades, migration to a
different server etc.
I don't know how to safely and efficiently perform this
Hello,
2017-10-16 15:33 GMT+02:00 Adam Weremczuk :
> Does it mean the only option is throwing this database into a bin?
>
Orphaned records (especially Path records) are no harmful to Bacula at all
and there is no any requirement that it should be removed. They only take
Hi Heitor,
Thank you for a quick reply.
We have plans of moving Bacula to a dedicated box, new tape drive and
install the latest version.
That's unfortunately unlikely to happen before Xmas.
And then did you kill the MySQL thread? Perhaps you should have waited.
I don't know exactly what
> Hello,
Hello, Adam,
> I'm running Bacula 5.2.6 on Debian linux.
You are strongly advised to move to earlier versions.
> A dry run of dbcheck has revealed the following.
> dbcheck -v -c /etc/bacula/bacula-dir.conf
> Hello, this is the database check/correct program.
> Modify database is off.
Hello,
I'm running Bacula 5.2.6 on Debian linux.
A dry run of dbcheck has revealed the following.
dbcheck -v -c /etc/bacula/bacula-dir.conf
Hello, this is the database check/correct program.
Modify database is off. Verbose is on.
Please select the function you want to perform.
1) Toggle