Jeff,

If you do end up killing the processes, you will have to run amcleanup CONFIG, 
this will spit out your email and print
the tape label(s) for you.  Amanda will not overwrite the tape.

good luck
Jim



---------- Original Message -----------
From: "Jeff Portwine" <jdport AT michigandrill DOT com>
To: <amanda-users AT amanda DOT org>
Sent: Fri, 25 Aug 2006 11:09:24 -0400
Subject: amdump frozen

> 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
------- End of Original Message -------