Note: The reason to use the source switch is that Windows Server 2012 R2 doesn’t install the source files. We can add new features by using the following PowerShell cmdlet:Īdd-WindowsFeature Net-Framework-Core, Failover-Clustering, RSAT-Clustering-Mgmt,RSAT-Clustering-PowerShell -Source d:\sources\sxs Let’s start by installing and configuring the clustering service on both SQL Servers ( SQL01 and SQL02). In this tutorial, we consider a lab environment with one Front End server and two SQL Server 2014 Enterprise Edition servers, which is a new environment without any previous Lync Server/OCS deployments. To deploy AlwaysOn Availability Groups for Skype for Business Server 2015, we need to follow specific steps. Note: AlwaysOn Availability Groups requires SQL Server 2012/2014 Enterprise Edition.įor other supported scenarios, check the following:īack End Server high availability in Skype for Business Server The good news is Skype for Business Server 2015 comes with AlwaysOn Availability Groups: Another supported scenario was to use SQL failover clustering, but in this case we need to manually deploy it:ĭatabase software support in Lync Server 2013
The reason for this was that Topology Builder did all the hard work for us. In Lync Server 2013, it was common to have SQL Server High Availability using SQL Mirroring. In SQL Server 2014 – Database Mirroring (SQL Server) Use AlwaysOn Availability Groups instead. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. This feature will be removed in a future version of Microsoft SQL Server. This was related to the fact that SQL Mirroring was marked as a feature to be removed in future SQL Server versions: In Lync Server 2013, there were requests regarding an alternative to SQL Mirroring for SQL Server High Availability.
0 kommentar(er)
