COMMMethod is set to SHAREDMEM  and has been that way from the start.
I'm got tracing turned on now so we will see if that reveals anything.
Here is the summary of our archive from last night.  Network(FIBER)
throughput seems to be ok but the Aggregate is abysmal.  Compression is
also turned off since we aren't going over ethernet and HW compression
is turned on at the tape drive.  We are backing up ~32000 file, some in
the 50-60G range.

Total number of objects inspected:  158,353
Total number of objects archived:    31,927
Total number of objects updated:          0
Total number of objects rebound:          0
Total number of objects deleted:          0
Total number of objects expired:          0
Total number of objects failed:           2
Total number of bytes transferred:    459.45 GB
Data transfer time:                  927.99 sec
Network data transfer rate:        519,159.18 KB/sec
Aggregate data transfer rate:      8,740.44 KB/sec
Objects compressed by:                    0%
Elapsed processing time:           15:18:40


Gary Galloway
___________________________________________________________
___________________________________________________________
Health Care Information Systems
University of Iowa Hospitals & Clinics

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, March 30, 2005 1:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Archive very, very slow

On Mar 30, 2005, at 2:14 PM, Miller, Ila wrote:

> ...The data is mounted to the TSM server so the TSM server is also the

> client and the data should not be going over the network at all. ...

Just a minor thought: Your COMMMethod is probably TCPIP, meaning that
the I/O would be going through the TCP/IP stack via "localhost". You
might try COMMMethod SHAREDMEM as a more efficient method for that
co-residency situation, and to see if any beneficial impact (which might
point to a TCP/IP issue). Beyond that, all the usual tuning values. And
someone may be able to contribute based upon similar configuration
experience.

    Richard Sims