March 18, 2013 at 8:33 am
We created a single node cluster and installed sql server failover cluster on it. Plan is to move LUNS and attach the drives to the cluster. Do system db disk needs to be part of dependencies list in the sql server service in clustering?
March 18, 2013 at 9:39 am
.
March 19, 2013 at 7:04 am
:unsure:
March 19, 2013 at 9:30 am
all the shared disks are dependencies otherwise how would the service start
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 22, 2013 at 9:48 pm
Actually from what I understand not all shared disks are dependencies for the SQL Server resource. The Quorum and DTC LUNS will not be able to be added as dependencies yet they are shared disks. However, to answer the original question, yes whatever shared drive your system dbs are pointed to will have to be added as dependencies for the SQL Server resource. Don't forget to restart the SQL Server resource from within configuration manager for the new settings to be applied. Otherwise SQL will not start as it was pointed out before.
March 22, 2013 at 9:58 pm
Jay,
We tested it on the dev servers and we never had any issue with shared drives. We never restarted the service. I am not sure why you wanted to do a restart of the service after adding the disks as dependencies ? Can you please explain in detail ?
March 23, 2013 at 1:43 am
Jay Beta (3/22/2013)
Actually from what I understand not all shared disks are dependencies for the SQL Server resource. The Quorum and DTC LUNS will not be able to be added as dependencies yet they are shared disks..
Maybe i should have spelt it out, all shared disks that are part of the resource group which the instance will use.
If you read the original post above the OP asked if the disk the system dbs are on has to be a dependency or not, they didn't mention quorum, dtc or any other application group!!!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 23, 2013 at 1:48 am
muthyala_51 (3/22/2013)
Jay,We tested it on the dev servers and we never had any issue with shared drives. We never restarted the service. I am not sure why you wanted to do a restart of the service after adding the disks as dependencies ? Can you please explain in detail ?
This was usually only experienced on windows 2003 clusters, the service would have to offline before the dependencies could be modified.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 23, 2013 at 6:59 am
LOL, Perry, please don't take it personally. You mentioned ALL shared disks and since quorum and DTC are shared disks hence my posts was valid regarding that even know they were not explicilty stated. It was more of a clarification. Thats why I mentioned that the system dbs are on shared drives. Its semantics and no one is questioning your knowledge.
March 23, 2013 at 7:55 am
And Perry is correct, there is no need for the SQL Server resource to be restarted under 2008 R2 when adding a dependency. That was only necessary under Server 2003, my apologies.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply