SQL AlwaysOn - Skype for Business

Transcription

1 2018 SQL AlwaysOn - Skype for Business DINESH SINGH

2 Contents Before Starting... 2 Windows Failover Clustering... 2 IPs Address and DNS... 2 SQL AlwaysOn... 2 Service Accounts... 2 Network Configuration... 2 Windows Failover Clustering... 3 Installing SQL Server...15 Skype for Business Deployment...20 Configure Skype for Business Databases for SQL AlwaysOn Availability Group...21

3 There are many changes on Skype for Business included high availability such as server pooling, disaster recovery with pool pairing, and several modes of Back End server high availability such as always on availability groups, database mirroring, and SQL fail over clustering. High availability referring to make sure that services are available even one or more servers goes down and disaster recovery means keeping services going in the event of a natural or human caused disaster and preserving as much data from before the disaster as possible. Skype for business server providing the high availability options in Front End as pool pairing as well as high availability options are in Back End servers such as database mirroring, Always On availability groups, SQL fail over clustering, Always On fail over cluster instances (FCI). Worked on a project for Skype for Business deployment with one of mu customer, and want to share my experience through this post. In this post my main focus on configuring the SQL Server AlwaysOn Availability Group for Skype for Business. Before Starting As always we have to go through the prerequisite, following are the recommendation from Microsoft Server requirements for Skype for Business Server 2015 Back End Server high availability in Skype for Business Server Windows Failover Clustering Following are the recommendation for configuration of the Windows Failover Clustering Failover Clustering Hardware Requirements and Storage Options Understanding Requirements for Failover Clusters IPs Address and DNS First of all we need to do ensure that our SQL nodes are configured on the customer LAN and domain joined. SQL AlwaysOn Next we need to decide the IP addressing for the SQL availability group, we need IP address for SQL AlwaysOn Group listener and DNS name for SQL AlwaysOn Group listener. Service Accounts Again we have to follow the best practice to use Active Directory Service Account where possible. Network Configuration First we have to configure the Network for public and private network card on both SQL servers.

4 Windows Failover Clustering Now time to install the Windows Failover Clustering role on servers, we have two option, first you can run the PowerShell command Install-WindowsFeature Failover-Clustering and 2nd option from GUI

5 Once complete we can see the "Failover Cluster Manager" in server tools Now time to create failover cluster, open from console of failover cluster manager

6 Select Create Cluster Click Next on Create Cluster Wizard Brows the both nodes from Active Directory and click on add

7 Next wizard for validating the cluster configuration test before continue, i have selected Yes Now it will start validating the configuration

8 Select "Run all Test" Next wizard ready for test configuration

9 Wizard is running for validating the configuration Here is the validation report for cluster configuration.

10 Next wizard you have to give the Cluster IP address and Cluster Name Next we have to make sure uncheck on "Add all eligible storage to the cluster" and press Next to continue

11 Once Windows Server Failover Cluster now created and we can get the warning regarding Quorum witness, we can ignore now as we will define latter also we can view the report Now we can see all the details from Failover Cluster manager Console

12 Now we have to define the Quorum\Witness folder and permission. Now create the Cluster Quorum from Failover Cluster Manager Quorum cluster configure wizard will give all details, click Next

13 Here we have option to select the Quorum witness next wizard configure the a file share witness

14 Next brows and select the file share witness Once we select the path of the file share witness click on Next

15 Now you can see the Cluster Quorum configuration has been completed and we can view the report also. Now we can see the both nodes are online from Failover Cluster manager console Now we see the completed the installation and configuration of the Windows Failover Cluster,

16 Installing SQL Server Mount SQL server ISO or put DVD and launch the SQL server installation center and select "New SQL Server fail-over cluster installation" SQL Server Setup files will verify the system Setup support rules identify problems

17 Here you need to select "SQL Server Feature Installation" Now we have to select the features Here we have select the instance or default or new instance and Instance root directory we have select Server Configuration and select authentication mode

18 Here is the Installation progress status Installation has been completed and we can view the reports Now Launch SQL Server Configuration Manager >Click SQL Server Services > Right Click SQL Server (Instance Name) > Properties > AlwaysOn High Availability Tab

19 Once you select the "Enable AlwaysOn Availability Groups" you will get the warning click "Ok"

20 Time to restart the SQL Server Agent services

21 Skype for Business Deployment We now move on to the deployment process for the Skype for Business Back End Database, as we already completed the All Front End Servers have been built with prerequisites, Skype for business Management Tools are installed and Skype for business topology has not to be defined Now press New, give the SQL server FQDN and select the Named Instance, in my case it is default Click High Availability Settings, now we can see the SQL Server FQDN filed has now changed to SQL Server Availability Group Listener FQDN and specify the primary SQL Server within the SQL Server FQDN field

22 Once complete publish the topology. Configure Skype for Business Databases for SQL AlwaysOn Availability Group Now Launch SQL Server Manager

23 Connect the SQL database and create New Database for high availability Give the Name etc.

24 Here you can see the Newly created Database, Right Click and open the properties > Select Option > Change Recovery Model from Simple to Full and repeat the process QoEMetrics Now we need to backup the databases within SQL Management Console, right click the Database SfBTestDB>Task>BackUp Verify the all settings and Click on Ok.

25 Here you will get the confirmation If you have the more Database you have to repeat the same process, here we have completed converting the Database to Full Recovery mode and backed up.

26 First of all log in to SQL Server management Studio and we can see that Skype for business server related databases were created successfully on SQL server USSQL1, now time to create a new Availability Group, right click AlwaysOn High Availability and open New Availability Group Wizard Fill the required information on wizard

27

28 Wizard also check the prerequisites and will let us know the details before proceed the database recovery needs to be changed to full and also perform a full backup. Click on Meet prerequisites

29 On the next step, need to add replica

30 And connect the second SQL server

31 Once you add you can see the both replica

32 Now we have to create a listener, select the listener tab and then select Create an availability group listener

33 Next specify a temporary file share, select Full synchronization.

34 And the wizard will run additional availability group validation checks

35 Here you view the complete summary

36 Everything is well, here is the details

37 From Console we can verify the, AlwaysOn High Availability configurations

38 Next we have to compare the Security Logins for both servers, if it is not matching with second SQL server we need to change the Primary Replica to the second SQL server, right click on Availability Group and select failover click on next and connect the SQL server, once failover successful we will get the summary wizard and we can review. And we can see that the primary replica is now in the second SQL server. Next, go to the Topology builder, select SQL Server Store and edit Properties and change the SQL Server FQDN to the second SQL Server and publish the topology. Once Topology published successfully now we have the Skype for Business Server 2015 with an AlwaysOn Availability Group configured.

39 Happy Learning Thank you! Disclaimer: The information contained in this Blog is for general information purposes only. It is strongly recommended to test it on a lab, before making changes in the production environment. If you want to implement you can use own your risk? If you feel some Content has to be removed which is not meeting any guidelines, please me dinesh.111@hotmail.com