none
Central Management Server cannot be moved to pool "Lyncfexxx" RRS feed

  • Question

  • Hello,<o:p></o:p>

    Our setup was running in Lync 2013 environment and recently we introduced only one skype 2019 server in the topology. As per the failover activity we tried to attempt Invoke-csmanagementserverfailover and encountered with below error.<o:p></o:p>

    Central Management Server cannot be moved to pool "lyncFEXXX" because either a previous failover attempt failed or there is already a failover in progress.<o:p></o:p>

    Note: Invoke-csmanagementserverfailover command was initiated from Lync 2013 management shell. The failure is really
    due to which the command was initiated from Lync 2013?<o:p></o:p>

    Besides, I need o fix the CMS replication issue in order to perform the poolfailover. As per the https://docs.microsoft.com/en-us/SkypeForBusiness/troubleshoot/server-configuration/cannot-perform-cms-failover article we need to run                      Invoke-CsManagementServerFailover –Restore to fix the issue.

    Is there any impact / side effects running this cmdlet in production?

    Thanks,

    Srini

    <o:p></o:p>

    Tuesday, June 25, 2019 2:38 PM

Answers

  • The issue has been resolve by updating the dbo.DbconfigInt table value under the XDS in SQL backend.

    The primary pool should have the value "Current State - 0"

    Backup pool should have the value " Current State - 3"

    In my case, the backup pool value was 1 instead of 3. Value 1 means the fail over is still going on. We changed the value to 1 by running the SQL query and checked the status. Everything started working normally including the CMS failover and backup status.

    Thanks,

    Srini

    Thursday, August 15, 2019 7:50 AM

All replies

  • Hi Srini,

    When using “Invoke-CsManagementServerFailover -restore”, it will restore the existing Central Management Server database.

    It is hard to say there is impact or no, I think you should first do a backup and schedule your downtime to do this based on the article.

    In addition, I assume you have deployed the pool pairing in your topology. Here is an article about pool failover you could refer to.

    https://ucgeek.co/2016/06/summary-pool-failover-failback-skype-business/

    Note: This response contains a reference to a third party World Wide Web site. Microsoft can make no representation concerning the content of these sites. Microsoft is providing this information only as a convenience to you: this is to inform you that Microsoft has not tested any software or information found on these sites and therefore cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software on the Internet.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, June 26, 2019 3:14 AM
    Moderator
  • Hello Shaw Lu

    Thanks for the details. We are planning to run this command on the weekend and let us the outcome.

    But, do we need to really run this command from Skype 2019 management shell or it is fine with Lync 2013 management shell as well?

    Note: Skype 2019 is not added in any pool as of now and running in standard edition. Pools paring is currently in Lync 2013 FE pools only.

    Thanks,

    Srini

    Wednesday, June 26, 2019 11:16 AM
  • Hi Srini,

    I think it is OK in either Lync 2013 or Skype for Business 2019 management shell.

    Hope everything goes well.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, June 27, 2019 8:24 AM
    Moderator
  • Hi Shaw Lu,

    MS suggested us to run the below command to perform the force move.

    Invoke-CsManagementServerFailover -BackupSqlServerFqdn "Servername" -BackupSqlInstanceName "SQL Instance name" -Force.

    Now, we can see the CMS is replication is up to date. However, we do see the below error when we run the command invoke-csmanagementserverfailover -whatif  

    Cannot failover the central management server, The new central management store located at "POLLXXX" is not in backup mode.

    Thanks,

    Srini

    Monday, July 1, 2019 7:22 AM
  • Hi Srinivasan,

    Did you deploy pool pairing with this “POLLXXX”?

    Please check the backup service on both primary and backup pool servers.

    Run “Get-CsBackupServiceStatus -PoolFqdn pool.domain.com | fl” to check the result.

    Usually both servers are in a “FinalState” and “NormalState”, so that pool fail-over is safe to perform.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, July 1, 2019 8:38 AM
    Moderator
  • Yes, we have deployed the Pool pairing.

    As of now, we see OverallImportstatus - Errorstate on both pools.

    OverallExportstatus - SteadyState on only one pool

    Thanks.

    Monday, July 1, 2019 10:01 AM
  • Hi Srinivasan,

    It seems something wrong about the backup service, please check the server Event to see if there is any related error.

    And here are some related articles you could refer to:

    https://blog.kloud.com.au/2017/07/23/resolving-skype-for-business-2015-backup-service-errorstate-issue/

    https://msucmenow.wordpress.com/2013/05/14/troubleshooting-lync-2013-pool-pairing-the-backup-service/comment-page-1/


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, July 2, 2019 7:48 AM
    Moderator
  • Ok. I am planning to break the pool pairing and configure it again to resolve the back-up issues. This is recommended by MS.

    Thanks,

    Srini

    Friday, July 12, 2019 12:57 PM
  • Status is same as earlier. We still see the below error

    invoke-csmanagementserverfailover -whatif  

    Cannot failover the central management server, The new central management store located at "POLLXXX" is not in backup mode.

    Thanks,

    Srini

    Tuesday, July 16, 2019 11:57 AM
  • The issue has been resolve by updating the dbo.DbconfigInt table value under the XDS in SQL backend.

    The primary pool should have the value "Current State - 0"

    Backup pool should have the value " Current State - 3"

    In my case, the backup pool value was 1 instead of 3. Value 1 means the fail over is still going on. We changed the value to 1 by running the SQL query and checked the status. Everything started working normally including the CMS failover and backup status.

    Thanks,

    Srini

    Thursday, August 15, 2019 7:50 AM