On Mon, 13 May 2002, jmurray wrote: > Ok, I figured out the permissions problem that was preventing amcheck from > working, as per below. > amcheck now finishes with no errors. > > When I run amdump, "top" on the client shows gtar working away, so it data > compression seems to be happening. amdump finishes with no errors, but in > the report email, I get: > > > These dumps were to tape daily001. > > The next tape Amanda expects to use is: daily001. > > > > FAILURE AND STRANGE DUMP SUMMARY: > > client.agic. /usr lev 0 FAILED [Request to client.agic.ne.jp timed out.] > > ... > > Can anyone help me end this nightmare? > > Shawn
Check the files in /tmp/amanda for the date in question. Better yet, remove /tmp/amanda, run a dump and scrutinize the files created. Could be the estimation timing out due to large partition, slow machine, short 'etimeout', low 'netusage', or a combination of these. Estimation timeout is one of the rare situations where, in my opinion, Amanda does not make the error visible. I notice that you use a single tape. It would make things easier for all of us if you use a somewhat more realistic setup. For example: dumpcycle 1 week # a full dump every week runspercycle 5 # backup weekdays only tapecycle 8 tapes # three extra tapes Or, if you're really short of tapes: dumpcycle 2 days # a full dump every other day runspercycle 2 # backup every day tapecycle 3 tapes # one extra tape -- Ulrik Sandberg
