Hi all
I was wondering if someone could clear up how the concurrent jobs are
dealt with by the storage daemon.
I only have one backup device (LTO3), and have a spool area defiend for
that device. if I had (for example) 4 concurrent jobs running, does this
mean:
4 clients dumping data back to storage-daemon
and
4 sets of spool files being created
If the spool area size limit is reached while clients are still sending
their data, which client's data is sent to the tape? Is the data sent to
tape interleaved in "chunks", or does one client get sent to tape, and
the rest of that client is spooled + taped before the other concurrent
jobs continue? (Yes, I know, a larger spool area would help here, but...)
My systems (at work and at home) are currently running just fine with 1
concurrent job, but I would like to look at reducing the overall time
taken for my scheduled backups.
Many thanks for putting up with my newbie questions
Steve
8 simultaneous backups should not be a problem. In my office, I run a
maximum of five backups (4 to one device) without problems, but that's
only because my backup hardware is *old* and can't handle a higher data
throughput without shoe-shining the tape drive. This is with 100MBit
network, a dumb switch and clients of widely differing speed, from
Pentium systems to dual-core 2GHz.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
