none
Multiple Listeners need to fail over only one.

    Question

  • We have a three node multisubnet WSFC with SQL Server. We have two Availability Groups. The Listener for the first AG was a piece of cake. The Listener for the second no cake walk. We managed to create it with a different IP but my network guys says this is going to cause issue in DNS. The bottom line is I need to failover only one of the AG’s and have the listener work. I haven’t found much online to help. I did find a few words about changing the port but have lost that article.

     

    This must be possible to do, can someone please point me a few links that will help?

    Thursday, October 10, 2013 4:06 PM

Answers

  • >The ODBC drivers our app uses do not support MultiSubnetFailover so

    So why not upgrade to the latest SNAC ODBC drivers that do support MultiSubnetFailvoer?

    >I going to set RegisterAllProvidersIP = 1.

    You've got that backwards.  For legacy clients that don't support MultiSubnetFailvoer, you set RegisterAllProvidersIP = 0, and reduce the DNS TTL on the clients so they can get the new IP from DNS more quickly.

    "if you have legacy clients that that need to connect to an availability group listener and cannot use the MultiSubnetFailover property, we recommend that you change RegisterAllProvidersIP to 0. The following PowerShell example demonstrates how to do this. Replace yourListenerName with the name of the listener that you are changing."

    http://technet.microsoft.com/en-us/library/hh213080.aspx

    David


    David http://blogs.msdn.com/b/dbrowne/

    Friday, October 11, 2013 2:42 AM

All replies

  • I'm not sure what the issue is. 

    The two listeners will be completely separate.  And if your cluster is a multi-subnet cluster each listener will have an IP address on each subnet.

    By default each listener registers all of its IP addresses in DNS, and then the client connecting with MultiSubnetFailover=true connection string parameter will attempt to connect to both IPs and will use whichever one is online.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Thursday, October 10, 2013 6:36 PM
  • As of this afternoon I have been able to find enough information, and your verification, to determine that we have the proper setup. Two IP’s across 2 domains with the same DNS name. It worked very well. A failover from the Michigan to Amsterdam took less than a minute. Then from Amsterdam to Frankfurt was even faster. The ODBC drivers our app uses do not support MultiSubnetFailover so I going to set RegisterAllProvidersIP = 1.

    Thanks

    Charlie



    Thursday, October 10, 2013 8:54 PM
  • >The ODBC drivers our app uses do not support MultiSubnetFailover so

    So why not upgrade to the latest SNAC ODBC drivers that do support MultiSubnetFailvoer?

    >I going to set RegisterAllProvidersIP = 1.

    You've got that backwards.  For legacy clients that don't support MultiSubnetFailvoer, you set RegisterAllProvidersIP = 0, and reduce the DNS TTL on the clients so they can get the new IP from DNS more quickly.

    "if you have legacy clients that that need to connect to an availability group listener and cannot use the MultiSubnetFailover property, we recommend that you change RegisterAllProvidersIP to 0. The following PowerShell example demonstrates how to do this. Replace yourListenerName with the name of the listener that you are changing."

    http://technet.microsoft.com/en-us/library/hh213080.aspx

    David


    David http://blogs.msdn.com/b/dbrowne/

    Friday, October 11, 2013 2:42 AM