February 4, 2009 at 8:15 am
Hi all. We have install sql server cluster on one of our production server. As well as from cluster manager we have included all the drives except c drive as resources into our sql server group. Now, the problem is that , we can't see any other drives except D: drive from sql server...i.e. whenever we restore the database or attach the database it only shows D: drive on drive list...
Can you please tell us what can be the problem?
February 4, 2009 at 9:03 am
Is this an Active-Active cluster or Active-Passive?
You must assign the resources from Cluster manager and then specify the possible owners. Make sure the node you have SQL running on can attain ownership of the other drives. Also do a failover to make sure they ownership of resources gets transferred to the node that is running in case something bad happens.
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
February 4, 2009 at 9:30 am
Check your Dependencies in Cluster Administrator for SQL Server.
Make sure all your clustered disks are added as dependencies. If the SQL resource comes online before the physical disk does, SQL will not be able to access the drive.
cheers
February 4, 2009 at 9:44 am
Daveee (2/4/2009)
Check your Dependencies in Cluster Administrator for SQL Server.Make sure all your clustered disks are added as dependencies. If the SQL resource comes online before the physical disk does, SQL will not be able to access the drive.
cheers
The databases would be in Suspect mode and one has to restart SQL again with added dependencies as you mentioned..
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
February 4, 2009 at 9:46 am
The databases would be in Suspect mode and one has to restart SQL again with added dependencies as you mentioned..
Thanks!!
Unless he is talking about a backup drive or a drive on which no database files are hosted :w00t:
February 4, 2009 at 9:53 am
Daveee (2/4/2009)
The databases would be in Suspect mode and one has to restart SQL again with added dependencies as you mentioned..
Thanks!!
Unless he is talking about a backup drive or a drive on which no database files are hosted :w00t:
Good point..but I don't think they would build a cluster to host just backup files..from his post I feel they are going to place data,log and backup files on this production server which calls for correct configuration of dependencies from cluster administrator..and all this has to be thoroughly tested time and again by doing manual failovers..
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
February 11, 2009 at 12:03 pm
Still We have this problem.. Please reply.
By the way, can anyone How to setup dependencies from cluster manager?
Also to clarify again, We put Data drive(D: ),trans log drive(E: ) and backup drive(F: ) as resources in SQL Server group at cluster administrator. So that whenever we do failover, all these three drives will be gone to secondary server.
We are using Active-Passiver Clustering.
But we still don't know that why it is only showing us D: drive from sql server. Why it's not showing E: and F: drive, as we have also included those drives as a resource in SQL Server group.
Please reply.
Thanks.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply