Great, thanks John, you had a point with the change in the config file.
It indeed tried to use dump instead of GNU tar..
And indeed, the amcheck returns to be having no problems anymore.
Though, the backup itself fails still.. the next report was in the log file
----------------- <report logfile> --------------------
FAIL dumper cobalt01.somewhere.nl /home 0 [data timeout]
sendbackup: start [cobalt01.somewhere.nl:/home level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
----------------- </report logfile> --------------------
And this while I increased the dtimeout flag to 3600 (one hour).
The data to be processed is no more than approx 160 Mb. which is only a
small amount more than 127Mb which was the last successful backup.
Could it be because of MySQL (b)locking read-access to the tar process?
since MySQL operates under the /home directory? I sure am going to try.. (I
installed it in about the same period..)
I don't think it could be some permission setting, because afaik the backup
is being run as amanda, who has right to read and access the home directory.
And directories it hasn't access to should be skipped, right?
Once again thanks in forward for any help.
PS. the message is in plain text. ;-) I sure thought the html version was
bounced, why I reposted a plain text version of it... strange.
