Hi
Here are some tips, I hope you try them out and please do inform us on the post trial performance
NIC�s
� 10Mb/sec is 1.25MB/sec (8 bits in a byte) which translates to 4.4GB/hour transfer (IEEE 802.3i)
� 100Mb/sec is 44GB/hour (IEEE 802.3u)
� 1000Mb/sec is 440GB/hour (IEEE 802.3ab which is Ether and not fibre)
� TCP/IP has overhead so the actual transfer is typically around 50-60% efficiency. If your NIC�s support it, set the checksum offload to Tx/Rx so that the NIC handles the CRC calculations instead of the CPU. This does reduce CPU overhead and improves backup speed marginally.
� Set the correct Max Transfer Unit (MTU) size � To calculate �ping server -f -l
� To calculate the best Receive Window size (RWIN), calculate your MTU and then ping the server and insert the results into:
Bandwidth(KBPS) / 8 * Average Latency(MiliSec) = RWIN Size(Bytes). Round the result up so that it is exactly divisible by your Maximum Segment Size (MSS). If MTU is 1500 then MSS is 1460 (40k overhead).
Duplexing
� Half-Duplex is one way comunication, one person talks the other listens� Only one side can talk at a time
� Full-Duplex is sametime communication, if teo people are talking then they can both talk and listen at the sametime.
The debate on this issue is never ending.
You cna try out 100 Mbps with FULL DUPLEX on both the box and the switch side.
Using auto negotiate may sometimes result into network communication issues.
Chiao Come Va
Ankur Kumar