> we have a rather large Bacula setup - ~600 Clients, database for catalog is
> 19GB large. File table is ~65 million records.
>
> Right now, bacula director can not run backups as scheduled and delays the
> jobs for up to 2 hours, as it seems the catalog is not keeping up.
>
> CPU usage on SD is: 25% (0,5 Core)
>
> CPU usage on Dir is: 10% (0,2 Core)
>
> CPU usage on Catalog is: 25% (1 Core)
>
> SD has not hit it’s storage IO limit, as I/O Wait is almost zero (24x 10k
> spindles in Hardware Raid, doing ~50MB/s avg).
>
> Also we have defined 20 parallel backup drives doing backups, so drives is
> not a blocker I guess.
>
> It seems that the bacula catalog is CPU bound and that only a single core is
> used (of 4).
>
> How can I parallelize database access with Bacula Director to speed up the
> backup process.
>

If you do not have attribute spooling enabled enable that. Also tune
your mysql database. The defaults in a lot of systems assume you have
only 64MB of ram or similar.

John

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users