Hyper-V Correct Usage of VMs and VHDs
Posted on 2010-11-12
I want to change out some physcal servers and begin running Hyper-V. However, I am trying to figure out some configuration issues.
Currently I have the following accessed by about 50 users:
Fileserver - currently has 2 shares (DocMgmt and Data)
The Data share is the main network drive mapped on the client PCs. Stuff like user directories are stored on it. However, some workgroup applications are installed to that drive from client machines and are executed from this share or houses data from the client piece of the program.
The DocMgmt share houses a ton of documents that are saved by our document management software program. When the uses saves/profiles a document, the file gets saved here, and the file data/profile gets saved to the SQL server.
SQL - has the database for our Document Management solution and our accounting system.
Exchange - typical exchange install
I am adding:
2ea - DL385 G7 2-processor servers, Windows Server 2008 R2, 40GB RAM, 2ea - 146GB SAS 15K HD (2 for each server, mirrored)
1ea - SAN P2000 G3 SAS Dual Controller Array, 8ea - 300GB SAS 15K HDs
4ea - SAS Controllers (2 for each server for redundant connectivity to the P2000)
2ea - Microsoft Windows Server 2008 R2 64-bit Enterprise
Microsoft Exchange 2010
Sql Server 2008 R2
My goal is to use Hyper-V to recreate and host a VM for each of my previous mentioned servers (Fileserver, Mailserver, SQLServer). Then to have Hyper-Vs High Availability configured to switch between my 2 servers if anything fails. Of course hosting the VMs or VHDs on the SAN so that both servers can access them.
What is the best way to configure my drives in the SAN for this scenario?
Should I create a VM for my fileserver but have seperate VHDs for my 2 shares? Or just make my OS and all shares just on one big static size VM file?
Should my drive for SQL be paritioned to segment logs and other items?
The SAN will also be used for another share in the near future as we start a paperless initiative.
As you can see, I have not too much experience with Virtualization (or SANs for that matter) but am ready to attack. Any suggestions or ideas are welcomed!!