locked
S4B Upgrade to always on RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Following the link below:

    https://technet.microsoft.com/en-us/library/mt162336.aspx#BKMK_NoHAPool_CreateAlwaysOnGroup 

    We want to upgrade SQL store to be high available using always on an existing pool when we go through the article we have the below note:

    If the pool you are upgrading to an AlwaysOn Availability Group hosts the Central Management store for your organization, you must first move the CMS to another pool before you upgrade this pool. Use the Move-CsManagementServer cmdlet to move the pool. If you do not have another pool in your organization, you can deploy a Standard Edition server temporarily and move the CMS to this server before you upgrade your pool to the AlwaysOn Availability Group.

    Actually we dont have another pool and we dont intend to isntall a new one what will happen if we apply the procedure and we dont move the CMS server and why we have to move the CMS

    In case we move the CMS to a temporary pool as stated below do we have to delete the pool after we finish deployment since it is not  mentioned in the article.

    We appreciate your response and thanks in advance.

    Thursday, December 8, 2016 1:37 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Najwan,

    You need the Central Management Store accessible during the database server moves as you will need to update the topology from your old back end servers to your new back end server and publish this to make changes and for SfB to use the new SQL servers. If the CMS was not available you wont be able to change the configuration or update the CMS database so you would be stuck.

    Deploying standard edition front end server is recommend as described, you move the CMS from you old SQL server to the SE front end server which will hosted the CMS whilst you make your changes to the EE pool, after back end server changes, move the CMS back to the SQL always on back end servers and you can decommission the Standard Edition Front End Server.

    Its added work but its the best way to do it lowering risks and issues.

    Thanks,

    Martin

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". Thank you. This forum post is based upon my personal experience and does not reflect the opinion or view of my employer.

    • Proposed as answer by jim-xu Friday, December 9, 2016 9:17 AM
    Thursday, December 8, 2016 4:26 PM