Hyper-V best practices

I am setting up a new server. For the base OS I am installing Server 2012 R2 core. This will be installed on its own partition.
Is it suggested or recomnmended that the Hyper-V servers (5 in all) be on their own partiton?
What I mean is OS Drive C, DVD Drive D, Server1 Drive E, Server2 Drive F, Server3 Drive G or should all the vhd's go on the same drive such as: OS Drive C, DVD Drive D, Server1 Drive E, Server2 Drive E, Server3 Drive E

any insight into this?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would only state do not use OS partitions, if this is what you mean, they are old fashioned, and to be avoided if you can!

If you have the option of creating a dedicated RAID 1 OS LUN (or disk) for the OS.

and then store the VHDs (VMs) on another RAID 5 LUN.

Its much easier in the future to upgrade or extend!

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
LostInWindowsAuthor Commented:
Thanks for the insight!
Lee W, MVPTechnology and Business Process AdvisorCommented:
IDEALLY you want the VMs - EACH ONE - on it's own set of spindles and NOT sharing them.  Disks are the slowest major component and splitting a single array amongst several active systems can lesson performance - sometimes unbearably, depending on usage.  If you can't do that, then I would recommend a RAID 1 for the host OS and separate set of spindles for guests in a RAID 10.

Personally, *I* would say to partition.  My logic for this is that it helps ensure (when using Dynamic VHDs) that you don't fragment the VHDs over one another as they grow and if one fills it's partition, it doesn't stop ALL.  (If you run out of disk space, the VMs will go into a paused state.  If you run out of space on one partition, only that one VM gets paused; run out with all VMs on a single partition and ALL systems pause.

I would also use FSUTIL to create large temp files that you can delete to free up space - you should never reach that point, but weird things happen and this helps ensure you don't end up stuck with no space and no time to buy additional storage.

fsutil file createnew <tempfile.tmp> <size (in bytes)>

For example:
fsutil file createnew ExtraSpace.tmp 10000000000
should create a 10GB temp file virtually instantly (remember to exclude from backups).
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Hi, please have a look at my EE article: Some Hyper-V Hardware and Software Best Practices.

There is a wealth of information in there based on our Hyper-V work since Longhorn (2008 beta).
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

From novice to tech pro — start learning today.