At a customer I decided to do some recovery testing.
We use the chg-robot changer there, with one tape drive.
See below:
* tapetype
* changer
* taperscan
* storage
* amrecover_changer
(I could also show the whole config, but don't want to flood the list ...)
Amdumps work fine.
Recovery ... I have questions:
I decided to restore a DLE with a lev1 on one tape and the lev0 on
another tape, to test the whole handling of 2 or more tapes.
That lead to amrecover reading the lev1 tarball from tape 1, and then
hours of waiting ... it never got to the point of requesting tape 2 or
changing it on its own.
I read the manpages etc, and I am unsure if to use "robot" (= changer
name) as tape device in amrecover, or "tape:/dev/nst0" directly.
tested both, no difference
Maybe the tape drive doesn't return some of those EOM/EOT messages?
It's a HP Ultrium 4-SCSI, Rev: B12H ... as far as I remember that worked
before.
Thanks for any hints here.
(ah, for reference: Amanda-3.5.1 on Debian 11.3 right now)
---
here the configs:
define tapetype LTO-4 {
│
comment "Created by amtapetype; compression disabled;
2017-10-31 sgw" │
length 698510208 kbytes
│
filemark 0 kbytes
│
speed 36696 kps
│
blocksize 2 mbytes
│
readblocksize 2 mbytes
│
}
│
│
define changer robot {
│
tpchanger "chg-robot:/dev/sg21" # lsscsi -g
│
property "tape-device" "0=tape:/dev/nst0"
│
property "eject-before-unload" "no"
│
property "use-slots" "1-24"
│
changerfile "/etc/amanda/abt/chg-robot-dev-sg21"
│
}
│
│
define taperscan lexi {
│
comment "none"
│
plugin "lexical"
│
}
│
│
define storage abt {
│
tapepool "abt"
│
tapetype "LTO-4"
│
tpchanger "robot"
│
runtapes 1
│
taperscan "lexi"
│
│
flush-threshold-dumped 300
│
flush-threshold-scheduled 300
│
taperflush 300
│
autoflush yes
│
│
#labelstr "^ABT-[0-9][0-9]*$"
│
autolabel "ABT-%b"
│
}
│
│
reserve 30
│
│
amrecover_changer "robot"
