>Is that tapecycle < 'reuse' lines? Or tapecycle <= 'reuse' lines?
The number of "reuse" tapelist lines should equal the tapecycle value.
If there are less lines than tapecycle, Amanda will want new tapes
until it gets enough in the tapelist.
But that's not what's happening to you. You actually have **more**
tapelist entries than your tapecycle. I'm almost positive that in this
(unusual) situation, Amanda will do what it usually does and insist on
using the oldest tape, which would be 1283-000111.
But amcheck was not quite ready for this situation and it stopped looking
after it had scanned "tapecycle" (5) tapes. Had it gone a couple more
(or looked at all marked "reuse"), or if you had run it again, things
would have gone OK.
So my suggestion would be to get your tapelist in sync with tapecycle
either by marking some more tapes no-reuse or hand editing it to throw
some away. Or you can make sure the oldest tape to be used next is
within tapecycle of whatever is current in the changer.
I've taken a note to look into amcheck vs. tapecycle vs. "too many"
tapes in tapelist.
>I seem to have a problem related to <Date> field in the tapelist file. I
>can't establish a rule which relates the date to the tapecycle or dumpcycle
>yet ...
The date field is simply the date that amdump/amflush was run and used
the particular tape. It doesn't relate to dumpcycle. It sort of relates
to tapecycle, especially if runtapes is 1 and you run a backup every day.
>Tony Traylor.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
