Please try these tweaks if you want to, and let us know your results below.
joergr wrote:It depends and differs from system to system. what you need to know is that microsoft (i guess since vista and server 2008) adjusts the tcp window scaling dynamically with tcp autotuning feature. where this is mostly a good one it can become a bad one on some systems. ive explicitly seen very bad experience with especially high-performance access and rdp access. to get rid of this autotuning feature you have to manually disable it:
netsh, interface, tcp, set global autotuninglevel=disable
but then again, sometimes you may want to only set it to highlyrestricted. and again sometimes you may want to set it even more aggressive than microsoft does per default. as i said before, it depends on your system, your nic, your driver, your switches & cabling. You have to find an ideal solution for your special environment.
See the screenshot below for results with tweaks applied. Please keep in mind that with such storage throughtput, you will need to have a very modern 4-8 core CPU on your backup server, otherwise CPU will be your primary performance bottleneck with the default compression level. Check your CPU load during backup!joergr wrote:...and, for heavens sake, if you use Equallogic storage, PLEASE enable flow control on your switches and PLEASE use good ones (for example the dell 6248 is a very good switch for doing great stuff with equallogic).