Hello,

I enable data spooling for almost any job, because my LTO4 drive's
hw-compression allows to stream _my_ data at little over 100MByte/s
average, which bacula-fd can't deliver (localhost FD-SD connections
allow ~25MB/s with 60+% CPU usage; SoftCompression is disabled; oberved
FD reqests are 4KB/t only, but that's a completely different issue I
have to look at more closely some times later).
I'm aware that the numbers above are highly workload dependent and are
not representative.
They basically should give an idea why I need data spooling – nothing
more. Environemnt is bacula 7.0.5 (dir, sd and fd), FreeBSD 10.1 (amd64)
(also dir, sd and fd), LACP-GbE (irrelevant since I'm using localhost
sockets), 3.4GHz Xeon-E3v3, 8GB RAM and two LSI2008.

A typical job is 100-500GB in size. So spooling with only 25MB/s takes
significant ammount of time.
That's why I want to start the job as early as possible..
My problem is that data spooling starts _after_ the volume has been
mounted and positioned.
So if I start the job at midnight, no single bit get's spooled unless
somebody feeds the correct tape next morning :-( And next morning very
often delays to "next lunch"; that's were the missing 4 hours breaks the
timetable for my setup.

Is there already an option I missed, which would enable data spooling
without requesting the volume first?
That would save exactly the hours my setup needs as buffer if somebody
forgets to feed the tape.
Or is there any reason why data spooling must be delayed? I can't
imagine one. If something goes wrong at despooling, nothing changes if
volume was available before spooling or not.

Thanks,

-Harry




------------------------------------------------------------------------------

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users