>I still think my method is lazier. ;-)
While I'm a **big** fan of being lazy :-), your technique has some issues.
Assuming you have a tapecycle of N and tapelist has N tapes, which would
be the normal situation, as soon as you remove an entry from tapelist,
either by deleting the line, using amrmtape or marking it no-reuse,
Amanda will insist on a new tape for the next run because there are now
N-1 tapes "available".
In addition to the steps in your FAQ item, you would also have to
temporarily reduce tapecycle to match (or be less than) the number of
"reuse" entries in tapelist. Then remember to increase it when you put
the tape back to "reuse" status.
But reducing tapecycle has side effects. For one, it controls the number
of amdump.<nn> and log.YYYYMMDD.<nn> files kept around.
My "hand edit" approach doesn't have these problems but is much more
error prone (and hard to describe, etc).
This whole area of Amanda tape management is seriously icky and needs
to be worked on.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
