Thanks very much John. The amadmin command helped out a lot. I found that the one client that I was testing was still set to comp-user-tar. Changing these to comp-root-tar fixed it for me. Sorry for wasting your time. My eyes saw what they wanted to in disklist I guess.
It is working very well now. The clients are down to about 10% CPU usage combined between gtar and sendbackup now. One user with an old OSF/1 machine is very happy that I'm not chewing up as much CPU saving his data. Thanks very much for your help. I'll remember to search further in man amanda too! Steve _____________________________________________________________ Steve Cousins Email: [EMAIL PROTECTED] Research Associate Phone: (207) 581-4302 Ocean Modeling Group School of Marine Sciences 208 Libby Hall University of Maine Orono, Maine 04469 On Wed, 27 Mar 2002, John R. Jackson wrote: > >I am trying to get Amanda clients to not do copression, but have the > >server do the compression. I had thought that this would happen by > >changing the dumptype record for comp-root-tar to have: > > > > compress server fast > > > >instead of > > > > compress client fast > > That should have done it, assuming your disklist told Amanda to use > "comp-root-tar" as the dumptype, or inherited comp-root-tar and did > not override the setting. > > >When I watch the clients (Linux, OSF/1) with "top" I see gzip max out the > >processor on the client still. ... > > Try this on the server: > > amadmin <config> disklist <client> <disk> > > That will give you a listing of the various dumptype options. You > should see something like this: > > compress SERVER FAST > > If you still see: > > compress CLIENT FAST > > then you're probably not getting the dumptype you think you are. > > >I've looked around as best as I can but I > >can't find documentation on the dumptype fields other than in amanda.conf. > > They are all in the amanda(8) man page. > > >Steve > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
