Backup Central

I know that the quantity of files and the retention time are the big factors in the size of the catalog database in bacula. What would be a good calculation to use to ensure a healthy amount of space for the database? I have a postgresql database sitting in a partition with nearly 4GB free. I had a large backup fail at the end when it was attempting to update the catalog because there wasn't enough space. Granted there were more than 11 million records being inserted. There have been no other errors or concerns from postgresql until now.

Patti Clark
Information International Associates, Inc.
Linux Administrator and subcontractor to:
Research and Development Systems Support Oak Ridge National Laboratory


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

On Thu, Jul 19, 2012 at 08:35:42AM -0400, Clark, Patricia A. wrote:

I know that the quantity of files and the retention time are the big
factors in the size of the catalog database in bacula. What would
be a good calculation to use to ensure a healthy amount of space for
the database? I have a postgresql database sitting in a partition
with nearly 4GB free. I had a large backup fail at the end when it
was attempting to update the catalog because there wasn't enough
space. Granted there were more than 11 million records being
inserted. There have been no other errors or concerns from
postgresql until now.

Hi Patti,

we're using MariaDB 5.2.x with a retention period of 30 days for
around 100 clients. Here's some db stats from bweb:

Total clients: 135 Total bytes stored: 77.74 TB
Total files: 81038379 Database size: 126.59 GB

All the best, Uwe

--
NIONEX --- Ein Unternehmen der Bertelsmann AG



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Hello,

2012/7/19 Clark, Patricia A. <clarkpa < at > ornl.gov ([email]clarkpa < at > ornl.gov[/email])>
I know that the quantity of files and the retention time are the big factors in the size of the catalog database in bacula.  What would be a good calculation to use to ensure a healthy amount of space for the database?  I have a postgresql database sitting in a partition with nearly 4GB free.  I had a large backup fail at the end when it was attempting to update the catalog because there wasn't enough space.  Granted there were more than 11 million records being inserted.  There have been no other errors or concerns from postgresql until now.



In my projects I use a following database estimation:


DBSize = Nb_of_files_in_file_table * ( 400B + 400B )
where
Nb_of_files_in_file_table is a number all of files stored in catalog database for all required backups (something you can get from select count(*) from file;)
400B is an average size of a file record
400B is an average size of required indexes


It is accurate in 90%-95%, enough for estimation.


best regards

--
Radosław Korzeniewski
radoslaw < at > korzeniewski.net ([email]radoslaw < at > korzeniewski.net[/email])