Am Mittwoch, 26. August 2015 17:19:17 UTC+2 schrieb [email protected]: > Zitat von David Pearce <[email protected]>: > > > We use data spooling and this can increase the total time, but it > > definitely keeps the tape drive streaming (going at full speed) > > reducing wear-and-tear. > > > > However, I agree that a job that is spooling to disk should not > > reserve a tape drive and block it from other jobs. I guess that is > > the cost of using data spooling. > > It is possible to spool and despool (write to tape) at the same time, > but not within the same job. We have a setup with around 10 concurrent > running jobs with data spooling and while one of the jobs do > despooling to tape the others go on spooling fine. But be awere that > you need a really fast spooling area to saturate a LTO-6 for example > while other jobs write to the same IO device with 10G speed. > > Regards > > Andreas
This may be correct. If you have two jobs that use same pool spooling/despooling can run parallel. If you using different pools for every client job you will see: Jobs waiting to reserve a drive: Bareos seems to check, before the job starts, if there is any volume for writing. To check the Volume must be loaded to the tapedrive. Is there a way to move this check after the spooling process? -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
