To everyone that had replied to my request for help.
I have reduced the size of my spool buffer from 300G to 50G and run tests.
Things work better but I'm still getting timeouts. Now they appear to be
random over the out spooling. What I mean is that some jobs will do 1 to
multiple output
The engineer is probably mistaken. The line seems clearly to have
dropped. Perhaps you are still missing a Heartbeat interval somewhere
-- there are quite a number of them. The other thing is that I would
recommend a Heartbeat Interval of 300.
Another alternative is to upgrade to version 7.
One more suggestion, reducing the spool size has also helped. I have a
mix of clients where initially everyone was using a 500GB spool size. My
10Gb connected clients were fine, but my 1 Gb clients would timeout when
things were busy - I dropped the spool size to 50GB for the 1 Gb clients
and rar
My heartbeat interval is set to 300 - you should probably increase yours.
I originally had a smaller interval and had some clients that would time
out - particularly if they were Windows clients.
Patti Clark
Linux System Administrator
R&D Systems Support Oak Ridge National Laboratory
On 9/3/15,
On 2015-09-03 18:16, Jeffrey R. Lang wrote:
> 03-Sep 15:07 bkupsvr2-sd JobId 12570: Writing spooled data to Volume.
> Despooling 322,122,610,512 bytes ...
> 03-Sep 15:23 mmcnsd4-fd JobId 12570: Error: bsock.c:429 Write error sending
> 253977 bytes to Storage daemon:bkupsvr2.gg.uwyo.edu:9103: ERR
First let me say thanks to Kern and all those that have helped make
bacula a great tool.
My current backup environment currently consists of a server, VTL and a
tape library connected by a 10GiG network. Bacula currently at 5.2.13.
I plan on upgrading once I've integrated the tape library and th
