Understanding Monitoring and Archiving on Lync Server 2013


Monitoring and Archiving has undergone major changes since Lync Server 2010. For Lync Server 2010 and prior versions, we had Message Queuing (MSMQ), have messages stored on a communications server, which were transported to the Monitoring Server and the Archiving Server, using MSMQ, and then were consumed into respective server roles using an Agent. In Lync Server 2013, we introduced  Lync Server Storage Service (LySS), as a replacement for Message Queuing(MSMQ). The LySS database is part of the LyncLocal Instance on all servers.

LySS can have different types of data, but mostly has the following types of data

  1. Monitoring Data ( CDR & QoE Reports) which are sent to your Monitoring Server, defined in the topology
  2. Archiving Data ( for Content Archiving if enabled) , which are sent to the Archiving Server, defined in the topology

Since LySS is an SQL Express Instance it has some of the limitations of SQL Express Installation like 1 GB Maximum RAM Utilization, 1 CPU Max Utilization, and 10 GB Max DB Size. These limitations, generally speaking, work extremely well with LySS, as there is little data on the database, before it gets committed to the respective back-end servers, like a monitoring server or an archiving server. In the unlikely event that your Monitoring or Archiving Server is/are offline for an extended period of time ( or not configured correctly) , the 10 GB Max DB limit may certainly be a challenge.

Each LyncLocal instance can expand up to 10 GB in size, which can queue-up several hundred thousand messages, given most CDR/QOE reports are very small, Archiving data is fairly small too. Additionally, there are fail-safe mechanisms in place, to export the content from SQL Express to the either a Web service file share (for example \\contoso.com\LyncFileShare\1-WebServices-1\StorageService\DataArchive\20161122\LyncStd01.contoso.com\), if access to the file-share is available,  while the other possibility is the local Application Data directory of each front-end server ( for example C:\ProgramData\Microsoft\Skype for Business Server 2015\StorageService ).

The resource Kit for for Lync Server 2013 and Skype for Business Server 2013 have a tool called ImportStorageServiceData that can be used to re-import these files into the local LyncLocal instance.

In-order to help troubleshoot, we also have a built-in scenario called MonitoringAndArchiving, which will collect relevant logs from the servers, where the scenario has been running.

Description Centralized Logging Tool Scenario Logging Tool Components
Monitoring and Archiving logging MonitoringAndArchiving UDCAgent

 

A friendly note to all Lync Administrators, since this Database can have Content Archiving, which may be required for legal / regulatory / compliance purposes in your organization, before you scorch a server or delete this database, always take a back-up.The UDCAgent is an application that is responsible to transfer messages from LySS database to the appropriate back-end database.

Comments (0)

Skip to main content