Hello,
czw., 7 lut 2019 o 02:34 Adam Nielsen napisał(a):
> > Spooling can reduce overall throughput because the data is
> > sequentially written to disk and then read back.
>
> This is what got me. I thought it was a buffer to ride out variations
> in disk read speed (like the mbuffer program)
Hi
This is a log of a job done with this config :
Two 400GB ssd drive in raid0 are in my storage server mounted in /data_spooling
My librairy is a SCALAR i500 with 2 LTO7- Fiber channel drives.
speed lan on servers : 10Gb/s
Fiber channel : 8Gb/s
speed read/write on raid 0 ssd : about 8 Gb/s
the a
On Thu, 07 Feb 2019 11:32:29 +0100
Wolfgang Denk wrote:
> Dear Adam,
>
> In message <20190207185030.35830...@teln.shikadi.net> you wrote:
> >
> Also, disk space is cheap - where is the problem of using a much
> bigger spool area? I use only LTO4 tapes so far, and I have a
> 1.5 TB spool area.
Dear Adam,
In message <20190207185030.35830...@teln.shikadi.net> you wrote:
>
> It may also help in this case, but so would buffering instead of
> spooling. I was under the impression that in the case of slow clients,
> Bacula is designed to read from many clients at the same time, so that
> it c
Hello,
There seems to be some differences of opinion about Bacula's spooling.
Spooling was implemented for a number of reasons:
1. Primarily to reduce tape shoe shining (particularly due to Clients
doing Incremental backups)
2. To allow multiple jobs to write to the tape in larger chunks to
impro
> I have a different understanding of the function. there is no need
> to read "data off clients as fast as possible" - if your clients are
> fast, they have no problems to provide the data at lower rates,
> too. It's the other way round; if your clients are slow so they
> cannot feed the data fa
Dear Adam,
In message <20190207113145.144af...@teln.shikadi.net> you wrote:
> > Spooling can reduce overall throughput because the data is
> > sequentially written to disk and then read back.
>
> This is what got me. I thought it was a buffer to ride out variations
> in disk read speed (like the
> Spooling can reduce overall throughput because the data is
> sequentially written to disk and then read back.
This is what got me. I thought it was a buffer to ride out variations
in disk read speed (like the mbuffer program) but it's not. The
purpose is to get data off clients as fast as poss
