The problem is in the changer script, it doesn't use the -otapedev.
The fix is to tell amdump to not use the changer:
amdump ... -o tapedev=/no/such/device -o tpchanger=
Jean-Louis
Gerrit A. Smit -TI- wrote:
We have a tape-robot with tapes to dump on, but sometimes I don't want to dump
to tape directly: the data of some small clients, which are available during the
Monday morning meeting of their users, should be hold, to be flushed to tape as
side-effect of the nightly dumps of the other clients.
Until now I forced this behaviour by making a symbolic link to a changer.conf
with effectively 0 slots available. Not the neatest way to do it, but it worked.
To make things neater, I tried to use the config overwrite option to amdump.
But, saying amdump ... -o tapedev='/dev/null' of amdump ... -o tapedev='null:'
doesn't do the trick: Amanda uses the tapedev from the configfile, and I end up
with a near to empty tape.
Why doesn't amdump do as I tell her, like status in the manpage?
(I didn't look at the sources yet, I only read the manpages)
Gerrit
