[SunHELP] FW: tar copy/extract redirected over ssh, still nee d help

That's about 700 KBytes/sec...  Standard 10/100 should max out at about
10000 KBytes/sec.

ssh transfers have CPU overhead because of the crypto stuff but this seems
extreme.  You might want to check your switch & hme ports to see if you're
truly at 100fdx (see the "ndd" command).  Some switch vendors don't
auto-negotiate well and the ports have to be forced up.

Another check would be to ftp and see if the speed jumps.

Another check, if allowed by your scp version, would be to scp the file with
the "-c none" flag, which says "no crypto", and see if the speed jumps again
- it takes the load off the CPU's.

Finally, can you dual-connect your clariion temporarily?  Maybe you can get
the disks seen on the other host.

-M

-----Original Message-----
From: Markham, Richard [mailto:RMarkham at hafeleamericas.com]
Sent: Wednesday, September 25, 2002 7:45 PM
To: 'sunhelp at sunhelp.org'
Subject: RE: [SunHELP] FW: tar copy/extract redirected over ssh, still
nee d help


I resolved my issue due to using ' instead of ". Thanks Mark, Chris.
I have one last question whilst I burn up my welcome.  I transfered
files to another box over a 100mbit switched environment both boxes are 
E420R's and the source has disks on a EMC CLARIION.  It took 1 Hour
and 13 Minutes to transfer 3gb.  The issue I have is the amount of 
data I have to transfer is about 50gb total.  So I'm looking at 15-17 
hours to transfer what will copy locally to new directories in less 
than 4 hours.  Am I faced with a hard fact of life or is there light 
out there in another transfer method?  I am not certain that the ssh
connection is slowing the tar/transfer process.  TIA for any insight
from those of you with more experience in this area.
_______________________________________________
SunHELP maillist  -  SunHELP at sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp