>> Not for a single job. When the storage daemon is writing a job's spooled
>> data to tape, the client must wait. However, if multiple jobs are
>> running in parallel, then the other jobs will continue to spool their
>> data while one job is despooling to tape.
>
> I come back on this. I've setup on director's storage Autochanger{}
> configuration:
> Maximum Concurrent Jobs = 5
> but i've set on storage configuration, in the Device{} stanza:
> Maximum Concurrent Jobs = 1
> as suggested for tapes; clearly i've only one device/tape. I've defined two
> jobs, but the first run, the second:
> is waiting on Storage "BPBKPLOMAutochanger"
> And don't start to spool data, wait there indefinetively.
Sorry, i really don't understand and i need feedback...
I've read many time that tapes are handled better as they are, sequential
media; so they need on storage:
Maximum Concurrent Jobs = 1
but in this way, if i need spooling (and *I* need spooling for tapes!) i can
run on tape jobs only sequentially: eg:
- spooling job1 -> despooling job1 (repeated many times)
- spooling job2 -> despooling job2 (repeated many times)
- ...
A bright suggestion is to define different jobs and so 'interleave' that,
so when job1 is despooling, job2 can spool data.
But if set on storage 'Maximum Concurrent Jobs = 1', the storage do exactly
one job at a time. job2 wait the end of job1. Period.
I can set 'Maximum Concurrent Jobs > 1'? What i can expect from the SD? Will
despool job1 and then despool job2, or i can expect to have also the
despooling of job1 and job2 'interleaved', that i suppose is a bad thing?
Sorry, thanks.
--
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
