what are the best practices for disk configuration/data directories for a sql server 2012 failover cluster?

hello all
im looking to setup a new sql server 2012 failover cluster (1 active, 1 passive node for the time being)
im wondering what the best practices are for the data directories, and which disks i should place them on
i originally setup 3 shared disks, 1 for DB, 1 for logs, and 1 for quorum
i believe in sql server 2012 i might need to specify locations for 3 other database locations which are TEMP DB, TEMP LOGS and BACKUP
can the TEMP DB go on the DB disk? and can the TEMP LOGS go on the original LOGS disk?
i assume im going to need to setup another disk for the BACKUP location
also, we are starting this cluster from scratch, and im not 100% sure how big to make each drive- is there a best practice for disk sizes? my department agreed internally that we would create a database drive which is 40gb in size, for the time being- this is being done so we can add more storage later on via our SAN administration console. what should the other sizes of the drives be if this database drive is going to be 80gb?

also, is the MSDTC drive now the QUORUM drive in sql server 2012?
LVL 1
jsctechyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Carl TawnSystems and Integration DeveloperCommented:
The Quorum disk shouldn't need to be any more than about 10GB.

In an ideal world you would have drives for Data, Logs, TempDB and Backup. However, if you're on a SAN then this is more of a maintenance thing rather than performance based.

Data will need to be however big you estimate it needs to be based on current, and expected, data volumes. Log should be at least 40% the size of the Data drive, but the bigger the better. Backup will need to be the same size as the Data drive. TempDB will need to be at least as big as the biggest index you have on your database - but again, the bigger the better.

These aren't hard an fast rules (nothing ever is in these scenarios) but are a rough guide.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jsctechyAuthor Commented:
thanks Carl-
what about the Temp Logs directory? can that go with the other Logs directory?
0
jsctechyAuthor Commented:
also- on my SAN, im able to increase the size of the volumes that are presented to the servers - how plausible and easy is it to increase the size of the drive(s) when its in a production environment? can i just rescan the iscsi target, and then increase the volume size via server management console?
0
Carl TawnSystems and Integration DeveloperCommented:
Again, it's one of those "It depends...." questions :)

On a SAN where all of the LUNs are striping across the same spindles then it doesn't really matter. Logs write sequentially, so logically should sit with the other log files. On the flipside tempdb usage tends to be more erratic than for user database logs, so can impact the log writing on other databases.

Performance wise you should also consider creating multiple files for tempdb to aid performance.

You can check up on Microsofts best practice guide for tempdb here: http://msdn.microsoft.com/en-us/library/ms175527%28v=sql.105%29.aspx
0
Carl TawnSystems and Integration DeveloperCommented:
With regard to resizing the LUNs; that's a bit outside my area of knowledge i'm afraid.  

At the data centre I worked at the storage team were loath to dynamically resize the LUNs (mainly because if something went wrong it would be their responsibility!), so we were always presented with new LUNs and had to switch over.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.