Solved

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

Posted on 2015-01-08
2
728 Views
Last Modified: 2015-01-09
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.
Thanks
0
Comment
Question by:lutherpendragon
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 40538512
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.
0
 

Author Comment

by:lutherpendragon
ID: 40539763
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?
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Resolve DNS query failed errors for Exchange
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question