During the planning and deployment of Microsoft 2012 or Microsoft 2008 R2 SP1 for your Front End pool, an important consideration is the placement of data and log files onto physical hard disks for performance. The recommended disk configuration is to implement a 1+0 RAID set using 6 spindles. Placing all database and log files that are used by the Front End pool and associated server roles and services (that is, Archiving and Monitoring Server, Lync Server Response Group service, Lync Server Call Park service) onto the RAID drive set using the Lync Server Deployment Wizard will result in a configuration that has been tested for good performance. The database files and what they are responsible for is detailed in the following table. NOTE: If your policies and configurations require a more specialized installation, the database and log files can be installed to any pre-defined location using the Lync Server Management Shell. See Database Installation Using Lync Server Management Shell for more details. DATA AND LOG FILES FOR CENTRAL MANAGEMENT STORE CENTRAL MANAGEMENT STORE DATABASE FILES Xds.ldf Xds.mdf Transaction log file for the Central Management store Maintains the configuration of the current topology, as defined and published by Topology Builder
Lis.mdf Lis.ldf Location Information service data file Transaction log for the Location Information service data file DATA AND LOG FILES FOR USER, CONFERENCING, AND ADDRESS BOOK CORE LYNC SERVER 2013 DATABASE FILES Rtc.mdf Rtc.ldf Rtcdyn.mdf Rtcdyn.ldf Rtcab.mdf Rtcab.ldf Rtclocal.mdb Rtcxds.mdf Rtcxds.ldf Persistent user data (for example, access control lists (ACLs), contacts, scheduled conferences) Transaction log for Rtc data Maintains transient user data (presence runtime data) Transaction log for Rtcdyn data Real-time communications (RTC) address book database is the repository where Address Book service information is stored Transaction log for Address Book Service Hosts the conference directory. Maintains the backup for user data. Transaction log for Rtcxds data. DATA AND LOG FILES FOR CALL PARK AND RESPONSE GROUP APPLICATION DATABASE Cpsdyn.mdf Dynamic information database for the Call Park application
Cpsdyn.ldf Rgsconfig.mdf Rgsconfig.ldf Rgsdyn.mdf Rgsdyn.ldf Transaction log for Call Park application data file Lync Server Response Group service data file for the configuration of the services Transaction log file for the Response Group application configuration Response Group service data file for runtime operations Transaction log for the Response Group service runtime data file DATA AND LOG FILES FOR ARCHIVING AND MONITORING SERVER ARCHIVING AND MONITORING DATABASE FILES LcsCdr.mdf LcsCdr.ldf QoEMetrics.mdf QoEMetrics.ldf Lcslog.mdf Lcslog.ldf Data store for the call detail recording (CDR) process of the Monitoring Server Transaction log for call detail recording (CDR) data Quality of Experience data file stored from the Monitoring Server Transaction log for Monitoring data Data file for the retention of instant messaging and conferencing data on an Archiving Server Transaction log for Archiving data In this topic, references are made to disk and to RAID set. Note that in the configuration of resources, referring to a disk means a single hardware device. A hard disk drive with two partitions, one holding log files
and the other partition holding data files, is not the same as two disks, each dedicated to either log or data files. In reference to RAID sets, there are a number of different RAID technologies from various vendors. And, with the proliferation of storage area networks (SAN), RAID sets dedicated to a single system are rarer. You should consult with your RAID or SAN vendor to determine what the best configuration is for your disk layout when configuring for performance with. Note also that not all disk drives are created equally; some perform better than others. Even drives from the same manufacturer can vary in performance because of rotational speed, hardware cache size, and other factors. LYNC SERVER 2013 Microsoft 2012 has specific requirements when installing and deploying. Because Windows and define their security differently, logging in as an administrator in the Active Directory domain does not implicitly grant permissions for. You must also be a member of the sysadmin entity on the -based server you are configuring. PERMISSIONS REQUIRED FOR DATABASE AND LYNC SERVER INSTALLATION The following options detail three permissions and group membership associations for installation of files and databases. Choose the scenario that best meets the requirements of your organization. PERMISSIONS AND GROUP MEMBERSHIP ASSOCIATIONS
SQL SERVER OR LYNC SERVER 2013 ROLE Administrator Administrator Both Administrators sharing installation duties ROLE-TYPICAL SQL SERVER PERMISSIONS AND GROUP MEMBERSHIP Must be granted membership of sysadmins SQL Server security group and member of the local Administrators group sysadmin group member (or equivalent) and member of the SQL Server local Administrators group Administrator is member of sysadmins group (or equivalent) and member of the SQL Server local Administrators group ROLE-TYPICAL LYNC SERVER 2013 PERMISSIONS AND GROUP MEMBERSHIP Must be a member of the RTCUniversalServerAd mins group Must be a member of the RTCUniversalServerRe adonly group administrator is member of RTCUniversalServerAd mins PERMISSIONS OUTCOME administrator has the proper permissions to install both Lync Server 2013 and databases. administrator has the proper permissions to install both Lync Server 2013 and databases. The Lync Server 2013 administrator can install Lync Server 2013, but cannot install the databases. The administrator uses the Lync Server Management Shell and Windows PowerShell cmdlets provided by the administrator to install the databases. The
Management Shell used by the SQL Server administrator is installed on the Front End Server. This eliminates the need to install the administrative tools on the SQL Server-based server.