Solved

SQL 2008 R2 Failover Cluster Network Name Problem

Posted on 2014-03-29
2
660 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 500 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

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

A safe way to clean winsxs folder from your windows server 2008 R2 editions
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

617 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