August 18, 2010 at 8:05 am
We have added another SAN based Drive to our Clustered (Active/Passive) SQL 2005 server for the purpose of moving the backups to it. I have added it as a Cluster resource. When I open SSMS to modify either thru management or server objects the E Drive is not appearing.
How do we get that drive to appear to SSMS??
It is showing up in the My Computer. The Cluster has gone thru a failover test since adding the drive as well (essentially restarting the SQL service on that node).
August 18, 2010 at 8:11 am
Via script try creating a database to that drive and let me know what you get for an error.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
August 18, 2010 at 8:13 am
you need to add that drive as a dependency to the SQL Server instance you wish to use it on. You will need to offline the service resource first, then add the drive as a dependency, then bring the service back online again. Once this is done, SQL Server Management Studio will recognise that drive as one that the instance has a relationship with!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 18, 2010 at 8:19 am
Perry Whittle (8/18/2010)
you need to add that drive as a dependency to the SQL Server instance you wish to use it on.
Yeah - I figured as much as well and was hoping the error would show that. 😉
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
August 18, 2010 at 8:41 am
Ahhh I did not have that as a dependency of the SQL server itself. OK I will have to do that after hours. I will do that tonite and let you know!
Thanks!
August 18, 2010 at 9:06 am
you're welcome 😎
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 19, 2010 at 6:48 am
Perry & David! Thanks very much for both of your replies to my issue!
Perry's solution did the trick - I had added the physical drive to the cluster resources but had not made it a dependency of the SQL.
It now sees it! Thanks very much for all of your help!!!
Brad
August 19, 2010 at 8:53 am
Brad
you're welcome, this does trip a few people over 😉
SQL Server when clustered will only use devices that it has dependencies on!
Regards
Perry
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 20, 2010 at 4:54 am
I had the same problem a few moons ago with a cluster an outsourced IT company added disks to but they forgot about the SQL Server part - doh!
I found this short and simple how-to from MS (ignore the title). Don't think it applies to SQL 2008 since I've no 2008 clusters to test it on.
August 20, 2010 at 6:35 am
Thanks for that too! Just seems to be a real lack of written resource materials relating to the care and feeding of Microsoft Clusters...
August 20, 2010 at 7:03 am
After deploying a clustered SQL Server instance I always check my resource dependencies.
😎
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply