In my case using spooling didn’t prevent shoe-shining; it just introduced long
pauses while data was spooled. I think all this means is that I can read from
my data sources faster than my tape can write.
So far the only change I made to help with shoe-shining was to set Max File
Size to a
Dan,
I’m new to bacula, and arguably not very smart, but I’ve been struggling with
tape drive performance pretty much since the moment I got the configurations to
a functional state so I’ll share my learnings thus far.
Can you hear your tape drive? If so, do you hear lots of stops and starts
Spool Directory = /usr/local/bacula/spool
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
}
Messages {
Name = Standard
director = Director-Ural = all
}
> On Mar 1, 2016, at 6:34 PM, Cejka Rudolf <c
written to the spool directory (which is ssd) so
maybe the real backups will be faster. We’ll see.
Thanks again,
Simon
> On Mar 1, 2016, at 8:42 AM, Martin Simmons <mar...@lispworks.com> wrote:
>
>>>>>> On Tue, 1 Mar 2016 14:07:55 +0100, Cejka Rudolf said:
>>
Or perhaps a more accurate subject would be "Trouble successfully using
Bacula on FreeBSD"...
I've set up bacula 7.2 on my FreeBSD server using Postgres as the
backend database.
My tape drive info:
mt -f /dev/nsa0 status
Drive: sa0: Serial Number: ##
