Sunday, 16 August 2015

Lync Server 2013 Architecture

Posted by Ashwin Venugopal

Enterprise Edition Servers

  • Front End Servers
    • In previous versions of Microsoft Communications Server, user data and presence information were saved only on the Back End SQL Servers.
    • In Lync Server 2013, user data is now replicated to every Front End Servers and this provides for more efficient connections.
    • The main function of the Front End Server is to act as the Registrar for the Lync users. 
    • One can group The Front End Servers as Primary and Backup Registrars for the Lync users. 
    • We can add as many as 12 Lync 2013 Front End Servers can exist in a single pool.
  • Load balancing
    • For SIP traffic that is IM and Enterprise Voice workloads, DNS load balancing is the preferred mechanism.
    • For conferencing traffic that uses web protocols, hardware load balancing is required.
  • Back End SQL Server
    • When Lync Server is installed as many as 12 back end databases are created in the SQL Server.
      • RTC Instance is used by Lync to store persistent user information like scheduled conferences, contact lists..etc
      • RTCLOCAL Instance is used by Lync front end server to store a local copy of the master CMS database and other database used for some user information (presence, endpoints..etc.)
      • Application Databases
        • CPsdyn: contain dynamic information used by Call Park application
        • RGSConfig: contain the configuration of the Response Groups, like Agents, Workflows, Queues, Holidays…etc.
        • RGSDyn: contain dynamic “live” information used by the Response Groups
      • Archiving & Monitoring Databases
        • LCSLog: archive information about Instant messaging sessions, P2P calls and conferencing used by the archiving server.
        • LCSCdr: store the call details records used by the monitoring server.
        • QoEMetrics: store information about Quality of Experience used by the monitoring server.
      • Central management Databases
        • XDS: this is the Lync Central management Store (CMS) database, it holds Lync topology, configuration and polices (more details: Simple understanding for Lync CMS)
        • Lis: store location information (network subnets, ports, Switches…etc.) that is used by Lync Location services for E9-1-1 feature.
      • Lync Core Databases
        • RTC: It store persistent user information (contact list, scheduled conferences…etc.)
        • RTCDyn: Store dynamic “live” data about users (current presence, endpoints user logged in from…etc.)
      • Users Databases
        • RTCAB: store the Lync address book information used by Lync address book services
        • RTCXDS: store a back up of user data
  • Edge Server
    • This is required in order to support external users.
    • For high availability DNS load balancing is the preferred mechanism for Edge pool.
    • Following services run on Edge Server
      • Access Edge (for SIP)
      • Web Conferencing Edge
      • A/V Conferencing Edge.
  • Optional Roles
    • Director
      • Responsible for authenticating users and informing them of their home Registrar.
    • Mediation Server
      • Mediation Servers are required for all Enterprise Voice deployments.
    • Persistent Chat Server
      • Group Chat
Standard Edition Servers

  • Front End roles as well as Back End roles
  • SQL Express
  • No Server Pools

Additional Servers and Services

  • Active Directory
  • Reverse Proxy (Optional)
  • Microsoft Exchange Server 2013 (Optional)
  • Office Web Apps Server (Optional)
  • Microsoft SharePoint 2013 (Optional)
  • System Center Operations Manager 2012 (Optional)
Thank you for reading.

No comments:

Post a Comment