John,
Apparently I confused every one with my explanations.
Of course I run amcheck BEFORE amdump, but that also means that amcheck is
run after the "previous" amdump ....
And the output of the amcheck on tape DailySet109 was just to prove that the
tape does have a valid label!
The problem occurs when I do put the valid tape in for the next run and
amcheck is run, it then compains that the inserted tape isn't an amanda tape
and if I check the first block using dd it does seem like if the tape was
blank ...
Does this make things clearer
Pat.
"John R. Jackson" wrote:
> >I have this constant recurrant error, that every day the amcheck is
> >failing just after a succesfull amdump.
>
> I don't understand. Do you really mean you're running amcheck **after**
> you run amdump? Why? Usually it's run **before** amdump so any problems
> it finds can be fixed before the run.
>
> >for instance the day before tape "DailySet109" is dued I run amcheck and
> >get the following:
> >Amanda Tape Server Host Check
> >-----------------------------
> >Holding disk /amanda2/amanda/work: 985386 KB disk space available,
> >that's plenty
> >ERROR: cannot overwrite active tape DailySet109
> > (expecting tape DailySet108 or a new tape)
>
> This says that even though *you* thought DailySet109 was the next tape
> to be used, Amanda thinks the next tape should be DailySet108 and that
> DailySet109 is still active.
>
> It sounds to me like your tape sequence is confused, or you are not
> getting the right (from Amanda's point of view :-) tape mounted at the
> right time.
>
> How are you deciding what tape to mount?
>
> What happens if you run "amadmin <config> tape"? Does it show the tape
> you expect to be used next (I guarantee it is showing the tape Amanda
> expects to see next)? If you mount that tape, is amcheck happy?
>
> >Pat.
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
