Do I need to create a separate partition for the Data drive when using a virtual machine

Hey all,

I am thinking of creating a virtual machine for one of my clients using Hyper-V. It will be a terminal server environment where they will be using a cetralised database and accessing emails and docs. Their documents folder is only around 50GB and they have been getting away with 240GB up until now but I will increase a little when I build it. My question: Is there a need to partition the OS from the data drive.. will this provide any increase in performance or reliability?

FYI We will be running SSD drives with 32GB RAM, 8 vCPU cores which I think is ample.

Chopper2302Asked:
Who is Participating?
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 Fellow)VMware and Virtualization ConsultantCommented:
It's not compulsory, but it's up to you have you create servers.

Also DO NOT create partitions, but create individual virtual disks per volume (or drive letter).

e.g.

virtual disk 1 = C:
virtual disk 2 = D:

It makes it much easier in the future for expanding the disks.

Partitions are legacy of the old days, when we could only have 32MB partitions under DOS.
Chopper2302Author Commented:
Thanks for the reply.

Sorry, I worded that wrong and have had a big day. Yes, have created plenty of servers but not for Server 2016 yet. Usually, I create virtual disk

C:Drive for OS
D:Drive for Data

Will it increase performance though or is better for NTFS permissions.

One side question, how much space you would allow for VDisk 1 for Server 2016

TIA
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
If both virtual disks are on the same "volume" on the Host - the performance will be the same.

With two virtual disks, a small margin of improvement, but not detectable.

Easier to manage should you want to expand C: and D:

40-80GB but you can always grow it..

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
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Peter HutchisonSenior Network Systems SpecialistCommented:
For Drive C, I would allocate at least 100GB, that would cover the OS, applications and any updates that will accumulate over the months/years.
Chopper2302Author Commented:
OK, sweet thank you guys ;)
Chopper2302Author Commented:
Thanks again
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
no problems.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I have two very thorough EE articles on all things Hyper-V:

Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
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
Virtualization

From novice to tech pro — start learning today.