Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SQL 2008 R2 Failover Cluster Network Name Problem

Posted on 2014-03-29
2
Medium Priority
?
698 Views
Last Modified: 2014-03-30
regards,


when I failover between nodes of the same place, the network name does not respond to me within 15 minutes. The SQL gets Online but clients can not connect to the unresponsive SQL network name Cluster.

There any special settings that make ?
0
Comment
Question by:JnavarroMc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 28

Accepted Solution

by:
Ryan McCauley earned 2000 total points
ID: 39965767
Can we get some more detail here. For example:

1. Do the clustered network name and IP address come online as expected? The SQL Server clustered resource should rely on these and should wait until they're up to come online itself, so this shouldn't be an issue, but I wanted to confirm. If you move the resource group to the other server, is the IP the first thing to come online?
2. Can you suddenly connect after 15 minutes (and is this exactly, or around 15 minutes)? During this period, what happens if you try to connect to the SQL Instance by IP address, rather than name? During this "15 minute" period, can you connect to the clustered instance from one of the two nodes themselves, or can you telnet to the ip address on the open port?
3. During this 15 minute period, is the previously active (now passive) node still online? If it is, what happens if you reboot it - does the service on the other node suddenly become accessible?

Though I can't say for sure, I'd suspect the service is coming up without issue, and it's actually your networking equipment that isn't routing your requests properly. The IP address is owned by one node, and then when it fails over, the other node takes control of the IP address and starts to accept traffic. However, if you network equipment doesn't realize the switch has taken place, it may still be routing requests to the previously active node, and SQL Server isn't listening for them there anymore.

With the extra detail, we may be able to diagnose it a bit better.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
When trying to connect from SSMS v17.x to a SQL Server Integration Services 2016 instance or previous version, you get the error “Connecting to the Integration Services service on the computer failed with the following error: 'The specified service …
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question