Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I need to deploy some vms for sql servers, how do you plan the san volumes ? put os, data & log files in different vmdk ? or different volumes ? or put all in same volume ?

Also , is it good advise to create many volumes or limit them to 1 or 2 ? ( sql-log, sql-data,files,os-vms,24hours, 5mins, no-replica )

thanks in advance.

share|improve this question
add comment

3 Answers 3

  1. Follow Microsoft's best practices for SQL disks. Put OS, data, and logs onto separate VMDKs. http://technet.microsoft.com/en-us/library/bb402876.aspx

  2. Don't use more virtual CPUs than you have to.

  3. Align your partitions.

  4. Don't put too many VMs on the datastore that your SQL server is on.

share|improve this answer
    
"Align your partitions." - could you explain this more ? –  user40997 Aug 1 '10 at 14:53
    
Sure! When partitions are unaligned with their underlying systems, you double the amount of work needed per IO request. VMware does a great job explaining it in the following document. Now, I will say that you may not notice a difference unless you have some serious IO on the SQL server, but again, we are talking best practice. :D vmware.com/pdf/esx3_partition_align.pdf –  JakeRobinson Aug 2 '10 at 6:07
1  
To this I would add - Seperate VMDKs and Datastores is good, but if they're all coming from the same RAID Array, your performance is still going to be limited by the number of spindles, RAID configuration, and contention with other VMs running on that array. I'd advise setting up dedicated RAID arrays on your SAN for the data & logs, if you performance requirements really require it. Extra arrays on your SAN is additional management etc though, so only if you need it. Also pay heed to the saturation of your links to the SAN (number of fiber or iSCSI interfaces available). These matter. –  Chris Thorpe Oct 24 '10 at 6:42
add comment

From performance perspective, it is always a good practive to put OS, data, log and tempdb files on different drives

share|improve this answer
add comment

Hello, I need to deploy some vms for sql servers, how do you plan the san volumes ? put os, data & log files in different vmdk ? or different volumes ? or put all in same volume ?

It depends on your backup and performance needs. If you plan to use snapshots, your snapshot provider may need to have the data and log files on the same VMDK. If you need multipathing for faster SAN throughput, then you may need data files on several different VMDKs on separate underlying LUNs.

Also , is it good advise to create many volumes or limit them to 1 or 2 ? ( sql-log, sql-data,files,os-vms,24hours, 5mins, no-replica )

Again, depends on your backup and performance needs. Generally it's easier to lump these onto as few volumes as possible, but if you're doing volume-level snapshots with your SAN for extremely fast backups, you'll want to group VMs together based on their disaster recovery needs.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.