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 device
yes, of course
this is config of fd and sd on storage server
bacula-fd.conf
FileDaemon { # this is me
Name = arkive03.tumo.lab-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run/bacula
Maximum Concurrent Jobs = 20
FDAddress = 10
Hi
I have to build a rpm for the bacula-fd 5.2 in Cent OS 6, and follow
this page :
http://www.bacula.org/5.2.x-manuals/en/utility/utility/Bacula_RPM_Packaging_FAQ.html
I downloaded and extracted the bacula-5.2.13.tar.gz file, then :
Looked at the bacula.spec.in file in "platforms/rpms/redhat/ba
Hi Norbert,
I'm the Bacula mantainer for Fedora. can you use the rebuild I do of
current packages for RHEL/CentOS and Fedora? You can upgrade directly from
CentOS/RHEL packages straight to them.
They have all features enabled. Please read the included README file in
bacula-common.
Bacula 5.2: htt
Hello Alexander
You need to set "Maximum Concurrent Jobs" in these directives below:
= Server side =
## bacula-dir.conf ##
Director, Storage, Client
## bacula-sd.conf ##
Device, Storage
## bacula-fd.conf ##
FileDaemon
= Client side =
## bacula-fd.conf ##
FileDaemon
You are u
> 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
If I have a situation like the attached file, can someone help me
understand which comes first, between the "Client Run Before Job"
script, and the "File = "\\ 13-Apr 09:24 zhomebackup2-fd JobId 59114: Fatal error: Cannot open
> FileSet input file: /etc/bacula/zhome_jobfile_lists/zhome_list_l.
> ER
For various reasons I've ended up with a large number of tapes that only
have a few GB on them (tape drive issues caused by a contaminated
tape(*)) and this is burning up pool spares.
I want to migrate the files on those tapes to newer tapes within the
same pool, then recyle the original tapes
- Original Message -
> From: "Alan Brown"
> To: "Bacula Users"
> Sent: Wednesday, April 13, 2016 1:28:39 PM
> Subject: [Bacula-users] tape migration (within a pool)
> For various reasons I've ended up with a large number of tapes that only
> have a few GB on them (tape drive issues cau
> If I have a situation like the attached file, can someone help me
> understand which comes first, between the "Client Run Before Job"
> script, and the "File = "\\
> The reason is this. This situation is a little complicated, but the
> short answer is that the "Client Run Before Job" script, wi
> On 13/04/16 17:43, Heitor Faria wrote:
>> Not the entire JobID, just the parts which are on the tapes in question.
>>
>> Does anyone have a recipe for this?
>> Hello, Alan. Migrate and copy jobs support a Selection Type = Volume, that
>> combines with the Selection Pattern directive, that receiv
Unfortunately, there's some sensitive info in the script. I'll see if I
can post an excerpt later.
But here's what I've observed:
- When the file doesn't exist, I get the error as described. I've even
attached to the bacula-fd using strace, and verified that it does try to
open() that file, but
> Unfortunately, there's some sensitive info in the script. I'll see if I
> can post an excerpt later.
>
> But here's what I've observed:
> - When the file doesn't exist, I get the error as described. I've even
> attached to the bacula-fd using strace, and verified that it does try to
> open() t
Heitor,
I don't know if this will affect anything, but your example backs up the
file "/tmp/dummy". What I'm trying to do is read from a file, to get
the list of files to be backed up. It's a difference between this syntax:
> File = /tmp/dummy
And something more like this:
> File = "\
> Heitor,
>
> I don't know if this will affect anything, but your example backs up the
> file "/tmp/dummy". What I'm trying to do is read from a file, to get
> the list of files to be backed up. It's a difference between this syntax:
>
>> File = /tmp/dummy
>
> And something more like this
Just in time: I tested and it works.
# bacula-dir.conf
FileSet {
Name = "Full Set"
Include {
Options {
signature = MD5
}
File = "\\|/tmp/list.sh"
}
}
# /tmp/list.sh
ls /tmp/dummy*
*list files jobid=8
+--+
| Filename |
+--+
| /tmp/dummy1 |
| /tmp/dummy2 |
Ah. That's good to know. I'd wondered if there was something like
that. I like it, since it consolidates the two steps (pre-job
processing, and reading the list of paths) down to 1 script, as well as
avoiding writing to a temporary file.
I need to finish vetting this tomorrow, but preliminarily
17 matches
Mail list logo
