On Wed, May 28, 2008 at 8:07 AM, Steve Campbell <campbell AT cnpapers DOT com> 
wrote:
> I run the default backup of my catalog twice a day, along with a lot of
> other jobs. The size of the catalog grows slightly every day and now is
> about 1.8 GB.
Is this the database size or the backup? If the backup are you using
compression?

> I keep a six month rotation of full monthly backups, along
> with some weekly differential and daily incremental backups. As the
> 6-month-old monthly backups are purged, shouldn't the catalog size drop?
>
> I have not reached the 6 month mark since I started using Bacua, so no
> full backup volumes have been purged as yet. I am asking only to ensure
> I am not forgetting to do something maintenance-related.
>

We have been using bacula since late 2003 or early 2004 and to this
point we have 4,500,000 files, 38 clients and 10336 completed jobs.
The catablog database (postrgresql) is 16.38GB (size reported in
bacula-web) but when compressed (during the catalog backup) it is less
than 800MB.

To reduce the size of the database you may need to compact it
(database specific - VACUUM in postgresql) and possibly run the bacula
dbcheck program. I do not do either very often because the server has
100s of GB free disk space and these operations take hours to
complete..

John

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users