Topic Last Modified: 2011-05-12

Microsoft Lync Server 2010 supports clustering for Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2, and Microsoft SQL Server 2005 in an active/passive configuration. For details about SQL Server clustering, see Database Software and Clustering Support in the Supportability documentation.

You should set up and configure the SQL Server cluster before you install and deploy the Enterprise Edition Front End Server and back-end database. For procedures to set up and install the clustering and SQL Server software, see SQL Server 2008 “How to: Create a New SQL Server Failover Cluster (Setup)” at http://go.microsoft.com/fwlink/?LinkId=202919. For procedures to set up and install the clustering and SQL Server software for SQL Server 2008 R2, see “Getting Started with SQL Server 2008 R2 Failover Clustering” at http://go.microsoft.com/fwlink/?LinkId=218032. For procedures to install and configure a cluster in SQL Server 2005, see “How to Create a New SQL Server 2005 Failover Cluster (Setup)” at http://go.microsoft.com/fwlink/?LinkId=202920. When you install SQL Server, you should install SQL Server Management Studio to manage the locations for database and log file locations. SQL Server Management Studio is installed as an optional component when you install SQL Server.

Important:
To install and deploy the databases on the SQL Server-based server, you must be a member of the SQL Server sysadmin group for the SQL Server-based server where you are installing the database files. If you are not a member of the SQL Server sysadmin group, you will need to request that you be added to the group until the database files are deployed. If you cannot be made a member of the sysadmin group, you should provide your SQL Server database administrator with the script to configure and deploy the databases. For details about the proper user rights and permissions that you need to accomplish the procedures, see Deployment Permissions for SQL Server.

To configure SQL Server clustering

  1. After you have completed the installation and configuration of SQL Server clustering, you define the SQL Server store in Topology Builder by using the SQL Server instance virtual cluster name (as configured in the setup for SQL Server clustering) and the instance name of the SQL Server database. Different from a single SQL Server-based server, you will use the virtual node fully qualified domain name (FQDN) for a clustered SQL Server-based server.

    Note:
    The individual Windows Server cluster nodes do not have to be configured for Topology Builder. You will use only the virtual SQL Server cluster name.

  2. If you are using Topology Builder to deploy your databases, you must be a member of the SQL Server sysadmin group. If you are a member of the SQL Server sysadmin group, but you do not have privileges in the domain (for example, a SQL Server database administrator role), then you have the rights to create the databases but not to read necessary information in Lync Server 2010. For details about the user rights and permissions necessary to deploying Lync Server 2010, see Deployment Permissions for SQL Server.

  3. Ensure that the database folder and log files folder defaults are mapped correctly to the shared disks in the SQL Server cluster by using SQL Server Management Studio. This is a required procedure if you will create databases by using Topology Builder.

    Note:
    If you did not install SQL Server Management Studio, you can install it by rerunning the SQL Server installation, and then selecting the management tool as an added feature for the existing SQL Server deployment.

  4. Install the databases for the SQL Server-based server by using either Topology Builder or Windows PowerShell cmdlets.

To create databases by using Topology Builder

  1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.

    Warning:
    The following procedure assumes that you have defined and configured your topology in Topology Builder. For details about defining your topology, see Defining and Configuring the Topology. To use Topology Builder to publish the topology and configure the database, you must log on as a user with the correct user rights and group memberships. For details about the required rights and group memberships, see Deployment Permissions for SQL Server.

  2. In Topology Builder, as you publish the topology, on the Create databases page, click Advanced.

  3. The Select Database File Location page has two options that determine how the database files will be deployed to the SQL Server cluster. Select one of the following:

    • Automatically determine the database file location. This selection uses an algorithm to determine the database log and data file locations based on the drive configuration on the SQL Server-based server. The files will be distributed in such a way as to attempt to provide optimal performance.

    • Use SQL Server instance defaults. Selecting this option will install the log and data files according to the SQL Server instance settings. After deployment of the database files to the SQL Server, your SQL Server database administrator may want to relocate the files to optimize performance for your particular SQL Server configuration requirements.

  4. Complete the publishing of the topology and confirm that there were no errors during the operation.

To use Windows PowerShell cmdlets to create SQL Server cluster databases

  1. Open Lync Server Management Shell.

    Note:
    Production SQL Server clusters typically require that logs and data files be placed strategically for performance reasons.

  2. Use the Install-CsDatabase cmdlet to install the Topology Builder configured databases. Do one of the following:

    • Install the database files to the clustered SQL Server-based server and respect the definitions that you created in the topology document. The topology document defines the clustered SQL Server-based server instance, but you need to deploy database files to specific disk locations.

      Copy Code 
      Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <fully qualified domain name of SQL Server cluster> -DatabasePaths <logfile path>,<database file path> -Report <path to report file>
      Copy Code 
      Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn sqlvirt.contoso.net -SqlInstanceName  RTC -DatabasePaths "g:\rtcdynlog","h:\rtclog","i:\dbs" -Report "C:\Reports\Install-SQL-Cluster-DBs.htm"
    • Alternatively, you can use the following command to allow the cmdlet to determine the optimal location for the log and data files, and to override the topology document to use a named instance on the clustered SQL Server-based server.

      Copy Code 
      Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <fully qualified domain name of SQL Server cluster> -SqlInstanceName <named instance> -Report <path to report file>
      Copy Code 
      Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn sqlvirt.contoso.net -SqlInstanceName  RTC -Report "C:\Reports\Install-SQL-Cluster-DBs.htm"
    Tip:
    By omitting the DatabasePaths parameter, the cmdlet is allowed to determine the optimal placement of the log and data files on the named instance.