>All was working well, but since a few weeks my weekly configuration is
>trying to do a level 2 backup of the disk /usr2. ...
Others are reporting problems with "strategy noinc". I'd need to see
the amdump.<nn> file that went along with Amanda doing something other
than a level 0.
>Last week i forced a full backup of
>this disk via
>amadmin, but the last backup failed again with
>
>FAILURE AND STRANGE DUMP SUMMARY:
> gretel /usr2 lev 0 FAILED [can't switch to incremental dump]
Again, I'd need to see the amdump.<nn> file. As a guess, you might be
out of holding disk space. That would cause Amanda to fail to do the
full dump and also not switch to an incremental (either because of the
"force" or "strategy noinc"). Or it could be something else.
It might also be useful to grep for /usr2 in the log.<YYYYMMDD>.<nn>
file and see whether any other messages were present, but amreport just
didn't display them.
>I have nothing changed on the Amanda server, in the configurations or
>something else. So why is Amanda trying to do incrementals since a
>few weeks?
What makes you think it's trying to do incrementals? I didn't see any
evidence of that in the report you sent.
The "can't switch to incremental dump" message doesn't mean it tried to
do an incremental. It means it couldn't do a full and while it normally
would have tried an incremental, something prevented that.
I agree there should be more messages about why it failed.
>Jens Krause
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
P.S. You might take a look at columnspec in amanda.conf. It would
clean up the Amanda reports so the columns don't run together.
