Are you using the “robot” type changer? See man amanda-changers
define changer LTO5-robot {
tpchanger "chg-robot:/dev/changer” # or “chg-robot:/dev/sgNN”
property "tape-device" "0=tape:/dev/nst0"
changerfile "/usr/local/etc/amanda/LTO5-Robot-state”
…. other settings …..
}
The barcode match-up to tape name gets stored in that changerfile
(whatever name
YOU put there; that’s my file name) and it might not need to actually
mount and scan the tapes each time.
Can you perform the following command?
amtape [config] inventory
If you can’t, then I think you don’t have the barcode-to-tape matchup info
stored anywhere.
more knowledgeable answers may follow from developers….
only a user:
Deb Baddorf
Fermilab
On Apr 2, 2015, at 1:20 PM, Jason L Tibbitts III <[email protected]> wrote:
> I'm running 3.3.6 (but could easily upgrade if it would help). For a
> long time I've been wondering about amanda's behaves when I have a
> tapecycle larger than the number of tapes in my barcode-supporting
> library and all of the tapes in the library have been recently written.
> When the next tape in the cycle isn't in the library, amanda will
> attempt to load and scan every single tape in the library, even though
> it should be able to tell immediately that the tape it wants isn't there
> just by the barcodes. Unfortunately this takes about 70
> minutes. (Tandberg T24 library with 22 occupied slots. My tapecycle is
> 88 tapes.)
>
> So basically if I know it's tape day and I happen to not get to it
> before amcheck runs, I potentially have a 70 minute wait before I can do
> anything, even though all of the necessary information is already
> available. I know amanda can properly talk to the barcode reader
> because it can directly load a tape by barcode. All listings in
> tapelist have the barcode present.
>
> Is this the expected behavior or have I perhaps missed a setting?
>
> - J<
