On Wed, 26 Aug 2015 17:19:15 +0200 [email protected] wrote: > > 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 >
And there may also be cases where data spooling does not make much sense, eg. a large fileserver with fast storage and tape library attached to the same machine and the average file size not too small so that it can deliver data fast enough to the tape. Also not needing additional concurrent jobs from multiple clients. In that case I'd only use attribute spooling, see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirJobSpool%20Attributes Regards -- Stephan Dühr [email protected] Bareos GmbH & Co. KG Phone: +49 221-630693-90 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz, M. v. Wieringen -- 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.
