Amanda-Users

Re: amdump frozen

2006-08-25 11:43:12
Subject: Re: amdump frozen
From: Frank Smith <fsmith AT hoovers DOT com>
To: Jeff Portwine <jdport AT michigandrill DOT com>
Date: Fri, 25 Aug 2006 10:36:08 -0500
Jeff Portwine wrote:
> This morning first thing I looked in my email to see the amanda backup
> report to see how it ran last night there was no report there.    So I
> checked the server and doing a ps showed:
> 
> backup   17511  0.0  0.2  2272 1064 ?        Ss   Aug24   0:00 /bin/sh 
> /usr/local/sbin/amdump DailySet1
> backup   17523  0.0  0.2  2604 1080 ?        S    Aug24   0:00 
> /usr/local/libexec/driver DailySet1
> backup   17525  0.0  0.1  3268 1008 ?        S    Aug24   0:00 taper DailySet1
> backup   17526  0.0  0.1  2592  952 ?        S    Aug24   0:00 dumper0 
> DailySet1
> backup   17527  0.0  0.1  2592  952 ?        S    Aug24   0:00 dumper1 
> DailySet1
> backup   17528  0.0  0.1  2592  952 ?        S    Aug24   0:00 dumper2 
> DailySet1
> backup   17529  0.0  0.1  2592  952 ?        S    Aug24   0:00 dumper3 
> DailySet1
> backup   17530  0.0  0.1  2592  952 ?        S    Aug24   0:00 dumper4 
> DailySet1
> backup   17532  0.0  0.2  3260 1108 ?        S    Aug24   0:00 taper DailySet1
> backup   17542  0.0  0.0     0    0 ?        Z    Aug24   0:00 [chunker] 
> <defunct>
> 
> It's been stuck like this since I don't know what time last night.  
> If I kill off these processes, what will Amanda do the next time it runs?
> Will it try again with the current tape, overwriting whatever it managed
> to get on the holding disk before it froze last night?    I'm not really
> sure what (if anything) got backed up last night or how I should proceed.
> 
> Thanks for any suggestions,
> Jeff
> 
You can kill all the processes and then run amcleanup.  If you have
dumps in the holdingdisk then you can run amflush to write them to
tape (or if you have autoflush enabled in your config they will get
flushed on the next run).  On your next run amanda will use the next
tape, even if nothing actually was written to the one last night.
   Since your taper process is hung, I suspect either it was in the
middle of a direct to tape dump of a client that went away, or you
have some disk or tape I/O errors (SCSI bus hang, etc.) that might
need to be checked out.

Frank


-- 
Frank Smith                                      fsmith AT hoovers DOT com
Sr. Systems Administrator                       Voice: 512-374-4673
Hoover's Online                                   Fax: 512-374-4501

<Prev in Thread] Current Thread [Next in Thread>