Tips » Reducing Data Center Costs » Tip 7 - Optimize Bandwidth Rather than Grow It

Tip 7 - Optimize Bandwidth Rather than Grow It

by Greg Shields

I once worked alongside a brilliant network engineer named Gary Andria. This old friend and coworker of mine was always full of poignant quips of wisdom that still stick with me today.

One in particular I'll always remember had to do with a project to connect two particularly-problematic sites with new bandwidth. Gary told me one day, “Greg, never add bandwidth except as a last resort, because traffic will always grow to fit available bandwidth . If you want to be smart, then figure out ways to better use what you've got.”

Herein lies a situation that plagues many of us who support remote sites, branch offices, satellite locations, and other out-of-the-main-office networks that are invariably connected with not enough bandwidth. Connecting remote offices to the main often happens through MPLS connections through a provider's cloud, with the company non-linearly paying more when more bandwidth is needed.

The problem with the more-isn't-necessarily-better approach is in finding solutions that make economic sense. To make better use of that existing bandwidth, you need to seek smart alternatives for your users:

  • Speed application access with Terminal Services / Remote Desktop Services / Citrix XenServer. Client/server applications work great when clients and servers are well connected. These applications grow problematic, however, when their two halves are separated by long distances and slow network connections. With many business applications today following the client/server model, one solution is to move the client right into the data center with its paired server. Once there, remote application infrastructures such as Remote Desktop Services or Citrix XenServer leverage WAN-optimized protocols to pass screen updates and keyboard/mouse commands with very little bandwidth consumption. Better yet, the traffic flows from these applications are substantially more predictable than with traditional client/server communication. Thus, you can more effectively scale and plan for RDS' RDP or Citrix's ICA traffic patterns. If you're WAN-constrained, consider centralizing the hosting of your applications back into the main office.
  • Speed file downloads with Microsoft BranchCache / Citrix Branch Repeater. Migrating your applications to a remote applications infrastructure eliminates the need for expensive client/server traffic; yet users may still need to access files and folders at the main office. Transferring a file or folder from one location to another must still transfer that entire file over the wire, which consumes an excess of bandwidth and slows the connection for everyone. Get around this problem through site-to-site caching and bandwidth optimization solutions such as Microsoft's BranchCache and Citrix's Branch Repeater. Solutions like these take different approaches to conserving bandwidth, with BranchCache caching documents locally after they've made their first trip across the wire. Branch Repeater uses a collection of technologies to cache, optimize, compress, and otherwise get more out of each long-distance connection.
  • Speed patch installation with distributed WSUS architectures. Solutions such as Microsoft's WSUS create a manageable infrastructure for patching, enabling administrators to choose which patches get deployed and when. But its other utility is in the local caching of patches. Rather than forcing each individual client out to the Internet for its monthly updates, WSUS stores them locally for LAN distribution. What many admins don't recognize is that multiple WSUS servers can be connected together, enabling them to replicate update data between each other. The result is that branch offices can get all their patches from a single source that replicates during off-hours, preserving available bandwidth during the day.
  • Speed technical support with LogMeIn / RapidAssist / WebEx / GoToAssist. Lastly are the tools that IT itself uses to troubleshoot problems without leaving the desk. Many troubleshooting tools can be excessive consumers of bandwidth, with the traffic requirements for “looking over the shoulder” consuming large amounts of your tiny connection. Others, like those mentioned here, are designed specifically with the Internet in mind, using multiple forms of compression and optimization to ensure that troubleshooting connections occur with very little bandwidth.

Obviously, many other solutions exist that help you use what you've got rather than buy anew. No matter what solutions you chose, remember Gary's advice that your users will always figure out ways to consume any available bandwidth once you hand it to them.

Greg Shields is an independent author, instructor, and IT consultant based in Denver, Colorado, and a co-founder of Concentrated Technology. With nearly 15 years of experience in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft systems management, remote application, and virtualization technologies. Greg is a Contributing Editor and Columnist for TechNet Magazine, and is the author of five books, including Windows Server 2008: What’s New / What’s Changed. Greg is also a highly sought-after instructor and speaker, speaking regularly at conferences like TechMentor Events, and producing computer-based training curriculum for CBT Nuggets.  Greg is a recipient of Microsoft "Most Valuable Professional" award with a specialization in Windows Terminal Services.