Em 21-09-2011 13:33, Alexandre Chapellon escreveu:

As Gavin pointed out, a 150GB database is huuuuuuuuuuuge for only a dozen client.
Unless you have billions of files on each client there is no reason your catalog is that large.
Are you sure you correctly applied job and file retention on your catalog? Also are you sure you catalog is not full of orphaned records?

Before migrating to postgres (which is a good choice for big catalogs), I would look at the catalog to see if all retention period are correctly applied.

I am running dbcheck to see how many rabbits come out of the bushes. File table is only 6.6GB and Log is 105GB. What's that Log table for? It only have blobs...

Also, in a near future I will change bacula-dir to another server, which will be a good opportunity to start a blank catalog and go with Postgres, without any migration, just keeping the old one sitting there until the end of retention period.

--

Marcio Merlone

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1

_______________________________________________

Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

--

Alexandre Chapellon

Ingénierie des systèmes open sources et réseaux.
Follow me on twitter: @alxgomz