Shulou(Shulou.com)06/02 Report--

This article focuses on the establishment and configuration of back-end database alwayson in skype for business server deployment. Viewing this article requires some experience and weakens the entire skype for business server deployment process.

When it comes to the high availability of enterprise backend databases when planning a Skype for business server project, Microsoft officially supports three defaults:

1. SQL failover cluster

2. SQL image

3 、 SQL Alwayson

SQL failover clustering is a relatively old technology, with high tolerance, complex operation but relatively stable and reliable. SQL image should be regarded as an intermediate product, and later SQL is gradually canceling this function, but it is easy to operate when deploying Skype, but the logging problem is a headache. SQL Alwayson is a new high-availability technology that began with SQL 2012. It is not as complex to configure as a SQL cluster, but has the high availability of multiple replicas as mirrored.

Today we will share how to achieve alwayson high availability of back-end data in Skype for business server.

Environment description:

Domain:ucssi.cn

The two SQL FQDN are: sqlsvr01.ucssi.cn and sqlsvr02.ucssi.cn

Skype server FQDN is: sfbpool.ucssi.cn

Prerequisite preparation:

Two SQL Server servers install .NET 3.5 in order to successfully install SQL Server 2014 and also need to install windows failover clustering on two SQL Server servers in order to successfully implement the SQL Alwayson function

We can execute the following installation command in Powershell (note to specify the source file for .net3.5):

Add-WindowsFeature Net-Framework-Core,Failover-Clustering,RSAT-Clustering-Mgmt,RSAT-Clustering-PowerShell-Source d:\ sources\ sxs

Next, adjust the order of SQL Server network cards: the service network card is better than the heartbeat network card.

When the above conditions are ready, start the Windows failover cluster deployment.

Two servers should be tested for cluster verification before creating the cluster, using the following Powershell command (or graphical interface)

Test-Cluster-Node sqlsrv01,sqlsrv02 (testing with this command will fully test the two servers, storage arbitration, etc., of course, there will be some warnings, it is recommended that you review each warning carefully and resolve the warning according to the actual situation before cluster deployment)

After completing the verification, you can start to create the cluster, using the following Powershell command to create the cluster (or graphical interface)

New-Cluster-Name sqlcluster-Node sqlsrv01,sqlsrv02-NoStorage-StaticAddress 192.168.31.180

Open Windows failover Cluster Administrator, and the cluster has been created

To configure witness quorum for the Windows failover cluster, you first need to create a shared folder to hold the witness

Then configure the cluster arbitration

Set-ClusterQuorum-Cluster sqlcluster-NodeAndFileShareMajority "\\ dc\ sqlclusterwitness"

The next step is the SQL Server installation. Note: alwayson only supports SQL Server 2012 or above. At the same time, SQL Server must be Enterprise Edition, and SQL Server instance names must be consistent.

To install the SQL Server function, at least check the database engine

Keep the default instance name or specify the instance name (the two SQL instance names must be the same)

Use a service account for domain users (it is recommended to create a separate service account for SQL in production environment, with ordinary user permissions)

Then wait for the installation of the two SQL Server to complete. Then we need to create an A record in DNS as a listener for alwayson. Take sql.ucssi.cn as an example, manually pointing to a VIP 192.168.31.168

When SQL Server is installed, open the SQL Server configuration Manager, select the SQL Server property, and enable the alwayson feature

Restart the SQL service

At the end of the SQL Server installation section, bloggers who have read my previous ADFS back-end database configuration should know that the alwayson configuration requires the existence of data before enabling high availability group configuration for this database. So the next step is to install Skype for Business Server, define a SQL Server in the topology, let the topology automatically create the database, then configure the database with alwayson, and change the database FQDN in the topology again after the configuration. Next, start the prerequisite installation of Skype for Business Server.

Open Powershell and execute the following command to install:

Add-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Server-Media-Foundation, BITS, Desktop-Experience, Telnet-Client-Source d:\ sources\ sxs

After installing the prerequisites, insert the image of Skype for business server to install

Next, complete the AD preparation in turn.

Install management tools

Then create a new front-end pool and select the back-end SQL Server to store as the new FQDN with listeners and one of the SQL Server in the backend database. The purpose is to allow SQL to automatically generate the database needed for Skype through the topology.

Then define the file storage and so on (here we focus on the back-end database, which will simplify the entire Skype for Business Server deployment process), and finally click publish Topology

After publishing the topology, the database required for skype has been automatically generated on sqlsrv01.

Since the premise of alwayson is to make a full backup of the database, you need to complete the backup of all databases at once before you can create an alwayson group.

Use the following SQL Powershell for backup

Invoke-Sqlcmd-Query "ALTER DATABASE [cpsdyn] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [rgsconfig] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [rgsdyn] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [rtcab] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [rtcshared] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [rtcxds] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [xds] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Invoke-Sqlcmd-Query "ALTER DATABASE [lis] SET RECOVERY FULL WITH NO_WAIT;"-ServerInstance "SQL01\ SFBDB_BACK"

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database xds

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database lis

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database cpsdyn

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database rgsconfig

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database rgsdyn

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database rtcab

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database rtcshared

Backup-SqlDatabase-ServerInstance SQL01\ SFBDB_BACK-Database rtcxds

Or use a graphical interface.

At the same time, the recovery model of the database needs to be changed to complete.

Finally, you need to copy the directory structure to the second SQL server:

Robocopy C:\ CsData\\ sqlsrv02\ c$\ CsData / e / xf *

Then start creating the alwayson group

Define group name

Select a database

Add copy

Next step is to create

Add a listener

The database is also synchronized on Sqlsrv02

At this point, you need to fail over the alwayson to the sqlsrv02

Select a new master copy

Complete the failover

Next we're going to go back to SFB Server and download the topology change SQL FQDN to sqlsrv02.

Publish the topology after the modification is completed

Then update the database with the following command

Install-CsDatabase-Update-ConfiguredDatabases-SqlServerFqdn sql.ucssi.cn-Verbose

Finally, change sql fqdn to listener FQDN again

Finally, the entire alwayson deployment process in the skype for business server environment can be completed by releasing the topology again.

Finally, to install the skype for business server component, the process is relatively simple, including local configuration, storage installation, Skype for business server component installation, and certificate application.

Next step: slightly! A little! A little!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.