On Wed, Aug 15, 2007 at 07:57:32PM -0700, fedora wrote:
> > In "normal" failure modes, this should be taken care of.  Can you give
> > some detail on the type of failure that's triggering this?
> > 
> > Also, amcleanup should function as a second line of defense for killing
> > such processes.
> 
> Here is the error in mail report:
> FAILED [data timeout]
> FAILED [cannot read header: got 0 instead of 32768]
> FAILED [too many dumper retry: "[request failed: timeout waiting for ACK]"]

It looks like you have a communication problem.  What auth are you using
for that client?  This is, unfortunately, not the sort of error that
amcheck will pick up on.  It's usually caused by bad firewall settings.

> Here is my cronjob:
> 0 21 * * * /usr/local/sbin/amcleanup DailySet1
> 10 21 * * * /usr/local/sbin/amcheck DailySet1
> 30 21 * * * /usr/local/sbin/amdump DailySet1
> 
> I put amcleanup before amcheck and amdump. Was it a proper sequences?

No -- you shouldn't need to run amcleanup regularly, but only when a
failure occurs.

Also, running amcheck 20 minutes before your dump doesn't give you much
time to fix anything.  Most people run amcheck in the late afternoon --
after any tape swapping is done, but with enough time to correct any
errors before heading home for dinner.

Dustin

-- 
        Dustin J. Mitchell
        Storage Software Engineer, Zmanda, Inc.
        http://www.zmanda.com/