<div>
It's not compulsory, but it's up to you have you create servers.<br />
<br />
Also DO NOT create partitions, but create individual virtual disks per volume (or drive letter).<br />
<br />
e.g.<br />
<br />
virtual disk 1 = C:<br />
virtual disk 2 = D:<br />
<br />
It makes it much easier in the future for expanding the disks.<br />
<br />
Partitions are legacy of the old days, when we could only have 32MB partitions under DOS.
</div>


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.

<div>
Thanks for the reply. <br />
<br />
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 <br />
<br />
C:Drive for OS<br />
D:Drive for Data<br />
<br />
Will it increase performance though or is better for NTFS permissions. <br />
<br />
One side question, how much space you would allow for VDisk 1 for Server 2016<br />
<br />
TIA
</div>


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

Chopper2302

<div>
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.
</div>


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.

<div>
OK, sweet thank you guys ;)
</div>


<div>
I have two very thorough EE articles on all things Hyper-V:<br />
<br />
<a href="https://www.experts-exchange.com/articles/13256/Some-Hyper-V-Hardware-and-Software-Best-Practices.html" rel="ugc">Some Hyper-V Hardware and Software Best Practices</a><br />
<a href="https://www.experts-exchange.com/articles/31442/Practical-Hyper-V-Performance-Expectations.html" rel="ugc">Practical Hyper-V Performance Expectations</a>
</div>


I have two very thorough EE articles on all things Hyper-V:

Some Hyper-V Hardware and Software Best Practices [https://www.experts-exchange.com/articles/13256/Some-Hyper-V-Hardware-and-Software-Best-Practices.html]
Practical Hyper-V Performance Expectations [https://www.experts-exchange.com/articles/31442/Practical-Hyper-V-Performance-Expectations.html]

<div>
<div class="content wysiwyg-content">
<h2>Hey all,<br />
<br />
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?<br />
<br />
FYI We will be running SSD drives with 32GB RAM, 8 vCPU cores which I think is ample.<br />
</h2>
</div>
</div>


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.


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

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.

Storage

The term "Backup" means the methods and processes involved to copy computer data (system data as well as application data) to media other than the ones where the data originally live (disk, tape, optical, cloud). "Restore" in turn means the methods and processes involved in data recovery, i. e., bringing back copied computer data to their original location. Backup/Restore primarily serves as a means of protection against data loss, be it due to disaster, corruption or sabotage. It can also be used for recovering data from an earlier point in time and even for cloning machines or applications. There is a wide variety of backup/restore software available, from expensive commercial products to free or open source tools.

Storage Software

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.