Hello, I am putting bacula through it's paces and have run across some slowness when purging volumes. I am using freebsd 6.1, bacula 1.38.11_1, and postgresql-server-7.4.13_1 on a dual xeon with 2GB of ram. I have three 15-spindle raid5 arrays (5.6 TB each) to manage spooling and database needs. Each array can sustain at least 45-55 MiB/s. I do full backups to tape each night and write 920,675,853,003 bytes of 4,717,815 files across 3 400GB LTO-3 tapes. This is only a third of the data that would be archived every 24 hours if I were using bacula in production. I am concerned about the amount of time it takes the catalog to purge a volume. If this were in production, it would have to purge 7-10 volumes from the catalog each night. Is there a way I can speed up the purge process? Is there some specific postgres tuning that would increase delete performance? Actually, I've noticed select and insert performance is pretty bad, too. I'm trying some better disk management strategies that have significantly increased the insert performance (I shortened the nightly backup attribute despool by 13 hours), but deletes still take a long time. Has anyone else gone through this before? How did you solve performance issues?
Thank you, Adam ps: I have tuned the freebsd kernel for increased sysv resources as recommended in the postgres manual. Perhaps I need more sysv tuning? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
