Hi,
I have a complex bacula config (2.4.4) with about 100 clients, 300 Jobs 
and 48 Storages on two Storage Daemons (32 on one and 16 on the other). 
The multiplicity of Storages is for paralelism. The clients are spread 
among the storages with config generator, which selects the Storage for 
them. But still many clients share the Storages and must wait for each 
other. I noticed each job goes through two phases: running phase 
(aquiring data from client) and Dir inserting attribures phase (DIA). In 
DIA phase job still blocks the Storage but actualy it does not need it 
more. Is it possible to avoid that? Some asynchronous catalog inserting 
or some feature in 3.0?

Marek

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users