SQL Cluster failover - KB article

Hi Guys:
Long time ago, i was read one KB article which explains node selection during fail-over.
For eg: if we have have 3 node(A,B,C) cluster, If A is active for some reason it is going to fail-over, at this case it should decide either B or C. For this selection MS explained in one KB article.
Actually i m searching for this KB article but not found. If it there in your fav. list can you please share it.
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

KB: Failover behavior on clusters of three or more nodes
Doc:
Configure Failover and Failback Settings for a Clustered Service or Application
David
David http://blogs.msdn.com/b/dbrowne/

Similar Messages

Question on sql cluster failover behaviour

Hi Experts,
I have a doubt on SQL Cluster.
In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
Could anyone shed some insight on this?
Thank you.

All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Coldfusion Service to be restarted after each SQL Cluster failover

We have Windows 2003 Servers (Std) with IIS 6.0 . Our backend
is a clustered windows 2003 Ent environment, running an SQL 2005
Database. The entire cluster is running on a Unisys ES 7000
machine. We are running CFMX on the Windows 2003 Std Server (with
IIS6.0).
Everytime we need to perform a failover on our Windows 2003
Ent Clustered environment (same environment with the SQL database),
we normally need to recycle the Coldfusion service on about 5 or 6
of the Windows 2003 IIS6.0 servers.
The reason we need to recycle the Coldfusion service is
because requests peg the server to the point of not being able to
use it...very very slow.
Can anyone help? I'll be forever indebted
You can reach me at [email protected]
Thank you very much.

Hello,
Could you please examine the event viewer (Control Panel – Administrative Tools) and share with us any errors you may find?
http://windows.microsoft.com/en-us/windows/open-event-viewer#1TC=windows-7
Could you please examine SQL Server error log also and share any errors you may find?
http://msdn.microsoft.com/en-us/library/ms187109(v=sql.120).aspx
http://msdn.microsoft.com/en-us/library/ms175832(v=sql.120).aspx
If you use Windows backup feature, could you please verify if it includes a backup of SQL Server. That may be a possible
cause.
Make sure user databases do not have the “Auto close”
option set to true.
http://msdn.microsoft.com/en-us/library/bb402929.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

ColdFusion 9 Fails after SQL 2008 Cluster Failover

All,
I have a ColdFusion 9 app server that seems to be failing when my SQL 2008 cluster fails over to the passive node. By failing, my IIS server does not respond to any .cfm requests about 4-5 minutes after the failover. It serves out static and .asp pages just fine. Restarting ColdFusion server service and rebooting the server itself does not fix the problem. The only fix is to fail the SQL cluster back to the original node.
Specs are as follows:
SQL - SQL 2008 SP1 64-bit active/passive cluster VM
CF - CF9 running on Windows 2008 SP2 64-bit VM
Erick

Problem solved. We had a linked server defined in SQL that pointed to an Oracle instance. We could successfully run the "Test Connection" in SQL Management Studio for the linked server when our SQL 2008 cluster was on node 1. However, we got an "OraOLEDBpus10.dll: The specified module could not be found" error message when trying to test the connection when the cluster was on node 2. The fix was to add the Oracle folder path to the Windows PATH environment variable on node 2. The Oracle installer is supposed to do this automatically, so we don't know why it was missing.
The reason CF would become unresponsive was that we had a template with a query that used the linked server. The purpose of this template was to monitor the status of the linked server. Using CF Server Monitor, we were able to see active requests to that template which would keep running and not terminate even though we set a timeout value in CF Admin.
Erick

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Change the IP Addresss of Servers that are members of a Windows Failover Cluster and SQL cluster

Hi all,
I have 3-nodes Windows Server 2012 R2 Cluster, on top of it I have two clustered named SQL 2012 instances installed. We need to change the IPs and subnet for the three physical servers incorporated in the Windows cluster. What will be the impact on
the Windows and SQL clusters? What extra configuration is needed in both Windows and SQL clusters to make sure the service will not fail after changing the IPs?

A similar question was answered
here.
The impact is that your Windows and SQL Server failover clustered instances will be offline during configuration so you need to schedule downtime. Plus, your client applications will not be able to find the new IP addresses immediately, depending on your
DNS TTL value. Work with your network/systems engineers to find out what this value is or validate the existing TTL values on your clustered resources by checking the HostRecordTTL property value. A workaround here is to set the HostRecordTTL property values
of your SQL Server network name to a very low value, say 1 minute, and then change it back to the current one once all of the applications can connect back to them.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2014 Failover Cluster

Hi All,
I am having permission issue while bringing sql cluster resource online.
I had the cluster setup and working with ENT edition, inorder to change the SQL edition, I removed the node from the cluster, uninstalled all the binaries and create a new failover cluster using STD edition. Using the same network name/IP as before, however
the setup started failing while trying to bring the clustered service online.
Cluster network name resource 'SQL' failed to create its associated computer object in domain '' during: Resource online.
The text for the associated error code is: Access is denied.
Please work with your domain administrator to ensure that:
- The cluster identity 'DBCLUS$' has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity 'DBCLUS$'.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity 'DBCLUS$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.
There was no permission change in AD, and I verified all the proper permissions exits.
In the properties tab, I see Kerberos status: Access is denied.
Windows 2012 Cluster and Windows 2003 AD.
I am stumped. Any help appreciated. Thank You.
-Kranp.

Hi All,
I removed a node from the cluster and ran, cluster node <computername> /forcecleanup, to cleanup all the registery entries.
Now I am trying to create a new windows cluster and am getting the below error
Beginning to configure the cluster ********.
Initializing Cluster ********.
Validating cluster state on node ********.com.
Find a suitable domain controller for node ********.com.
Searching the domain for computer object '********'.
Bind to domain controller \\********com.
Check whether the computer object ******** for node ********.com exists in the domain. Domain controller \\********com.
Computer object for node ********.com exists in the domain.
Verifying computer object '********' in the domain.
Checking for account information for the computer object in the 'UserAccountControl' flag for CN=********,CN=Computers,DC=********,DC=com.
Enable computer object ******** on domain controller \\********.com.
Configuring computer object '******** in organizational unit CN=Computers,DC=********,DC=com' as cluster name object.
Get GUID of computer object with FQDN: CN=********,CN=Computers,DC=********,DC=com
Validating installation of the Network FT Driver on node ********.com.
Validating installation of the Cluster Disk Driver on node ********.com.
Configuring Cluster Service on node ********.com.
Waiting for notification that Cluster service on node ********com has started.
Forming cluster '********'.
Adding cluster common properties to ********.
Creating resource types on cluster ********.
Creating resource group 'Cluster Group'.
Creating IP Address resource 'Cluster IP Address'.
Creating Network Name resource '********'.
Searching the domain for computer object '********'.
Bind to domain controller \\********.com.
Check whether the computer object ******** for node exists in the domain. Domain controller \\********com.
Computer object for node exists in the domain.
Verifying computer object '********' in the domain.
Checking for account information for the computer object in the 'UserAccountControl' flag for CN=********,CN=Computers,DC=********,DC=com.
Set password on ********.
Configuring computer object '******** in organizational unit CN=Computers,DC=********,DC=com' as cluster name object.
Get GUID of computer object with FQDN: CN=********,CN=Computers,DC=********,DC=com
Provide permissions to protect object from accidental deletion.
Write service principal name list to the computer object CN=********,CN=Computers,DC=********,DC=com.
Set operating system and version in Active Directory Domain Services.
Set supported encryption types in Active Directory Domain Services.
Unable to successfully cleanup.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
An error occurred while creating the cluster.
An error occurred creating cluster '********'.
Access is denied
To troubleshoot cluster creation problems, run the Validate a Configuration wizard on the servers you want to cluster.
I can manually run clear-clusternode without any issues, verified all the permissions, exists.
I am stumped. Any help appreciated. Thank You.
-Kranp.

Disable Remote Resigtry service for SQL Server failover cluster

Hi,
Is it safe to disable Remote Registry service from the the two nodes of SQL Server failover clustering?
Operating system: Microsoft Server 2008 R2 Enterprise Edition (64-bit)
Database software: Microsoft SQL Server 2008 R2 Enterprise Edition (64-bit), Failover Clustering
Thank you.
Regards,
Gan

Hi Pradeep,
You are right. I tested and verified that the GUI of cluster (Failover Cluster Manager) was not working properly after disabling Remote Registry service. Thank you :)
Regards,
Gan

SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Moving Physical SQL Cluster into Virtual SQL Cluster based on Hyper-V Failover

Hello All............I have a SQL Cluster based on Physical Hardware that has Three-3 instances as well. I have setup a Hyper-V Failover Cluster (2012 R2) and have built Virtual/Guest SQL Cluster (2012 R2) upon it. Now, I intend to move
the instances/databases from Physical SQL Cluster to Virtual SQL Cluster.
1. Is this supported? If so, I would appreciate any guidance on it?
2. Is P2V of SQL Cluster supported in Hyper-V Failover Cluster based on Windows Server 2012 R2?

Hi Sir,
Please refer to the following blog regarding moving SCCVM SQL database to another SQL server:
http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
It is quoted from the similar thread :
https://social.technet.microsoft.com/Forums/en-US/a1558842-cdf5-4e5f-8f10-d660e96eae1b/migration-sql-for-sccm-2012?forum=configmanagermigration
But it seems that is a migration of system center production , I would suggest you to post the question to system center forum ：
https://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagermigration%2Coperationsmanagergeneral&filter=alltypes&sort=lastpostdesc
Best Regards,
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL CLUSTER NAME REMAIN IN A FAILED STATE

We have the following configuration in our enterprise;
- Two physical servers ( both running windows server 2008 R2)
- The physical servers have been clustered (CLUSTER1).
- Six Virtual Machines ( two for each tier of our SharePoint 2010 installation)
- Two web front ends, two application servers, two database servers.
- The two database servers (running windows server 2008 R2) have been clustered (SQLCLUSTER2) and point to a SAN.
After an unexpected power failure, the SQLCLUSTER2 has refused to come online. The IP Address comes "Online" when turned on manually. The disks also come online when turned on manually using "Bring this resource online". But once the
Cluster name is attempted to be brought online all other resources turn into "failed" state and the entire SharePoint portal becomes unavailable. See image below
Note: We have recently had a problem with one of our Domain Controller and had to be decommissioned one of the two(2) DC's. My investigation reveals that the decommissioned DC was used to create the Cluster Name Object (CNO) SQLCLUSTER2.
I have been battling to restore the cluster to normalcy for over a week now. But periodically (after some hours) all the resources turn to "failed" state and down goes our SharePoint portal.
Please any assistance anyone can offer to help resolve this issue would be highly welcomed.

Hi Pedro Fuentes,
Please refer the following article to check whether your CNO permission is correct.
Error during installation of an SQL server Failover Cluster Instance
http://blogs.msdn.com/b/psssql/archive/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance.aspx
The similar thread:
Sql Server 2008 R2 Clustered Setup fails with The cluster resource 'SQL Server' could not be brought online
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/04ee7ddd-f94a-4410-9ce4-cf25178e09da/sql-server-2008-r2-clustered-setup-fails-with-the-cluster-resource-sql-server-could-not-be-brought?forum=sqlsetupandupgrade
SQL Server Instance is not coming online on windows 2008 R2 cluster
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c7a8ad00-53be-409e-ac54-0a709e62e7bb/sql-server-instance-is-not-coming-online-on-windows-2008-r2-cluster?forum=winserverClustering
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL Server Failover Clustering error

Hi All,
I am currently setting up 2-node SQL Server cluster but I am getting error when doing the failover test from Node2 to Node1.
Here is the quick overview of what I have so far.
1. Setup the failover cluster for both nodes, public and private network, cluster disks for Quorum, MSDTC and SQL, etc.
2. Run validation configuration before creating the cluster. Validation report completed successfully with no errors/warnings.
3. Created cluster, created MSDTC cluster and installed SQL server on both nodes.
Now I am doing some failover test on whether cluster resources will failover from Node1 to Node2 and Node2 to Node1.
Failover Test: Active Node is Node1.
1. Disable Public network on Node1.
2. Failover to Node2 -> successful
3. Enable Public network on Node1.
Problem:
After the failover to Node1, I tried to failback the resources from Node2 to Node1 by disabling the public network on Node2 (which is the active Node after the failover from Node1 to Node2) but the cluster resources won't failback to Node1.
Failback from Node2 to Node1 -> failed
1. Disable Public network on Node2.
2. Failback to Node1 -> failed
- Cluster Name and Cluster IP ->
failed
- SQL cluster group (SQL name, SQL IP address, Analysis, SQL server and SQL Server Agent) ->
failed
MSDTC cluster group -> failed back successfully to Node1
3. Enable Public network on Node 2.
4. Manually online Cluster Group and SQL cluster group
I tried to Manually online the Cluster Group and SQL cluster group but it CANNOT be online unless I enable the Public network on Node2. I have checked on the cluster event log and I am getting some event ID 1077 and 1069 errors and Event ID 1069 and 1205.
Here are some of the logs on the cluster events.
Event ID 1069: The Cluster service failed to bring clustered service or application 'SQL_Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Event ID 1205: Cluster resource 'SQL IP Address 2 (db-vip)' in clustered service or application 'SQL_Group' failed.
Anyone experience the same issue before? Appreciate if someone can point me to right direction to resolve the issue.
Thanks in advance for your feedback.
BTW, failover and failback works perfectly when I try to reboot the Active node. Resources failed over successfully from Node1 to Node2 and vice versa when I reboot the server.
Thanks again.
Regards,
Ivan

Hi,
In above node test process 6, after “disable public network on node 2” the two cluster should still have private heartbeat network communication, check can you ping node 1 now?
Check event viewer, whether you received Event 1069 in node 1? Refer to this article to troubleshoot this issue:
Event ID 1069 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
Check and correct any problems with the application or service associated with the resource. For example, if the application or service cannot start within reasonable time limits, diagnose and resolve the issues that cause slow starting.
Check and correct any problems with cables or cluster-related devices.
Adjust properties for the resource in the cluster configuration, especially the value for Pending timeout for the resource. This value must allow enough time for the associated application or service to start. For more information, see "Viewing the value
for Pending timeout for a resource."
To view the value for Pending timeout for a resource:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
In the console tree, click a clustered service or application.
In the center pane, if you cannot see the clustered resource that you want to view, expand one or more visible resources until you see the clustered resource.
Right-click the resource you want to view, click Properties, and then click the Policies tab.
Under Pending timeout, view the setting. Make sure it allows enough time for the associated application or service to start.
For more information please refer to following MS articles:
Network failure detection and recovery in a two-node Windows Server 2000 cluster
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

SQL Cluster failover - KB article

Similar Messages

Maybe you are looking for