>
> *FD Connect Timeout = time*
> where time is the time that the Director should continue attempting to
> contact the File daemon to start a job, and after which the Director will
> cancel the job. The default is 30 minutes.
> *SD Connect Timeout = time*
> where time is the time that the Director
Thanks Kern. Now I will sleep much better ;-)
Peter
On 2018-01-31 11:26, Kern Sibbald wrote:
The network status command does not exist on older File daemons, which
is what the 2 Invalid command means.
Yes, you are right. New features don't work on older software.
Best regards,
Kern
Thanks for your answer Kern,
I adjusted the parameters and still did not work. Spanning tree settings of
the switches where the bacula server and xenserver are connected can affect
this way?
On Wed, Jan 31, 2018 at 8:29 AM, Kern Sibbald wrote:
> In general, it is not necessary to set the keep a
On 31 January 2018 at 10:26, Alan Brown wrote:
> On 31/01/18 10:14, Ben Laurie wrote:
> > I also have that on my LTO3 drive.
>
> You should test this using the fill command in btape (which will test
> with uncompressible data). if the block size is set correctly you're
> going to achieve very clo
In general, it is not necessary to set the keep alive time or the
heartbeat to 1 minute. That causes unnecessary network usage.
Setting them to 300 seconds (5 mins) should be sufficient in
virtually all cases.
On 30.01.2018 21:44, Elias Pereira
wro
On 31/01/18 10:14, Ben Laurie wrote:
> I also have that on my LTO3 drive.
You should test this using the fill command in btape (which will test
with uncompressible data). if the block size is set correctly you're
going to achieve very close to the published throughput.
Please note that 250MB/s fo
The network status command does not exist on older File daemons,
which is what the 2 Invalid command means.
Yes, you are right. New features don't work on older software.
Best regards,
Kern
On 30.01.2018 12:08, Peter Milesson
wrote:
Since updating from Bacula 7 to 9.0.2 we are not getting emails when an
intervention is required, i.e required tape not available in the library. We
get all the other notifications when a job finishes. Is this a bug or a
mis-configuration?
Regards,
Chris Sluman
---
I also have that on my LTO3 drive.
On 21 December 2017 at 23:08, Dan Langille wrote:
> Hello,
>
> I'm using Bacula 7.4.7 on FreeBSD 11
>
> What Bytes/block are you using for your LTO4 tapes?
>
> I ask because I just noticed:
>
> ###
> Device tape is "LTO_0" (/dev/nsa0) mounted with:
> Volum
Hello,
As the error message says the Aligned-Disk cannot be opened or
does not exist. What it doesn't say very clearly is that you do
not have the aligned-driver. This driver has not yet been
released. It will be released in binary form in the next couple
o
Kenneth Garges wrote (2018/01/30):
> I???m having trouble getting a tape library to work.
Hello, try chio status -v or mtx status. Both should return
status of your autochanger including tape labels. If they both
do return an error, do you have correct permissons on /dev/ch*?
I have the following
Dan Langille wrote (2017/12/21):
> Hello,
>
> I'm using Bacula 7.4.7 on FreeBSD 11
>
> What Bytes/block are you using for your LTO4 tapes?
Oops, I waited for the others and now I see that I'm waiting too much :o)
I still do use Maximum Block Size = 65536 and I never had the problem.
The big win
12 matches
Mail list logo
