In the message dated: Fri, 07 Sep 2012 01:15:53 -0000,
The pithy ruminations from Chris Ord on
<[Bacula-users] bacula possibly confused about label> were:
=> Dears,
=>
=> In the middle of a backup job bacula is asking for a tape it has labeled and
is registered corre
=> ctly(I believe) in the database.
=>
=> Here's the relevant info
=> Status gives me this:
=>
=> Running Jobs:
=> Writing: Incremental Backup job DailyArchive2 JobId=182 Volume="VARCD003"
=> pool="ArcD" device="Drive_0" (/dev/nst0)
=> spooling=0 despooling=0 despool_wait=0
=> Files=0 Bytes=0 Bytes/sec=0
=> FDReadSeqNo=6 in_msg=6 out_msg=4 fd=5
=> ====
=>
=> Device status:
=> Autochanger "Changer01" with devices:
=> "Drive_0" (/dev/nst0)
=> Device "FileStorage" (/tmp) is not open.
=> Device "Drive_0" (/dev/nst0) open but no Bacula volume is currently mounted.
=> Device is BLOCKED waiting for mount of volume "VARCD003",
=> Pool: ArcD
=> Media type: LTO5
=> Slot 4 is loaded in drive 0.
=> Total Bytes Read=0 Blocks Read=0 Bytes/block=0
=> Positioned at File=0 Block=0
=> ====
That sounds like exactly the problem that I reported:
http://old.nabble.com/critical-error----tape-labels-get-corrupted%2C-previous-backups-unreadable-td33192066.html
Bacula is able to instruct the tape library to load media, based on the
physical barcode label, but if the logical label written to the tape becomes
corrupt, bacula cannot use the tape.
My work-around when this occurs (too often!) is to change the volume status to
"Disabled" (in bconsole):
volume=VARCD003 volstatus=Disabled
This causes bacula to choose a different tape.
=> Used Volume status:
=> VARCD003 on device "Drive_0" (/dev/nst0)
=> Reader=0 writers=0 devres=1 volinuse=0
=>
=> List Volumes gives me this:
=>
=> 146 | VARCD003 | Append | 1 | 1,040,640,685,056 | 1,061 |
315,360,000 | 0 |
=> 4 | 1 | LTO5 | 2012-08-14 03:58:04 |
=>
=> So it's loaded,
=> it's used the tape,
=> it's marked appendable
=>
=> yet bacula doesn't see it.
=> I can't relabel the tape without removing the MediaId from the catalog and I
am concerned about
=> wiping the job/data as it is a duplicate backup job and I don't want the
labelling to go out of
=> sequence.
Valid concerns.
Once all backups are finished, you can stop the storage daemon and then use
"btape" (the "readlabel" command) to see if the tape has a valid logical
label.
Mark
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
