locked
Skype specific instructions regarding the process that needs to be followed to migrate the Skype databases from one SQL Server to another. RRS feed

  • Question

  • For example, these questions should explain what type of info we need:

     

    ·        When we take the SQL databases offline (prior to migration) do we need to stop any Skype services? If yes, which ones?

    ·        Skype applications will be pointing at the source SQL Server. When we move the databases to destination SQL Server, are there any configuration settings we need to amend so that the Skype applications point at the new, destination SQL Server? If yes, which ones?

    ·        Following migration, presumably we will need to restart Skype services (if we stopped them before)?

     

    These types of instructions are normally documented by Microsoft. Please can you point us to the documentation that describes – in detail – how we can go about this migration?

    Tuesday, February 18, 2020 2:40 PM

Answers

All replies

  • Hi Sid4563,

    <Question 1> When we take the SQL databases offline (prior to migration) do we need to stop any Skype services? If yes, which ones?

    When you take the SQL database offline, it is no need to stop the Skype for Business services.

    <Question 2> Skype applications will be pointing at the source SQL Server. When we move the databases to destination SQL Server, are there any configuration settings we need to amend so that the Skype applications point at the new, destination SQL Server? If yes, which ones?

    You need to deploy a Standard Edition Server in your environment. Then, the Central Management Store will be hosted on the Standard Edition Server as an interim.

    <Question 3> Following migration, presumably we will need to restart Skype services (if we stopped them before)?

    You don’t need to stop the services. After you have published the new topology and have created new databases in your new SQL instance, you need to restore the backups. Then, you need to restart Skype for Business services one server at a time to pick up the new instance name. You should do this in a staged approach to ensure that you do not put all of your users offline at the same time.

    You can follow this document. It describes the detailed steps and it also support Skype for Business server: http://web.archive.org/web/20190322005314/https://blogs.technet.microsoft.com/nexthop/2010/12/20/change-a-pool-database-instance-when-the-pool-hosts-the-central-management-server/.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Wednesday, February 19, 2020 3:00 AM
  • Hi Sid4563,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.

    Thanks for your understanding.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, February 21, 2020 5:20 AM
  • Thank you for that link – this looks to be the sort of thing we want. I have some questions though:

     

    1)      The instructions are applicable to Lync Server 2010. As we are running Skype for Business 2015, are these instructions still going to work for us?

    2)      The instructions state that the most recent versions that have been tested for migration are from SQL Server 2008 R2 to SQL Server 2008 R2. Will these still work for us given that we’re migrating the CMS Server databases from SQL server 2008 R2 to SQL Server 2019?

     

    Please let me know if you need any further information in order to answer these questions.

    Monday, February 24, 2020 2:26 PM
  • Hi Sid4563,

    <Question 1> The instructions are applicable to Lync Server 2010. As we are running Skype for Business 2015, are these instructions still going to work for us?

    The commands used in this link are applied to Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019. So, you don’t need to worry about this.

    <Question 2> The instructions state that the most recent versions that have been tested for migration are from SQL Server 2008 R2 to SQL Server 2008 R2. Will these still work for us given that we’re migrating the CMS Server databases from SQL server 2008 R2 to SQL Server 2019?

    You can’t do like this.

    If your environment is Skype for Business server 2019, you can just use Microsoft SQL Server 2019, Microsoft SQL Server 2017, Microsoft SQL Server 2016. For more details about this, you can refer to this document: https://docs.microsoft.com/en-us/SkypeForBusiness/plan/system-requirements#back-end-databases-that-will-work-with-skype-for-business-server-2019.

    Different environment supports different SQL server edition. This is for Lync server 2013: https://docs.microsoft.com/en-us/lyncserver/lync-server-2013-system-requirements-for-sql-server. This is for Skype for Business server 2015: https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/requirements-for-your-environment/server-requirements#back-end-databases-that-will-work-with-skype-for-business-server-2015.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, February 25, 2020 6:20 AM
  • The link you provided below refers to Standard Edition Lync\Skype for Business servers – as we run Enterprise Edition Skype for Business 2015 servers please could you provide a link to the appropriate Enterprise edition guidance.

     

    http://web.archive.org/web/20190322005314/https://blogs.technet.microsoft.com/nexthop/2010/12/20/change-a-pool-database-instance-when-the-pool-hosts-the-central-management-server/.

    Thursday, February 27, 2020 8:44 AM
  • Hi Sid4563,

    In fact, this link refers to Enterprise Edition Lync/Skype for Business servers. The following image describes the workflow. The Standard Edition is just a temporary place to store the CMS database.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Thursday, February 27, 2020 9:08 AM
  • Hi Sid4563,

    I am checking the status of this case. Please let us know if you would like further assistance.

    Meanwhile, if the reply is helpful to you, please try to mark it as an answer to close the thread, it will help others who encounter the same issue and read this thread.

    Thank you for your understanding and patience!


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, March 3, 2020 9:05 AM
  • I’m glad that my reply is helpful.

    Here I will provide a brief summary of this post. This will make answer searching in the forum easier.

     

    <Request/Expectation>:

    Skype specific instructions regarding the process that needs to be followed to migrate the Skype databases from one SQL Server to another.

       

    <Suggestion>:

    <Question 1> When we take the SQL databases offline (prior to migration) do we need to stop any Skype services? If yes, which ones?

    When you take the SQL database offline, it is no need to stop the Skype for Business services.

    <Question 2> Skype applications will be pointing at the source SQL Server. When we move the databases to destination SQL Server, are there any configuration settings we need to amend so that the Skype applications point at the new, destination SQL Server? If yes, which ones?

    You need to deploy a Standard Edition Server in your environment. Then, the Central Management Store will be hosted on the Standard Edition Server as an interim.

    <Question 3> Following migration, presumably we will need to restart Skype services (if we stopped them before)?

    You don’t need to stop the services. After you have published the new topology and have created new databases in your new SQL instance, you need to restore the backups. Then, you need to restart Skype for Business services one server at a time to pick up the new instance name. You should do this in a staged approach to ensure that you do not put all of your users offline at the same time.

    <Question 4> The instructions state that the most recent versions that have been tested for migration are from SQL Server 2008 R2 to SQL Server 2008 R2. Will these still work for us given that we’re migrating the CMS Server databases from SQL server 2008 R2 to SQL Server 2019?

    You can’t do like this.

    If your environment is Skype for Business server 2019, you can just use Microsoft SQL Server 2019, Microsoft SQL Server 2017, Microsoft SQL Server 2016. For more details about this, you can refer to this document: https://docs.microsoft.com/en-us/SkypeForBusiness/plan/system-requirements#back-end-databases-that-will-work-with-skype-for-business-server-2019.

        

    <Reference Links>:

    http://web.archive.org/web/20190322005314/https://blogs.technet.microsoft.com/nexthop/2010/12/20/change-a-pool-database-instance-when-the-pool-hosts-the-central-management-server/.

    Different environment supports different SQL server edition. This is for Lync server 2013: https://docs.microsoft.com/en-us/lyncserver/lync-server-2013-system-requirements-for-sql-server. This is for Skype for Business server 2015: https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/requirements-for-your-environment/server-requirements#back-end-databases-that-will-work-with-skype-for-business-server-2015.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Best Regards,
    Sharon Zhao


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, March 11, 2020 6:27 AM