On Thu, Sep 01, 2011 at 11:06:47AM -0400, mark.bergman AT uphs.upenn DOT edu 
wrote:
>               [A], while it should be close to [B]. The reason for
>               the decrease in performance is that bacula stops all
>               spooling as soon as it starts de-spooling.
> In an ideal configuration, there could be multiple spool directories defined,
> and bacula would open a new spool file in the next directory as soon as it
> begins despooling.

We run 1 spool directory and several concurrent jobs spool to it. While
one gets despooled, the others continue spooling. However, if you run
out of spool space, spooling is stopped on all jobs till a complete
despooling is done.
Best practice IMHO with big disks:
- SpoolSize large enough to hold most of your backups completly
- Spool Directory large enough to hold several jobs

In my case most backups are <50GB, incrementals often only <100MB. I use
a 1TB Spool Directory and a Spool Size of 800GB, large enough for all
but my biggest backup job. It works fine here.

Regards,
        Adrian
-- 
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
Fon: +49 (7 11) 78 28 50 90 - Fax:  +49 (7 11) 78 28 50 91
Mail: lihas AT lihas DOT de - Web: http://lihas.de
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users