[prev in list] [next in list] [prev in thread] [next in thread]
List: amanda-users
Subject: Re: amdump frozen
From: Jon LaBadie <jon () jgcomp ! com>
Date: 2006-08-25 15:36:08
Message-ID: 20060825153608.GA8561 () butch ! jgcomp ! com
[Download RAW message or body]
On Fri, Aug 25, 2006 at 11:09:24AM -0400, 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.
amstatus may give you an idea of what succeeded before you kill stuff.
after amcleanup, you can run amreport and get the normal daily email.
--
Jon H. LaBadie jon@jgcomp.com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic