如何合理进行Lync容量规划


在Lync的项目实施中,都会涉及容量规划的问题。

本文将会围绕此问题,介绍在部署Lync时如何专业地设计后端数据库容量,文件共存容量以及监控归档,群聊等内容。

 

1. Lync Server后端所存储的主要数据如下

1) CMS

2) The Registrar, User Services, and the Address Book use this database for registration, routing, presence information & conferences, replicating user information, in-band provisioning, and address book functionality.

3) Application Store:

Call Park application

Response Group application

 

如果用户接近且不超过80000人,可参考如下配置:

http://technet.microsoft.com/en-us/library/gg398835.aspx

(微软官方文档中没有提供具体的计算方法和计算公式,我们会对此提供进一步更新。谢谢理解。)

 

2.存档和监控所存储的数据如下

Archiving and Monitoring Store

This store is used by the Lync Archiving Server Role and the Monitoring Server Role.  There are 3 separate databases used:

LcsLog: stores Instant Messaging and Conferencing data for archiving purposes (used by the Archiving Role).

LcsCdr: stores the Call Details Records (used by the Monitoring Role)

QoEMetrics: stores the Quality of Experience data (used by the Monitoring Role)

 

存档和监控的数据库大小计算公式:

Database size = (DB growth per user per day) * (Number of users) * (Number of days)

 

详情可参考如下链接:http://technet.microsoft.com/en-us/library/gg615015.aspx

 

计算举例

days to keep monitoring data 60
days to keep archiving data 60
CDR 49KB
QoE 28KB
Archiving 57KB
   
Number of users 1000
   
CDR 2940000KB
QoE 1680000KB
Archiving 3420000KB
   
   
Total space requirement 8040000KB
  8.04GB

 

3.关于持久聊天服务器的数据库大小计算

我们提供工具来完成本内容的计算,此工具可在本文附件中下载

 


 

4.关于Server的数量,CPU,网络带宽和内存的规划

此方面的规划计算可通过以下工具完成:

Lync Server 2013 Capacity Calculator:

http://www.microsoft.com/en-us/download/details.aspx?id=36828

 

5.SQL mirroring在SQL standard版本与SQL Enterprise版本间的区别

从逻辑上讲,两个版本是没有区别的,都可以实现相关功能。

但是如果需要高级的Mirror, always-on availability grp功能需要SQL Enterprise版本的支持。

 

 

 

Microsoft China Partner Team

 

Group Chat Database Sizing Tool & Lync 2013 file share space estimator.rar


Comments (0)

Skip to main content