SQL Server Failover Clustering error

Question

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

Answer 1

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