New users considering switching to Bacula are often curious about how large other Bacula installations are: how many clients, how much data is being backed up, how large the catalog database gets, etc. While such questions usually get one or two people answering, I thought it would be nice to try and generate a quantitative set of data to give people a clearer picture.

This perl script will run a handful of queries against your catalog, and print the resulting statistics. Open the script file, and edit the first few lines to reflect your configuration, including the database username, password, and driver. It was written and tested against MySQL 4.1, but uses standard SQL so should work against other engines.

bacula-dbstats.gz

If you would like your results to be included, you can either add yourself to the list below or just email them to me directly at the email address at the bottom of the page (note the anti-spam obfuscation). Please include the output of the script, along with the version of bacula and basic statistics of the servers you are running your storage daemon and catalog on (operating system, CPU, memory), and what kind of and version database you are running (MySQL, Postgresql, SQLite).

— Frank Sweetser 2006/01/29 16:56

These are just a few preliminary results, thrown up by hand, to give a flavor of what the final results will look like. The finished product should also have some basic statistics, sorting, etc.