I am using Amanda 2.4.2p2 with a 96 slot, 4 drive tape library (Sun
StorEdge L3500). My operating system is Red Hat Linux 7.2, although I
doubt it matters.
In the documentation file TAPE.CHANGERS, I read this section:
Now there is another way, to get the chg-scsi a little bit more
flexible. If you use only one digit in the `tapedev' parameter,
the chg-scsi expects that changerfile points to a real
configuration file, not only a counting file.
[etc.]
This sounded like exactly what I want, so I am using it. That is, in
my various amanda.conf files, I have lines like these:
tpchanger "chg-scsi"
tapedev "1"
changerfile "/etc/amanda/chg-scsi.conf"
...and then the real configuration for the tape device appears in some
section of /etc/amanda/chg-scsi.conf. (The particular feature I like
is limiting Amanda to using only certain slots for a configuration. I
would not want Amanda to scan all 96 slots looking for something.)
This works great for doing backups. But today I decided to test a
restoral using amrecover. This failed at "extract", with the
following lines at the tail of the amidxtaped.debug file:
Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "0"
argv[4] = "kingtut"
argv[5] = "^/dev/sda1$"
argv[6] = "20020415"
amrestore: could not open tape 0: No such file or directory
amidxtaped: amrestore terminated normally with status: 2
amidxtaped: could not stat 0
could not stat 0
amidxtaped: pid 2220 finish time Tue Apr 23 14:44:58 2002
The problem here is pretty obvious: amidxtaped is using the tapedev of
"0" as the tape device, instead of the true device specified in the
changerfile as chg-scsi expects.
I am curious whether other people have seen this problem, and if
anyone can suggest a solution.
Thanks!
- Pat
