I have bacula set up to create formatted labels which include the
client name and job name, such that a typical label will look like:
Daily-tux2-fd-2010_05_20-03_05-Tux2
where tux2 is the name of the client.
I also set Max Volume Jobs = 1 for each volume, so it is only ever
used once, and never recycled.
At the moment, the machine tux2 is often shut down, due to an
intermittent (probably hardware or overheating) problem that I
haven't yet got to the bottom of.
When bacula comes to back up the machine when it is shut down, I get
the following log:
20-May 03:05 bacula-dir JobId 5168: Prior failed job found in
catalog. Upgrading to Full.
20-May 03:05 bacula-dir JobId 5168: Start Backup JobId 5168,
Job=Tux2.2010-05-20_03.05.00_47
20-May 03:05 bacula-dir JobId 5168: Created new Volume
"Daily-tux2-fd-2010_05_20-03_05-Tux2" in
catalog.
20-May 03:05 bacula-dir JobId 5168: Using Device "FileStorage"
20-May 03:08 bacula-dir JobId 5168: Error: getmsg.c:191 Malformed
message:
20-May 03:08 bacula-dir JobId 5168: Fatal error: No Job status
returned from FD.
20-May 03:05 bacula-dir JobId 5168: Warning: bsock.c:129 Could not
connect to Client: tux2-fd on
tux2.floof.bob:9102. ERR=No route to host
and the client is correctly not backed up. Note however that it
__has__ created and labelled a volume, using the client name tux2.
Now the next backup is started, for a client called "jewel". Because
the failed tux2 backup created a volume, this backup now uses the
confusingly named volume already created but not used:
20-May 03:08 bacula-dir JobId 5169: Start Backup JobId 5169,
Job=Jewel.2010-05-20_03.05.00_48
20-May 03:08 bacula-dir JobId 5169: Using Device "FileStorage"
20-May 03:08 bacula-sd JobId 5169: Labeled new Volume
"Daily-tux2-fd-2010_05_20-03_05-Tux2" on
device "FileStorage" (/backup/jewel/bacula).
20-May 03:08 bacula-sd JobId 5169: Wrote label to prelabeled Volume
"Daily-tux2-fd-2010_05_20-03_05-Tux2" on device "FileStorage"
(/backup/jewel/bacula)
20-May 03:08 bacula-dir JobId 5169: Max Volume jobs exceeded.
Marking Volume
"Daily-tux2-fd-2010_05_20-03_05-Tux2" as Used.
Would it make more sense to only create and label a volume once we
know the client is ready to be backed up?
Or alternatively, mark the volume as used when the backup fails,
since I have Max Volume Jobs = 1?
I appreciate that this is something of a corner case!
I also appreciate, before someone else point it out, that using
labels with dates in them etc is not a good idea due to recycling
files, but these files are not recycled, and only used once each, so
there is no future confusion built in, so don't bother pointing that
one out to me!! :-)
Thanks!
--
Mike Holden
http://www.by-ang.com - the place to shop
for all manner of hand crafted items,
including Jewellery, Greetings Cards and Gifts
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
