locked
Standard FE servers - Pool failover RRS feed

  • Question

  • Hello,

    I configured automatic pool failover in Topology. After that, I run Invoke-CsBackupServiceSync command. Everything looks good. Get-CsManagementStoreReplicationStatus is good.

    I decided to test everything. I disabled the NIC on the primary server. Failover did not happen. When I try to run basic commands, like: Get-CsUser | Sort-Object registrarpool | fl displayname,registrarpool, I receive the following:

    ************************************************************
    Get-CsUser : A network-related or instance-specific error occurred while
    establishing a connection to SQL Server. The server was not found or was not
    accessible. Verify that the instance name is correct and that SQL Server is
    configured to allow remote connections. (provider: SQL Network Interfaces,
    error: 26 - Error Locating Server/Instance Specified)
    At line:1 char:1
    + Get-CsUser | Sort-Object registrarpool | fl displayname,registrarpool
    + ~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Get-CsUser], SqlConnectionExc
       eption
        + FullyQualifiedErrorId : Microsoft.Rtc.Common.Data.SqlConnectionException
       ,Microsoft.Rtc.Management.AD.Cmdlets.GetOcsUserCmdlet
    ******************************************************************

    After that, I decided to try it manually: Invoke-CsManagementServerFailover -BackupSqlServerFqdn fe01.domain.local  -BackupSqlInstanceName RTC -Force

    It did not work. I received the following:

    *****************************************************************
    WARNING: Invoke-CsManagementServerFailover failed.

    WARNING: Detailed results can be found at
    "C:\Users\admin\AppData\Local\Temp\Invoke-CsManagementServerFailover-564ca79d
    -de71-475b-a905-4ba6a79133e0.html".
    Invoke-CsManagementServerFailover : Command execution failed: A
    network-related or instance-specific error occurred while establishing a
    connection to SQL Server. The server was not found or was not accessible.
    Verify that the instance name is correct and that SQL Server is configured to
    allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error
    Locating Server/Instance Specified)
    At line:1 char:1
    + Invoke-CsManagementServerFailover -BackupSqlServerFqdn
    fe01.domain.local - ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-CsManagementServer
       Failover], SqlConnectionException
        + FullyQualifiedErrorId : ProcessingFailed,Microsoft.Rtc.Management.Deploy
       ment.MoveCms.FailoverCmsCmdlet

    ******************************************************************************

    What am I doing wrong? Can someone help?

    Thank you.


    Thank you. Eric.

    Wednesday, April 20, 2016 3:45 AM

Answers

  • Hi,

    There is no automatic failover. admin needs to initiate manually.

    The Automatic failover and failback for Voice option and the associated time intervals in Topology Builder apply only to the voice resiliency features that were introduced in Lync Server 2010. Selecting this option does not imply that the pool failover discussed in this document is automatic. Pool failover and failback always require an administrator to manually invoke the failover and failback cmdlets, respectively.


    To test.,

    http://www.gecko-studio.co.uk/dont-play-with-fire-play-with-pool-pairing-configuring-testing/


    - Muralidharan. Please mark as answer/useful if my contribution helps you.


    • Edited by Muralidharan Radhakrishnan Wednesday, April 20, 2016 3:27 PM
    • Proposed as answer by Liinus Thursday, April 21, 2016 8:11 AM
    • Marked as answer by KPABA Thursday, April 21, 2016 1:56 PM
    Wednesday, April 20, 2016 3:07 PM

All replies

  • Hi,

    There is no automatic failover. admin needs to initiate manually.

    The Automatic failover and failback for Voice option and the associated time intervals in Topology Builder apply only to the voice resiliency features that were introduced in Lync Server 2010. Selecting this option does not imply that the pool failover discussed in this document is automatic. Pool failover and failback always require an administrator to manually invoke the failover and failback cmdlets, respectively.


    To test.,

    http://www.gecko-studio.co.uk/dont-play-with-fire-play-with-pool-pairing-configuring-testing/


    - Muralidharan. Please mark as answer/useful if my contribution helps you.


    • Edited by Muralidharan Radhakrishnan Wednesday, April 20, 2016 3:27 PM
    • Proposed as answer by Liinus Thursday, April 21, 2016 8:11 AM
    • Marked as answer by KPABA Thursday, April 21, 2016 1:56 PM
    Wednesday, April 20, 2016 3:07 PM
  • Thank you for the explanation and article is very helpfull. I have one question from that article and hope that you know.

    The author shows that the server gecko-fe1.gecko-studio.local is down and we want to failover to the gecko-fe2.gecko-studio.local server.

    Question is why do we have to issue

    Invoke-CsPoolFailOver -PoolFqdn gecko-fe1.gecko-studio.local -DisasterMode

    instead of

    Invoke-CsPoolFailOver -PoolFqdn gecko-fe2.gecko-studio.local -DisasterMode

    If we have to fail to the second server, why do we run it for the first one that is down? Is it a mistake?

    Thank you.


    Thank you. Eric.

    Wednesday, April 20, 2016 11:49 PM
  • It's not a mistake.. you are intiating failover for a failed server.... to a server which is paired and expscted to be running.

    www.rtcpedia.com - A real time communications blog

    Thursday, April 21, 2016 7:18 AM
  • Hi,

    If I understand correctly, you are asking to run the powershell command on which server?

    The powershell command can be run on any of the server. And you need to mention the FQDN of failed server in the powershell command.

    https://technet.microsoft.com/en-us/library/jj205189.aspx

    PoolFqdn

    Required

    Microsoft.Rtc.Management.Deploy.Fqdn

    Fully qualified domain name of the pool being failed over from. For example:

    -PoolFqdn "atl-cs-001.litwareinc.com"

    Let me know if that clarifies,


    - Muralidharan. Please mark as answer/useful if my contribution helps you.

    Thursday, April 21, 2016 10:43 AM
  • Got it. Thank you very much.

    Thank you. Eric.

    Thursday, April 21, 2016 1:56 PM