Lync 2013 Upgrade

Question

At the moment we have 2 sites each with one Lync 2010 server. We don't have any edge server and don't plan to have any as we won't be federating with any external companies nor want to have
the ability to access the Lync from internet.
Can you suggest the Lync 2013 design for High availability and Site resilience. Both should be automatic and shouldn't need any administrator intervention. Also the best pratice in regards to
splitting the roles.
Malli Boppe MCITP Enterprise Messaging Exchange 2010

Answer 1

Very simply, if you want high availability, in each site you'll need three (three is the recommended minimum due to Lync 2013 quorum design) front end servers with the HTTPS services load balanced using a hardware load balancer.  For back
end high availability, each pool should be mirrored SQL 2012 servers, two in each site.  These two pools will then be paired for site resiliency.  The site failover is not automatic, you will need to invoke the failover with a PowerShell command
invoke-cspoolfailover (http://technet.microsoft.com/en-us/library/jj205189.aspx).   The failure of a single server in a site otherwise and the reconnection of any clients would
be automatic.
I trust that if you're running each site on one server now, then those three should be enough.  For role splitting, it depends on what features you want.  If you want to share PowerPoints, you'll want to split off the Office Web Application role,
if you want HA, then you'll want multiples for the organization in a farm.  If you're running Enterprise Voice, it's up to you to collocate the mediation role, however I prefer to split it off for ease of troubleshooting. 
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications