SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Cluster not failing over after adding physical disk


Cluster not failing over after adding physical disk

Author
Message
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
Problem: Cluster not failing over after adding physical disk
Specs:
Server 2003
SQL 2005
Nodes: Active/Active, two node cluster each with an instance installed
Node1 has group A
Node2 has group B
Recent Event: I added a Physical Disk resource to group B on node 2 of the cluster

Story: I recently added a physical disk resource to group B on node 2 of a two node cluster. We are patching the servers and moved group A from node1 to node2, restarted node1 and moved group A back from node 2 to node 1.

An issue occurred when moving group B from node 2 to node 1. What happens is that the resources, SQL, IP… start moving over to node1 then the disk I just added fails and the whole group B moves back to node 2 (Fail Back).

I checked all the setting of the disk resource and they match perfectly with the others.

What I noticed is in computer management --disk manager of node 1 I do not see the disks for node2.

More specifically, in node 2 disk manager I can see all the local disk and the disks for node 1. The disk for node 1 are marked unreachable and have a red x. On node 1 I cannot see the disks for node 2 in the same way. I am only seeing the local disks on that node.

Another thing I noticed is that disk Manager on both nodes show a Disk 2

I rescanned disks on both server and still no luck.

Any help would be appreciated.

Jeff
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
More information:

I am in Node 2 in Computer Management, but this time SAN Disk Manager and under Disks I do not see the disk that is failing during a Move Group operation.

On node one all the disks are listed but node two does not have the disk that I just added.

Could this be my trouble.

Any help is appreciated.

Jeff
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53037 Visits: 17672
Once you add the new disks you must add them as a dependency to the SQL Server service cluster resource, this will require a restart of the clustered service

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
I did add the resource as a dependency to SQL Server Service, but have not yet restarted the "Cluster Service" on that node.

I will give it a try tonight after hours and let you know what happens.

Your help is appreciated.

Thanks

Jeff
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53037 Visits: 17672
jayoub (1/27/2014)
I did add the resource as a dependency to SQL Server Service, but have not yet restarted the "Cluster Service" on that node.

I will give it a try tonight after hours and let you know what happens.

Your help is appreciated.

Thanks

Please run the following from a command prompt on the server and post results

cluster node



cluster res



Take the new disks resource name from cluster res and put into the following

cluster res "disk resource name" /listowners



-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
Cluster res
Resource Group Node Status
Disk L: GroupsharePoint Z010 online
Disk M: GroupsharePoint Z010 online
SQL Network Name (SQLSHAREPOINT) GroupsharePoint Z010 online
SQL IP Address 1 (SQLSHAREPONT) GroupsharePoint Z010 online
SQL Server (SHAREPOINT) GroupsharePoint Z010 online
SQL Server Agent (SHAREPOINT) GroupsharePoint Z010 online
SQL Server Fulltext (SHAREPOINT) GroupsharePoint Z010 online
Disk J: GroupDisco Z009 online
Disk S: GroupDisco Z009 online
SQL Network Name (SQLVIRTUAL) GroupDISCOMP Z009 online
SQL IP Address 1 (SQLVIRTUAL) GroupDISCOMP Z009 online
SQL Server (DISCOMP) GroupDISCOMP Z009 online
Disk T: GroupDISCOMP Z009 online
NEWDB (this is a disk) GroupDISCOMP Z009 online
Disk K: GroupDISCOMP Z009 online
SQL Server Agent (DISCOMP) GroupDISCOMP Z009 online
SQL Server Fulltext (DISCOMP) GroupDISCOMP Z009 online
Cluster IP Address Cluster Group Z009 online
Cluster Name Cluster Group Z009 online
Disk Q: Cluster Group Z009 online
MSDTC Cluster Group Z009 online
Disk O: (problem disk) GroupsharePoint Z010 online


Cluster Node
Node NodeID Status
Z010 2 UP
Z009 1 UP

Cluster res "Disk O:" /listowners
Z010
Z009

Jeff
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
I just found out that the SAN Admin provisioned the disk to only the one node Z010 and did not include the other node Z009 in the storage software. The other drives have both hosts listed and probably this is the cause of the problem.

I will restart the cluster services or even the whole box tonight and check it and let you know.

I provided the information as best i could. I had to retype the whole thing and the formatting did not come out in a nice way.

Thank you very much

Jeff
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53037 Visits: 17672
jayoub (1/27/2014)
I just found out that the SAN Admin provisioned the disk to only the one node Z010 and did not include the other node Z009 in the storage software.

Thats your problem right there

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
jayoub
jayoub
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1297 Visits: 586
Still no luck. I rebooted the server and tried the move and it was the same results.

I still feel like the SAN Admin has not provisoned the drive correctly. I have done the job before with another SAN admin and it went without a hitch

In computer Management there is a folder called SAN Disk Manager and the trouble drive is not listed there. All other drives are listed and working. I have a feeling that there is more to the provisioning process that must be done.

I will keep trying and let you know what happens. I may have to start digging into the SAN myself and see. Sometimes a second set of eyes can spot something.

Thanks

Jeff
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53037 Visits: 17672
jayoub (1/27/2014)
Still no luck. I rebooted the server and tried the move and it was the same results.

I still feel like the SAN Admin has not provisoned the drive correctly. I have done the job before with another SAN admin and it went without a hitch

In computer Management there is a folder called SAN Disk Manager and the trouble drive is not listed there. All other drives are listed and working. I have a feeling that there is more to the provisioning process that must be done.

I will keep trying and let you know what happens. I may have to start digging into the SAN myself and see. Sometimes a second set of eyes can spot something.

Thanks

Its easy to get the IDs wrong and leave a device masked, i have experienced this in the past

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search