I'd like to second the comments by Hans -- Windows servers can perform well -- assuming the infrastructure is there to support it.
Our TSM server is running 6.2 on a 64-bit Windows 2003 Server. One 1Gb ethernet nic. Our datamover/proxy is running 6.3 client on a Windows 2008 R2 (64-bit) Server. One 1Gb ethernet nic. We are regularly able to stream image backups at 500Mbps (that's megabits-per-second, just to be clear), reading from 4Gb fibre-channel and dumping across a dedicated LAN connection to the TSM server. Sometimes sending for 15-30 seconds at 700-750Mbps, topping out at around 815Mbps. I can run two proxies simultaneously streaming, and the TSM server will be receiving data from multiple image backups at a sustained rate of ~700-750Mbps. Incremental, file-level backups are another story... searching 6 Million files in 4TB and backing up <50GB can take ~2 hours. I would love to see what I can do with 10Gb ethernet, but we're not there yet... Mike On Wed, Feb 12, 2014 at 2:13 PM, Schaub, Steve <steve_sch...@bcbst.com>wrote: > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Hans Christian Riksheim > Sent: Monday, February 10, 2014 9:04 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Exchange 2010 backup performance > > In my experience there is nothing wrong with the TCP stack in Windows. > Especially Windows2008R2 performs very well. For a single stream from a > 2008R2 client (dsm sel <big file of zeroes>) to an AIX TSM-server 500km > away over 10Gig directly to LTO5 has a speed of around 200MB/ at our setup. > Bottleneck being the drive. > > After too much experimenting I have found the critical factor to be to set > TCPWINDOWSIZE 0 at both dsm.opt and dsmserv.opt and increase the tcp-sizes > in AIX(and override the tcp-settings on the NIC). Windows OS can be left > alone as its default is quite OK. YMMV of course. > > Regards, > > Hans Chr. > Best regards, Mike RMD IT, x7942