Hello,
2017-10-16 17:01 GMT+02:00 Adam Weremczuk <ad...@matrixscience.com>:
> Hi Radoslaw,
>
> Our Bacula db is now over 13GB in size and I feel at least half of it is
> junk.
>
It is not a huge but fairly moderate database size.
> Most likely it also suffers a performance penalty.
>
I've managed a Bacula Catalog migration from MySQL (about 24GB in size) to
PostgreSQL. The MySQL database was not tuned by a customer at all and one
of the server's restore took up to 35-45min to build a directory tree for a
8M files backup.
The same process took no more then 3-4 min on well tuned PostgreSQL with
the same data on the same bare hardware.
If you are worried about the size of your Bacula Catalog database then you
should verify what are the sizes of every table in database. Then you
should realize that a Path table is not as large as you might expect. The
largest is always a File table. So the best cleaning you can make for your
database is to remove extremely old backups.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
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
