So Steve sent me this link and it’s an awesome read. It basically describes the optimization of the MAPI used between Microsoft Outlook clients and Exchange servers.
So I ate some mumble pie this morning! In the gig I am doing at the moment, they have deployed Riverbed Steelhead appliances to every remove location they have, with the view that with a centralised Exchange 2010 will work, even with high latency low bandwidth links.
As expected I had my concerns! I moved a couple of hundred mailboxes over the weekend from various Exchange 2003/2010 servers around the world, and checked the Steelheads in the main data centres this morning.
What do you think! The best result was 93% LAN vs WAN data compression which is just amazing! This was actually for BlackBerry connecting to a remote Exchange 2003 server!
For pure Outlook the numbers are impressive. The Steelheads actually “learn” what a user is doing so the compression will only get better. Add to that, the fact that the steelhead will keep an open connection to the CAS Array and pre-fetch any new mail, so the when the user connects to the mailbox in the morning, new mail will be almost instantly delivered!
If you have high latency, low bandwidth links you have to have a look at these as they are amazing! They are actually an RoDC so they can decrypt compress, transmit and re-encrypt the data!
On another point, it is possible for the steelheads to optimise DAG replication traffic! I am going to try this in the lab!
On a downside, they are unable to optimise mailbox move traffic, but I have been told that an update is coming soon that will fix that too!
I am going to put the update in the lab, so will update you on any progress.
#MSExchange #Riverbed #Stringray
The Riverbed Stingray documentation for Exchange Server 2010 has been updated!
PDF states Version 2.7. .. created by Vinay Reddy on Mar 26, 2013 3:44 PM, last modified by Vinay Reddy on Mar 26, 2013 3:44 PM
Can see some updates on page 40 – 41, 43 – 47 and the script on page 60 -61 has a few cookie related updated as is noted as “Updated the TrafficScript for Single Virtual Server for all Exchange services with persistence configuration removed for OAB and AutoDiscover”
Check it out here: https://splash.riverbed.com/docs/DOC-1716 -or- if they delete it ;-) here: https://ucinfo.files.wordpress.com/2013/04/stingray-traffic-manager-solution-guide-microsoft-exchange-2010.pdf