Have been tinkering with spooling... 1 server (perhaps 1.6 TB of backup
data) and 20 clients (varying from 30 - 400 GB per client).

It is sort of difficult to test since I don't really know what is going
to happen with a FULL backup of many TB of data until it actually runs
and it's not the sort of thing I want to do for fun.

SD has 'Maximum Spool Size = 750G'

Disk has approximately 860G free when not backing up/spooling

Allowing 3 simultaneous jobs at a time.

Last month - this setup worked well... cut my backup time in half but
that of course was incremental backups but worked rather poorly for my
first 'Full' backup.

I am thinking that the local server (running SD & Director w/ 1.6 TB of
backup data) swamped the spool and so I am thinking of turning off
spooling for this system - possibly putting it a lower Priority level so
it completes first but I would rather have the first couple of clients
spool while the server is being backed up.

Any other suggestions? 

If I have a Maximum Spool Size of 750G, should I also set Maximum Job
Spool Size of 250G to allow for 3 simultaneous jobs?

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


------------------------------------------------------------------------------
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