none
Lync 2013 | SQL Server 2012 RRS feed

  • Question

  • New SETUP in an existing forest

    Front End Servers:
    LyFE01.domain.com IP: xx.xx.xx.1 LyFE02.domain.com IP: xx.xx.xx.2

    Back End Servers: (Since we have no third SQL Server, automatic failover is not present. We’ve just setup Mirroring.)
    LyBE01.domain.com IP: xx.xx.xx.3
    LyBE02.domain.com IP: xx.xx.xx.4

    Pool Name: pool1.domain.com

    Web Services URL:
    Internal URL: intpool1.domain.com
    External URL: extpool1.domain.com

    SQL INSTANCE NAMES:
    Backend: LYNCDB
    Archiving: LYNCARCHIVING (Not yet setup because of confusion. Can I collocate this with the above LYNCDB Instance?)
    Monitoring: LYNCMONITORING (Not yet setup because of confusion. Can I collocate this with the above LYNCDB Instance?)

    DNS RECORDS:
    Host ‘A’ records for all nodes: xx.xx.xx.1, xx.xx.xx.2, xx.xx.xx.3, xx.xx.xx.4

    Host ‘A’ records for the Lync Pool as below:
    pool1.domain.com - xx.xx.xx.1
    pool1.domain.com - xx.xx.xx.2

    meet.domain.com – Meet Simple URL
    dialin.domain.com –Dial In Simple URL
    admin.domain.com – Admin Simple URL

    SERVER ROLES COLLOCATED:

    SQL REF URL:
    https://technet.microsoft.com/en-us/library/gg398102.aspx

    In this above URL there is a paragraph which says as below:

    You can collocate each of the following databases on the same database server:

    • Back-end database
    • Monitoring database
    • Archiving database
    • Persistent Chat database
    • Persistent Chat compliance database

    You can collocate any or any or all of these databases in a single instance of SQL Server or use a separate instance of SQL Server for each, with the following limitations:

    • Each instance of SQL Server can contain only a single back-end database, a single Monitoring database, a single Archiving database, a single Persistent Chat database, and a single Persistent Chat compliance database.
    • The database server cannot support more than one Front End pool, one Archiving deployment, and one Monitoring deployment, but it can support one of each, regardless of whether the databases use the same instance of SQL Server or separate instances of SQL Server.

    Q1. Under the DATBASES Section, the first line says you can collocate each of the following database on the same server and soon in the second paragraph it talks about the limitations such as: “Each instance of SQL Server CAN CONTAIN ONLY A SINGLE BACK-END DATABASE, a single Monitoring database, a single Archiving database, etc”

    what does this mean? I’ve to create multiple instances each one for Backend, Archiving & Monitoring on the same SQL Servers. Why does MS makes things complex and even more complex when explaining. I noticed that there is very less quality information or blogs on SQL Setup.

    https://technet.microsoft.com/en-us/library/gg425833.aspx
    In this above URL there is a paragraph which says as below:

    “Enterprise Edition Front End pool, which consists of one or more Front End Servers (typically, at least two Front End Servers for scalability) and a separate Back End Server. A Front End pool can contain a maximum of twelve Front End Servers. Load balancing is required for multiple Front End Servers. For SIP traffic, we recommend DNS load balancing, but hardware load balancing is also supported. If you use DNS load balancing for SIP traffic, you still need a hardware load balancer for HTTP traffic. We recommend SQL Server mirroring for high availability of databases. The back-end database requires a separate instance, but you can collocate the archiving database, monitoring database, persistent chat database, and persistent chat compliance database with it. Lync Server 2013 supports the use of a shared cluster for the file shares in your deployment. For details about database storage requirements, see Database software support in Lync Server 2013. For details about file storage requirements, see File storage support in Lync Server 2013.”

    Q1. As per my above plan, I’ve setup DNS Load balancing for my sip traffic and there is no hardware load-balancer available. In such a setup will it not work technically or is it mandatory?

    Q2. I’m confused because I’ve setup SQL Mirroring and when I was defining the topology, on Archiving & Monitoring Page it didn’t allow me to use the same Instance which I used for Backend? When we already have separate servers for SQL why is it not allowing me to use same instance. I was under the impression that it will create multiple Databases under the same instance. Please explain with some diagram or neat example or use my example itself.

    Thanks for reading my lengthy question.


    Fahad

    Wednesday, March 25, 2015 8:11 PM

Answers

  • I got the answer. If I wanted to use same Instance for archiving & monitoring OR same instance for all three (Backend, archiving & Monitoring).

    All I had to do was just select the SQL instance Name from drop-down on archiving & monitoring wizard. I was clicking New each time and getting that error.

    Marking this thread as closed.

    Thanks


    Fahad

    • Marked as answer by Fahad1981 Saturday, April 4, 2015 10:37 AM
    Saturday, April 4, 2015 10:37 AM

All replies

  • Lync 2013 can always be use with DNS loadbalancing for sip traffic. For  the web traffic you should use a HW LB if you will hve more than one FE.

    Monitoring an archiving could be installed in the same instance, but it has to be a named instance and not default


    regards Holger Technical Specialist UC

    Thursday, March 26, 2015 9:17 AM
  • It IS indeed possible to use the same, Default not named, SQL instance on the same SQL Server backend database as the Lync Server 2013 Enterprise Edition Front End Pool (with SQL Server 2012 SP1).

    Thanks / rgds,


    TechNet/MSDN Forum Moderator - http://www.leedesmond.com

    Thursday, March 26, 2015 1:16 PM
    Moderator
  • Hello Holger / Desmond,

    I'm running Windows Server 2012 R2 as OS & SQL Server 2012 With SP1 (Version: ).

    Whether you use Default or Named, you can't put Archive & Monitor Databases in same instance. Also, you cannot club any other database on Backend Instance. I've made a complete documentation of my topology builder, which I can email you, if you provide me your email address. Below i'm inserting key screenshots for your references.


    Fahad

    Thursday, March 26, 2015 2:07 PM
  • please find the third key snapshot.

    Fahad

    Thursday, March 26, 2015 2:08 PM
  • You certainly can; see:

    Server collocation in an Enterprise Edition Front End pool deployment for Lync Server 2013
    http://technet.microsoft.com/en-us/library/gg398102.aspx

    (tested and deployed in labs and production environments)

    Thanks / rgds,


    TechNet/MSDN Forum Moderator - http://www.leedesmond.com

    Thursday, March 26, 2015 10:26 PM
    Moderator
  • Hi Desmond,

    I'm already aware of the above URL & seen that notes. I've also mentioned this in my original query.

    If this is true, then why is it not allowing me to create topology using a single instance for Archiving & Monitoring at least. Please refer the screenshots sent earlier.

    Is anyone else facing similar issues? can you try this in topology builder and see if you can do it.

    Is there any lab where we can try this?

    Thanks
    Najeeb


    Fahad

    Friday, March 27, 2015 3:32 PM

  • It appears from your screen shot that TB is prompting that a SQL instance of that name already exists on the server you are selecting to use as the Witness. Can you check and remove it (if it exists and contains no data you need / or already backup) then try again?

    Thanks / rgds,


    TechNet/MSDN Forum Moderator - http://www.leedesmond.com

    Friday, March 27, 2015 3:47 PM
    Moderator
  • I've given below a simplified design which doesn't seem to work.

    Please guide..


    Fahad

    Friday, March 27, 2015 6:44 PM
  • this will not work, you cannot install 3 instances on one SQL server for you deployment.

    You can use one instance and install the mon and arch db on the same instance.


    regards Holger Technical Specialist UC

    Saturday, March 28, 2015 7:56 AM
  • Hi Holger,

    Even I don't want to try this. The fact is, in topology builder if I select same instance for Archiving & Monitoring it gives me error saying it is already in use.

    If you see the above excel table I sent, I tried keeping same instance for Arc & Mon, it throws an error. I'm trying to keep Arc & Mon on SQL Mirrorring without automatic failover because I can't even use the same witness server which I used for Backend Database.

    If you can take a minute and launch the Topology Builder yourself & try to keep Arc & Mon same instance you'll get the error.

    Could there be any version issue, like You people use & I'm using the Volume Licensing one.

    Just for the records, OS is windows server 2012 r2 and SQL is 2012 with SP1.

    Technically you all people are telling me it works, and it should work based on the TechNet documentation, then why isn't it? I gave all my settings I'm using.

    I've even made a document which I can email. I need to get out of this mess asap. Please help.


    Fahad

    Saturday, March 28, 2015 8:48 AM
  • Ok, what you can do is to use the same instance for the witness. The witness will not held any data oft the used db.

    The wittnes is used only for the automatically failover. The witness can also be a sql express and you don't need a license for this.


    regards Holger Technical Specialist UC


    Saturday, March 28, 2015 9:16 AM
  • Hi All,

    1. All I'm saying is, it doesn't allow me to use same instance for Archiving & Monitoring (With Only SQL Mirroring & no witness).

    2. If I use different instance it allows me to setup Archiving & Monitoring (with SQL Mirroring).

    There is a twist, since I'm trying to use different instances, if I try to use the same witness server which I used for Backend Database, even with different instance I get error.

    Now, how funny, this URL is even more messed up...

    http://lyncuc.blogspot.com/2012/07/lync-2013-topology-builder.html

    It uses same default instances for all three.

    Right now i'm not worried about witness for Archiving & Monitoring. Why am I not able to put this on same instance which is different from Backend Instance.

    I created multiple topologies scenarios but it doesn't work.

    Do I just have to give Instance Name or even the Database Name.

    Can anyone try using a topology builder & if it works, save that topology & zip & email me to khan_iem@yahoo.com


    Fahad

    Saturday, March 28, 2015 9:54 AM
  • I got the answer. If I wanted to use same Instance for archiving & monitoring OR same instance for all three (Backend, archiving & Monitoring).

    All I had to do was just select the SQL instance Name from drop-down on archiving & monitoring wizard. I was clicking New each time and getting that error.

    Marking this thread as closed.

    Thanks


    Fahad

    • Marked as answer by Fahad1981 Saturday, April 4, 2015 10:37 AM
    Saturday, April 4, 2015 10:37 AM