> If you are backing up one machine with a small number of files then sqlite > might be okay, but otherwise you'll probably find it will be a performance > bottleneck for anything bigger. > > I recommend you go with postgresql (or mysql).
I've used MySQL in the past, and Bacula is just apparently not optimized for it (or vice-versa, I'm not sure which). We run a fairly beefy MySQL server and we have hundreds of apps and web sites that all use that server and all of them work extremely well but when we used it for Bacula, the query that it used to build a list of files to restore took *ages* - in some cases more than 24 hours, and in some cases it never finished at all - for our data set. When we switched to Postgres, that query went down to a few minutes. Our backup load has changed significantly since then - we now use ZFS snapshots for our multi-terabyte, multi-million-inode file systems and use Bacula for our smaller VMs, none of which have more than a few tens of thousands of files each. So maybe it's time to revisit using MySQL. I just really hate maintaining a whole database server for one application, especially one as unwieldy as Postgres. Postgres requires a fair amount of memory, and has some compatibility issues with FreeBSD Jails (it requires you enable sysvipc for all jails, which is something of a security concern). It's also "one more thing" that I have to monitor. -- Tim Gustafson t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
