Organizations can use the Barracuda Load Balancer ADC to enhance the scalability and availability of their Lync Server deployments (formerly known as Microsoft Office Communications Server).
Barracuda Networks has conducted interoperability tests between the Barracuda Load Balancer ADC and Microsoft Lync Server. This guide describes how to deploy the Barracuda Load Balancer ADC to provide scaling in a Lync environment.
For organizations that want a scalable solution, Microsoft recommends using a hardware load balancer to distribute the traffic among multiple Lync Servers.
Product Versions and Prerequisites
You must have:
- Barracuda Load Balancer ADC version 5.1 or 5.2.
- Microsoft® Lync® Server 2010 or 2013 Enterprise Edition.
At least the minimum number of Barracuda Load Balancer ADCs required for your deployment:
Deployment Number of Barracuda Load Balancer ADCs Internal Lync Server Deployment
- Minimum: One Barracuda Load Balancer ADC
- Recommended: Two Barracuda Load Balancer ADCs for high availability
Internal Lync Server Deployment and Edge Deployment
- Minimum: Two Barracuda Load Balancer ADCs.
- Recommended: Four Barracuda Load Balancer ADCs for high availability
To maintain the integrity of the edge security model, separate load balancers are required for the internal traffic and the edge traffic.
Internal Lync Server Deployment, Edge Deployment, and non-collocated A/V Services
- Minimum: Three Barracuda Load Balancer ADCs
- Recommended: Six Barracuda Load Balancer ADCs for high availability
To maintain the integrity of the edge security model, separate load balancers are required for the internal traffic, the edge traffic, and the non-collocated A/V Services.
- Installed your Barracuda Load Balancer ADC(s), connected to the web interface, and activated your subscription(s).
- If you want to deploy Lync Server with high availability, clustered your Barracuda Load Balancer ADCs. For more information, see High Availability.
Support for Office Web Apps Server and Lync Server (for internal users only)
Office Web Apps Server is a new Office server product that delivers browser-based versions of Word, PowerPoint, Excel, and OneNote. A single Office Web Apps server farm can support users who access Office files through SharePoint 2013, Lync Server 2013, Exchange Server 2013, shared folders, and websites.
After the Office Web Apps server and Lync server are integrated, internal users can start sharing PowerPoint presentations without any further changes on the Barracuda Load Balancer ADC.
Refer to the Microsoft TechNet library for the following:
- A description of ports and protocols used by the servers, load balancers, and clients in a Microsoft Lync deployment environment
- Microsoft Lync Server Documentation
- Deploy Office Web Apps Server – http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx
Configuring Integration with Office Web Apps Server and Lync Server 2013 – http://technet.microsoft.com/library/3370ab55-9949-4f32-b88b-5cffed6aaad8
|Front-End Server||A Lync Server in the internal network running the Front End Lync Services.|
|Edge Server||A Lync Server deployed in the perimeter network running the Edge Lync Services.|
|Fully Qualified Domain Name (FQDN)||The unique name for a specific computer or host that can resolve to an IP address, e.g., |
|Service||A combination of a virtual IP (VIP) address and one or more TCP/UDP ports on which the Barracuda Load Balancer ADC listens. Traffic arriving over the specified port(s) to a service is directed to one of the real servers associated with that service.|
Deploying with Microsoft Lync Server
Before you deploy with Microsoft Lync Server, you must understand your deployment options. See Understanding Microsoft Lync Server Deployment Options.
Then see How to Deploy with Microsoft Lync Server 2010 and 2013 for instructions on how to deploy with the Microsoft Lync Server.