How to setup disk configuration on Hyper-v server 2012 R2

I have a single Hardware RAID 6 configuration with 8 hard drives ( 4TB each)  which gives me a total of around 24TB . That's all the drives I have in the server.  After the install of 2012 R2, I realized that setup has automatically partitioned the 24TB disk and installed the OS on a 2 TB partition. ( See the Attached Image ) .  The rest of the space is shown as unallocated as you can see.  The goal is to add the hyper-v roll have a couple VMs, but the mail goal of this server is to use a 2012 R2 VM as a file server. We currently have around 12 TB of data to transfer to this file server. I am wondering what would be the best way to do this . I am not familiar with hyperv and its virtual disks in 2012 server.
disk manag image1. When I plan to configure the fileserver vm, should I allocate 20TB to it and keep the OS and the Data files on the same Virtual disk? And what kind of virtual disk I should go with ?

2. I was even planning to shrink the 2TB OS host partition since that is too much for just the host OS, Is that OK?

3. How does all this come into play as I may want to take snapshots or use Windows Backup to back up the VMs.? Or that is not possible with that big of virtual disk created. I was told that Windows will attempt to backup the entire disk with ( 20tb) every-time instead of  just the changes as it not to only backup the changes to a virtual disk.
Thank you for your help.
4. When I right click the unallocated space, I don't get any options to create a new volume. ( see attached image)
diskconfig2.jpg
LVL 1
netcompAsked:
Who is Participating?

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

x
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.

Cliff GaliherCommented:
1) Depends on your disaster recovery plan. There are benefits to splitting up OS and data as well as performance concerns. There are deployments where I'd keep them together and others where I wouldn't. Nobody here knows enough about your environment to answer this with any accuracy.

2) Sure.

3) Checkpoints (snapshots) in production are a bad idea. Windows Server Backup depends on how you set up the backup. From the host. From the guest. 4The backup target. Some scenarios support incremental backups. Others do not.

4) probably because the RAID array  was initialized as an MBR disk with 512b sectors. That has a 2TB limit and has had since windows 2000 era. Nothing to do with Hyper-V. You need to go with 4k and your RAID array will need to support that.
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Re: #4 - you will need to redo the server because Cliff is almost certainly right and you almost certainly cannot save the system as is.  You will almost certainly have to delete the array and recreate TWO arrays - one of 2TB (or less) for the boot drive and the rest on another drive.
0
netcompAuthor Commented:
I ended up redoing the OS by booting to UEFI and installing the OS after converting to GPT . So, now I have a single 22TB C: drive . I wonder if I should partition that now or leave it as is and install my VMs?
If I leave it the way it is , should the file server VM have two virtual disk: a  C: drive (for OS) and another virtual disk D:( for the 14TB of data) . ?  I am concerned about backup as I had been told that if you are using Windows backup from the host , the back will NOt do an incremental backup and will attempt to backup the entire 14TB of the data every time there is change in the guest OS. Thank you,
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
NO WAY do I make a 22TB C: drive.  There's no reason for it.  If this is a terminal server, do it, but for a Hyper-V server, make a separate partition to store your VHDs.  Heck, I'd make SEVERAL - in part because I use DYNAMIC VHDs and as they grow, they can fragment.  Instead, I'll make several partitions and store one VHD per - it will be a contiguous block of space that cannot fragment over the entire disk (admittedly, this is a RAID, it's less of a concern, but you should keep in mind your performance on a RAID 6 is not going to be very good compared to a RAID 10.  Before setting things up, I would STRONGLY encourage you to do some disk performance tests to see the kinds of performance you can expect - that includes running some tests on NON-RAID drives, RAID 10, even RAID 1 just to understand the performance impacts your going to see.
0
SteveCommented:
to add to the comments above, take note that running the host & some VMs on a single logical volume may have some performance issues. each of the VMs will be fighting the host for disk access and you may end up with disk queues.
If required disk space allows, try to create 2 separate logical disks (RAIDs) instead of partitioning a single one.

If this isn't practical, consider what LeeW has said above. he's right as a single 22TB OS drive is going to cause you issues.
Your comment about backups earlier is one such issue as windows server backup insists on trying to take an image of the full OS drive, regardless of it's size.
0

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
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
Hyper-V

From novice to tech pro — start learning today.