{"id":271,"date":"2012-11-10T06:25:00","date_gmt":"2012-11-10T06:25:00","guid":{"rendered":"http:\/\/atumvirtwordpress.azurewebsites.net\/?p=271"},"modified":"2012-11-10T06:25:00","modified_gmt":"2012-11-10T06:25:00","slug":"lync-2013-features-topology","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2012\/11\/lync-2013-features-topology\/","title":{"rendered":"Lync 2013 Features – Topology"},"content":{"rendered":"
In designing our Lync 2010 environment, I was a bit beside myself at the scale of the number of required servers to deploy a simple, yet redundant, environment. \u00a0Even cutting a few corners, we ended up with 13 servers for our Lync pilot. \u00a0Using the same design in Lync 2013, the total number of servers is only 9.<\/p>\n
Lync 2013 simplifies the back end database requirements by storing data in the front end servers, one of which acts as a master. \u00a0The remaining front end servers act as backups, and will automatically take over in the event of a failure. \u00a0For this matter, Microsoft suggests deploying a minimum of 3 front end servers for a scaled enterprise deployment.<\/p>\n