I am in the process of upgrading our VMware data stores and planning on bringing in to the cluster the first SQL 2008 R2 64b server. In preparation for the SQL server the new SAN will have a RAID 10 LUNs and RAID 5 LUNs dedicated to the SQL server. The SQL Logs go on the RAID 10 and the Db go on the RAID 5.
My VM cluster consist of 3 x Dell R-710 servers will dual physical quad core processers and 72 GB of RAM. The 3 ESX servers already host 32 VMs. Review of the ESX performance show that the server's processors are not being taxed very hard (about 5%-10%) and the VMs are using about 16-20 GB of Memory per ESX server.
Here is what I have learned so far.
1. Start the 2008 SQL server as a uniprocessor server. It is easier to upgrade to a mulitprocesser server later.
2. There will be 3 vmdks - 1 for the OS, 1 for the LOGs and 1 for the DB.
3. The OS and DB will be put in the same VMFS. The logs on a RAID 10 VMFS
I am now looking for advice or best practices for building the SQL 2008 R2 64b server in VMware. For example.
I have not used resource groups. Should a resource group be built for just the SQL server?
Any advise and references would be most appreciated.