> If I understand you correctly, I must enable concurrent jobs to fix my
> problem?

Yes. Take a look at the manual for the details on how to enable concurrency.

More precisely, in a concurrent job scenario, enabling data spooling
forces sequential writing to tape (i.e. completely spooled jobs are
queued and written to tape one at a time).

There are two caveats:

1) bacula starts despooling as soon as there is a completed job -- make
sure your spool device is fast enough to deliver the full data rate
needed by your tape drive while there are still some jobs spooling.

2) I am not sure about what happens if the maximum spool size is reached
in this case. With no concurrency, the running job is paused while
spooled data is flushed and then spooling resumes; with concurrency, I
do not know whether this pause-flush-restart cycle is done for a single
job (thus preserving the sequential writing) or for all spooled jobs
(reverting to the "interleaved" behavior). Maybe someone can shed some
light on this point?

I have been running with this setup for a couple of years with good
performance and no problems so far.

> But I'll end up with a messier volume format which will make restore
> times longer?

Only if data spooling is disabled.

Andrea


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users