Many thanks for the response Douglas, all good stuff; I'm slowly learning the logic of Bareos and all this helps form a "bigger picture"
> Also, note that there are two different types of spooling: Data and > attributes. Data spooling is, like you typed, spooling to disk/SSD before > writing to tape. Attribute spooling is the meta-data insert into your > database, it stores those up and then does them all at once. > > We've found that spooling attributes is almost always good, so we set that as > the default. I neglected to mention we have attribute spooling on as well. I read that in a "cookbook" somewhere and deiced it made sense so glad to have it confirmed. > For spooling on disk to disk backups I think it depends more on how many > backups you have running concurrently. We don't use spooling for disk based > backups. Not here either; just spooling for the tape jobs. > On our tape backups, which are virtual full backups, we use spooling to > increase throughput. We run 5 parallel virtual-full backups that are spooling > to disk, but only one de-spools at a time to tape. This tends to keep the > tape > drive streaming more often than not, and the parallel virtual-full backups > let > the whole thing finish faster. If I understand what you are saying here these are jobs that create a full backup from an "Always Incremental" schedule?. On your single despool to tape, what sort of through put do you see on LTO-6? > > We aren't letting the tape drive do any compression, with today's CPUs we let > Bareos do that work. I'll give that a go. Cheers Dan -- 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.
