> FAILED AND STRANGE DUMP DETAILS:
> 
> /--  ind.ayo.com /var/lib/mysql lev 0 STRANGE
> sendbackup: start [ind.ayo.com:/var/lib/mysql level 0]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ...
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> | gtar: ./mysql.sock: socket ignored
> ? gtar: ./mysql/general_log.CSV: file changed as we read it

Means that the file mysql/general_log.CSV was getting modified while
tar was trying to save it. Most probably this file has not been
included (or included wrongly) in your amanda backup.

You have to understand that it takes some amount of time for tar to
make a copy of a *big* file. If that big file is changing often, it is
very likely it will be changing while tar is trying to copy it. There
is very little you can make about it, except stopping mysql while you
are doing th backup :)

Actually, this is only a STRANGE, not a FAIL.

A bit of auto promotion, this page
https://wwws.cs.ait.ac.th/amanda/operator.shtml reccords a number of
Amanda error message and the explanation for it, and possible recovery
action.

Olivier