A Unified Communication Blog
Get Adobe Flash player

If you are going to deploy a High Availability solution which you can use for Lync Server 2013, you will need to deploy a SQL 2012 mirroring cluster.

This is a guide on how to deploy the two primary server SQL 2012 servers.

 

I have in this example I have created two SQL Servers with these specs:

  • 4 x CPU
  • 16 GB RAM
  • 100 GB System Drive
  • 300 GB Data Drive
  • Windows Server 2012

You could also have 100 GB Log drive.

SQL Server loves performance and you should always place in a fast storage system, and give it a lot of memory.

Before you start the installation, you should create an account in AD, with a strong password, which never expires (you should manually control when you change the password).

The account will later in the guide running the SQL Services.

The AD account should be member of the local Administrator group on each server.

 

To install SQL 2012 you mount the SQL 2012 server CD in the first server.

Start the setup and click Next

Select the “New SQL Server…”

 

Select OK

 

Select Next

 

Select Next

 

Type a Product Key and Select Next

 

Read ALL the license terms before you accept it J and select Next

 

Select “SQL Server Feature Installation” and select Next

 

Select the below features

 

And these and select Next

 

When the check is complet Select Next

 

Make a new Named instance – call it RTC and Select Next

 

Select Next

 

Select an domain account for the below services

 

Choose mixed mode and type a strong SA password. You should also add administrator accounts or even better administrator groups which has access to manage the SQL.

 

On the Data Directories, choose where to place the databases and log files and Select Next

 

Select “Install Only” to the reporting services and Select next

 

Select Next

 

Select Next

At the next screen you can save an ini file which you can use on node 2, to make the exact same installation.

After a while the installation should complete and you can close the installation.

 

When you are going to install SQL on node 2, you can either do it all again, or you can do it the easy way if you remembed to save an installation ini file.

Mount the installation cd on the server and open an command prompt with administrator rights.

Run this command from the CD.:

F:>setup.exe /configurationfile=”c:_softwareConfigurationFile.ini”

After a while the installation is complete.

 

You should the run Windows update to install the latest servicepack and fixes for both windows and SQL server.

Normally you should run it a couple of times.

 

In the next guides, we will look at how to install the witness server, and configuring SQL and Lync.

 

Lync 2013 High Availability

Part 2: http://exchangepro.dk/2013/08/29/install-a-sql-2012-witness-server-for-use-with-lync-2013-part-2/

Part 3: http://exchangepro.dk/2013/09/01/configure-a-sql-2012-mirroring-cluster-for-use-with-lync-2013-part-3/

Part 4: http://exchangepro.dk/2013/09/14/deploy-a-lync-2013-file-store-part-4/

Part 5: http://exchangepro.dk/2013/09/19/prepare-your-servers-for-lync-server-2013-ha-part-5/

Part 6: http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/

Part 7: http://exchangepro.dk/2013/09/30/install-the-first-frontend-server-part-7/

Part 8: http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/

Part 9: http://exchangepro.dk/2013/10/13/install-the-office-web-servers-part-9/

Part 10: http://exchangepro.dk/2013/10/21/deploy-the-director-servers-in-lync-2013-ha/

Part 11: http://exchangepro.dk/2013/10/25/install-the-access-edge-ha-servers-part-11/

Part 12: http://exchangepro.dk/2013/11/05/deploy-reverse-proxy-using-kemp-hardware-load-balancer-part-12/

Part 13: http://exchangepro.dk/2013/11/14/adding-additional-frontend-servers-to-lync-ha-part-13/

Part 14: http://exchangepro.dk/2013/11/26/setup-load-balancers-for-the-internal-lync-servers-part-14/

Part 15: http://exchangepro.dk/2013/11/26/load-balance-the-office-web-apps-server-part-15/

Part 16: http://exchangepro.dk/2013/11/26/load-balance-the-lync-frontend-web-services-part-16/

Part 17: http://exchangepro.dk/2013/11/28/load-balance-the-lync-frontend-services-part-17/

Part 18: http://exchangepro.dk/2013/12/15/load-balance-the-lync-director-servers-part-18/

Part 19: http://exchangepro.dk/2013/12/15/load-balance-lync-access-edge-internal-nic-part-19/

Part 20: http://exchangepro.dk/2013/12/29/load-balance-lync-access-edge-external-nic-part-20/

7 Responses to Install a SQL 2012 Mirroring cluster for use with Lync 2013 – Part 1

  • Great post but where in the sql installation you save the intstallation.ini file?

    Thanks

    • disregard I figured it out :) excellent post had no idea I can duplicate installations with that file.

  • Very helpful and so detailed.

    thanks for so valuable knowledge sharing.

  • Hi Joachim,

    Setting up a Lync 2013 Environment, can you please let me know for Lync 2013 do we need SQL 2012 Standard or Enterprise version.

  • Hi Joachim,

    Great guide, I’ve found it very useful. My question is, is SQL mirroring necessary for HA? If I have a Back End pool with a single server, can I still achieve HA in my Front End pool, if it has multiple front end servers?

    • Hi Carson

      Thanks :)
      Yes, you can if you look isolated on the frontend servers – there is no requirements that you also need the SQL to be redundant.
      However – why deploy an enterprise pool with 3 or more servers and want it redundant if you have created a topology that is not redundant – if you patch the backend SQL you will bring down the pool. Or if you place all frontends on the same Hypervisor (if using Virtualization).
      I know a full setup require tons of servers to be redundant, but that is in my opion what an enterprise pool is for otherwise it you could have saved the complexity and cerated a standard server or a failover pool.
      Hopes this can help you on your way.

      Br. Joachim

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 71 other subscribers

Follow me on Twitter