• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 787
  • Last Modified:

best practice configuration for file & print server VM which will be replicated

Hi All,

I'm looking to create a file & print server VM using Hyper-v and have that server replicated to another host.

I want this server to host a file share with approx 500gb of files which will grow as well as the OS and AV applications.  For resilience, I will be replicating this server to another host.

I'm either going to create a 1TB VM, install the OS and partition the VHD with seperate drives for the file shares. Alternatively. I will create a 200GB VM and then create an extra VHD(x) under the VM hard drive options of 800GB to store the files.

Are there any best practices for creating VMs specifically those for storing large files or hosting file shares andany preference over the above methods? Note, I am replicating this VM to another host so size considerations are important.

I could be going about this the wrong way however so please let me know if there are alternative configs.
1 Solution
Cliff GaliherCommented:
Unlike physical drives where partitioning is required if you want to separate data types on continuous media, the nature of a virtual drive is that separation can be achieved simply by creating more drives. And by doing so, you also gain flexibility in that you can relocate a vhd(x) as needed to faster media as desired. I'd never partition a VHD. Simply create another VHD. As far as other "best practices" ...it depends on how you are replicating. I'd probably strongly consider a dynamic vhdx/thin provisioning the disk simply to keep actual file sizes down. But that does add some monitoring overhead as you need to be aware of you overprovision a thinly provisioned disk. With a new deployment,  I'd not even consider the older VHD format. Stick to vhdx unless Azure is going to be involved in the short term future.
lutherpendragonAuthor Commented:
Thank you Cliff. Just the confirmation I was looking for. With WIndows server 2012 r2 would you still say that it is best practice to have a seperate VHDx for the page file? especially since replication will be involved?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now