Hi,

I'm sorry, but you are wrong, duplex mismatch Does cause the speed to drop to 
Aboutaleb 5K/s. I've Deen Thissen on numerous occasions. 

-- 

Gr., Remco

On 7 sep. 2010, at 08:02, Niklas Lundström <niklas.lundstrom AT SWEDBANK DOT 
SE> wrote:

> I actually restored the files to my workstation, and the network settings are 
> fine
> Duplex mismatch does not cause the speed to go down to modem-speed from 
> 1995....
> 
> 
> -----Ursprungligt meddelande-----
> Från: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] För Remco 
> Post
> Skickat: den 7 september 2010 07:40
> Till: ADSM-L AT VM.MARIST DOT EDU
> Ämne: Re: [ADSM-L] 50Mb restored in 4.18h....
> 
> On 7 sep 2010, at 07:02, Niklas Lundström wrote:
> 
>> Hello
>> 
>> I just did a restore of 50Mb and it took 4h 18min
>> If it had been 50Gb I wouldn't complain
>> 
>> Total number of objects restored:       114
>> Total number of objects failed:           0
>> Total number of bytes transferred:   50.99 MB
>> Data transfer time:                9,426.15 sec
>> Network data transfer rate:            5.53 KB/sec   <--------------
>> Aggregate data transfer rate:          3.36 KB/sec
>> Elapsed processing time:           04:18:55
>> 
>> The server has a lot of files,  almost 7 million including the copypool. The 
>> TSM DB is really big, 180Gb and 94% full.
>> TSM Server 5.5.4.
>> 
>> Does anyone have a clue of why the restore took so long?
>> 
> 
> your network sucks? (to put it mildly :) ) I'd check to see if there is any 
> mismatch in duplex settings anywhere. Remember, auto-negotiation on the host, 
> and a fixed 100 full-duplex setting on the switch will lead to a host at 
> half-duplex and tons of collisions.
> 
> 
>> It found what volumes to mount fast, but then the client was "Waiting for 
>> files from the server....."
>> 
>> People here are complaining about TSM and that the restores takes long time
>> and it's hard to defend it when the restore takes so long...
>> 
> 
> -- 
> 
> Met vriendelijke groeten/Kind regards,
> 
> Remco Post