Hello Patti,
Please see below ...
On 05/06/2016 03:46 PM, Clark, Patti wrote:
> No and no. I also don’t perform updates on my backup servers willy nilly.
>
> There are bugs in bacula regarding the "Null Volume name” error. I have
> fewer contention issues with jobs requesting the same volume
No and no. I also don’t perform updates on my backup servers willy nilly.
There are bugs in bacula regarding the "Null Volume name” error. I have fewer
contention issues with jobs requesting the same volume on different devices
with some of the latest BEE versions. I expect that some of
If this ever happens to anyone else, see if either/both of these happened
during one of the volume writes:
1. The disk which bacula uses for its logs became full
2. Someone did an apt-get update/dnf update or whatever during the backup.
1. Definitley just hit us so we had to start the whole job
> Thanks!
>
> device {
>Maximum Changer Wait = 3d
> }
>
> Hey that's interesting ... never heard of it before - do you think it will fix
> my problem? I can set it to 30 days for this job
Welcome back, Bill: there is not much research material about this askdir.c:373
error. It's clear
Thanks!
device {
Maximum Changer Wait = 3d
}
Hey that's interesting ... never heard of it before - do you think it will fix
my problem? I can set it to 30 days for this job
+--
|This was sent by bill.dam...@yahoo.com
> Every time, it gets to about tape 10 or 11 in the set and the backup fails
> with
> this. Any clues what I can do to fix it please?
> 13-Apr 02:41 tiger-sd JobId 6763: Fatal error: Too many tries: Wrong Volume
> mounted on tape device "HP-ULTRIUM-LTO3-EXT2" (/dev/st1): Wanted
> 001-014-58
Fatal error: askdir.c:373 NULL Volume name. This shouldn't happen!!!
Every time, it gets to about tape 10 or 11 in the set and the backup fails with
this. Any clues what I can do to fix it please?
13-Apr 02:41 tiger-sd JobId 6763: Fatal error: Too many tries: Wrong Volume
mounted on tape
