On Wed, Jun 29, 2005 at 09:57:48AM -0600, Graeme Humphries wrote: > Hi guys, > > I've got my configuration mostly sorted out now, so it's doing what I > want it to. However, I've got a question about some weird behavior I'm > seeing on my AMANDA server. I'm using the srvcompress option because the > servers I'm backing up from are rather slow, and when backing up, I see > the following on the AMANDA server: > > 9675 ? S 0:00 \_ /USR/SBIN/CRON > 9676 ? Ss 0:00 \_ /bin/sh /usr/sbin/amdump weekly > 9685 ? S 0:01 \_ /usr/lib/amanda/driver weekly > 9686 ? S 4:24 \_ taper weekly > 9687 ? S 0:59 | \_ taper weekly > 9699 ? S 9:45 \_ dumper0 weekly > 10629 ? S 96:19 | \_ /bin/gzip --fast > 10630 ? S 0:00 | \_ /bin/gzip --best > 9700 ? S 6:52 \_ dumper1 weekly > 10086 ? S 149:32 | \_ /bin/gzip --fast > 10087 ? S 0:21 | \_ /bin/gzip --best > 9701 ? S 0:00 \_ dumper2 weekly > 9702 ? S 0:00 \_ dumper3 weekly > > Now, why oh why is it doing *two* gzip operations on each set of data!? > It looks like the gzip --best isn't actually getting that much running > time, so is there something going on here that's faking me out, and it > isn't *actually* gzipping everything twice? :)
A dump is two streams, the data being backed up and the index. Each are separately gzipped. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
