Skype for Business/lync Database schema resolution

by Lao Zhu

Do you know how many DB instances and databases are used by Skype for Business Server 2015/lync Server 2013 (The following unified LYNC, forgive me, this is inertia salutation)? The result will be a little unexpected. As we all know, the database is to store data, and Skype stores the data where there are SQL, AD, and shared folders, ad used to store basic user information, such as SIP URI, telephone number, and user policy information is stored in the CMS (SQL), In addition, the ad is used for storage for a backwards compatibility.

650) this.width=650; "height=" 379 "title=" clip_image001[6] "style=" border:0px; "alt=" clip_image001[6] "src=" http:// S3.51cto.com/wyfs02/m02/6c/8a/wkiom1vlpntanyl4aadhwazqyjk962.jpg "border=" 0 "/>

This is mainly about the SQL database it uses, as a matter of fact, Lync with a SQL instance is ok (like), but actually, it will use more than one instance, why the use of so many SQL, look at this picture is probably understand,

650) this.width=650; "height=" 584 "title=" clip_image003[6] "style=" border:0px; "alt=" clip_image003[6] "src=" http:// S3.51cto.com/wyfs02/m00/6c/8a/wkiom1vlpnbdeehyaagiamrgmvk851.jpg "border=" 0 "/>

As you can see, even in the Lync Server deployment design where the front-end and back-end are detached, there is actually an SQL instance (SQL EXPRESS) on each Lync server (including the front-end itself) that hosts the backend A copy of some of the databases in the DB instance (although only the CMS database is mentioned in Microsoft's public profile, I find that there are actually RTC and Rtcdyn two databases),

650) this.width=650; "height=" 118 "title=" clip_image004[10] "style=" border:0px; "alt=" clip_image004[10] "src=" http:/ /s3.51cto.com/wyfs02/m01/6c/8a/wkiom1vlpnabeqieaabdbjc_yci280.jpg "border=" 0 "/>

Note that the replication direction is a push replication, that is, from the CMS master to each Lync Server push, from the service console you can see that each Lync Server has a Lync Server Replica Replicator Agent service, It is used to receive replica data and replicate the resulting information to the master, with a corresponding Lync Server Master Replicator Agent service on master.

650) this.width=650; "height=" "title=" clip_image005[6] "style=" border:0px; "alt=" clip_image005[6] "src="/HTTP/ S3.51cto.com/wyfs02/m02/6c/8a/wkiom1vlpnaa5jlmaaats24pasm087.jpg "border=" 0 "/>

Obviously, this design primarily takes into account the availability, for example, even if the backend database is down, because the other Lync server has a copy of the configuration locally, the main functionality of Lync is not affected (so from this point of view, the back-end SQL outage does not cause the entire Lync system to crash, Most features can be used, and from this point, whether the backend needs to be deployed as a mirror or cluster is also worth discussing, as mirroring and clustering, especially mirroring, provide high availability, but the mirror itself can become a new point of failure, resulting in more maintenance tasks. I think this design is more reliable than two separate SQL mirrors on the back end.

From the above figure we can also infer the deployment sequence of Lync, the first step to prepare the ad, the second step to prepare the CMS to use SQL, the third step is to call Topology Builder to create a configuration to save to the CMS, the fourth step is to install or update Lync based on the CMS configuration information, for the Standard Edition, is the order of course , the second step is not to prepare the CMS storage on the Standard edition in the diagram, typically to deploy back-end SQL. In my personal sense, the Lync Publishing Wizard interface design has some issues that don't take into account the user experience, completely unlike Windows Server 1, 2, 3, 4, and so clearly:).

650) this.width=650; "height=" 346 "title=" clip_image007[6] "style=" border:0px; "alt=" clip_image007[6] "src=" http:// S3.51cto.com/wyfs02/m00/6c/8a/wkiom1vlpneistwwaagrdxkbrpw864.jpg "border=" 0 "/>

650) this.width=650; "height=" 262 "title=" clip_image009[6] "style=" border:0px; "alt=" clip_image009[6] "src=" http:// S3.51cto.com/wyfs02/m01/6c/8a/wkiom1vlpnjik79saadlx1xnwdw019.jpg "border=" 0 "/>

The following is a table to show the purpose of the various databases and the instance (whether it is Lync Standard Edition, or Enterprise Edition, is the same, only the standard version of SQL Express, Enterprise Edition back end with a separate database).

Note: The standard version of Lync Server is actually a very interesting thing, unlike the other products of the Standard Edition and the Enterprise edition of the difference mainly manifested in the feature, Lync Server Standard Edition feature is not missing, it is characterized by the use of SQL Express, but it has an advantage, You can put most of the characters on one server (and the Enterprise Edition is not), this feature is very advantageous to the general small and medium-sized environment, because you can install only one Lync Server Standard Edition to accommodate all the features (in addition to the edge and WAC, the other archiving and monitoring or need a separate back-end, But small and medium-sized companies may not have a cold, not to mention the archive can also be integrated with mail, not necessarily with SQL, considering the high availability, and then install a standard version of the backup pool, can also achieve disaster recovery within a few minutes. And the enterprise version because can not put several characters in one, instead of a thing complicated.

650) this.width=650; "Height=" 509 "title=" clip_image010[6] "style=" border:0px; "alt=" clip_image010[6] "src=" http:// S3.51cto.com/wyfs02/m02/6c/8a/wkiom1vlpnnbps2qaakkli9ldv4893.jpg "border=" 0 "/>

L RTC Instance: (That is, back-end database)

650) this.width=650; "height=" 207 "title=" clip_image011[6] "style=" border:0px; "alt=" clip_image011[6] "src=" http:// S3.51cto.com/wyfs02/m00/6c/8a/wkiom1vlpnmcunewaacqu4jvd-a514.jpg "border=" 0 "/>

L Rtclocal Instances: (each Lync server has)

650) this.width=650; "height=" 118 "title=" clip_image004[11] "style=" border:0px; "alt=" clip_image004[11] "src=" http:/ /s3.51cto.com/wyfs02/m02/6c/85/wkiol1vlp-2rtgu-aabdbjc_yci207.jpg "border=" 0 "/>

L Lynclocal Example:

650) this.width=650; "height=" "title=" clip_image012 "style=" border:0px; "alt=" clip_image012 "src=" http:/ S3.51cto.com/wyfs02/m02/6c/85/wkiol1vlp-2axw_iaabuafp8m3k395.jpg "border=" 0 "/>

This article is from the "FireWire Technology Brothers Blog" blog, please be sure to keep this source http://huoxian.blog.51cto.com/9437529/1643971

Skype for Business/lync Database schema resolution