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

Posted on 2014-08-06
Last Modified: 2014-10-07
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?
Question by:jsctechy
    LVL 52

    Accepted Solution

    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.
    LVL 1

    Author Comment

    thanks Carl-
    what about the Temp Logs directory? can that go with the other Logs directory?
    LVL 1

    Author Comment

    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?
    LVL 52

    Expert Comment

    by:Carl Tawn
    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:
    LVL 52

    Expert Comment

    by:Carl Tawn
    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.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
    Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
    Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
    This tutorial will walk an individual through the process of upgrading their existing Backup Exec 2012 to 2014. Either install the CD\DVD into the drive and let it auto-start, or browse to the drive and double-click the Browser file: Select the ap…

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    11 Experts available now in Live!

    Get 1:1 Help Now