Le 21/09/2011 18:56, Marcio Merlone a écrit : Em 21-09-2011 13:33, Alexandre Chapellon escreveu:It is supposed to contain bacula report... just like in the bacula log file.As Gavin pointed out, a 150GB database is huuuuuuuuuuuge for only a dozen client. I'm not sure having such a big amount of data in another table hurts, may be it does if you use innodb. If you use MyISAM... my guess is it should not hurts... but note I am not a DBA! However, I'd like to know if this table can be safely purged? As one day or another it will grow to an unacceptable size... (even more if I have the same info in logfile). 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. Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users --
|
<<attachment: a_chapellon.vcf>>
------------------------------------------------------------------------------ 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users