On 12/05/16 06:50, Robert N wrote: > Hi, Hello.
> I also have performance issues. Does the spooling make any difference > by copy jobs? I mean the data is anyway already on the disk, so > copying over to a spool ( disk ) and then to tape improves > performance? I thought exactly the same thing, and it turned out that I was wrong. > what do you mean by "I'm not interleaving my backups on disk anymore" > and how do you achieve it with parallel jobs? I'm doing virtual full backups to LTO-6 tape, which is not quite identical to copy jobs, but really very close. (Virtual full backups have to touch more source backups than copy jobs.) And I still spool the virtual full backups before writing to tape which allows me to get 160 MB/s to our LTO-6 tape drive. When I did virtual full backups directly to tape I only got between 80 MB/s and 100 MB/s. And over the 200 virtual full jobs that I run each week they are from wall clock perspective faster by spooling to disk and then writing to tape. I strongly suggest that you turn both Spool Attributes and Spool Data on. -- 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.
