Storage Provisioning For a Single Hyper-V Server Setup

Dashrender

huh - interesting situation you have there.

Personally - I'd go back to the client and ask - if there is any chance you will need/want more storage in the server, then let's just do it right now. Buy the 2 additional 3 TB drives and let's just start off correctly with a RAID 10.

I'd skip installing Win server 2016 and instead install Hyper-V 2016, then you'll manage it from a Windows PC using Hyper-V manager (might require Windows 10). This also cuts out any concern on licensing - you won't be tempted to install any applications into the VM host OS

Splitting the VM's OS out from it's data really doesn't gain you much. The OS doesn't really impact the use cases you've mentioned here. Personally I'd create a single VMDK 60-80 GB for your VM1 (AD). The data server is the bigger question - one one hand you just make one huge partition for both data and OS, on the other, you can split it, then split the data across multiple VMDKs also - the only reason I mention this is restore time. If it's all one giant disk, you have to restore the whole thing before you can access it, if they are smaller, you can get access to each bit as you restore it.

Dashrender

Do you work at this client's site? If not - I don't see any mention of iLo. You should look into remote access to iLo as well. You'll also either need a VPN connection so you can use Hyper-V manager from your desktop, or remote access to a workstation onsite for management.

This all assumes you don't work onsite.

DustinB3403

This server already comes with iLO as a standard feature. So it should be utilized.

I also agree with @Dashrender to avoid split arrays because the client wanted to save a few hundred. Push back, and recommend against this approach. Get the two additional drives and create a single array in OBR10. 5200 or 7200 drives by themselves are painfully slow compared to OBR10 of the same setup. The client will notice, and will call asking "why are things so slow" and you don't want to be the guy who said "I told you so".

Get the raid issue sorted out now, not later.

Download and Install the hypervisor to the OBR10 and, create your 2 VM's from that. Don't install server 2016 directly to the array, it allows for temptation and can cause the client to be out of compliance with Microsoft licensing.

DustinB3403

@dr.funkenstein Also welcome to MangoLassi.it

DustinB3403

@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:

I've created 2xRAID1 arrays ... Array1 with 2x2TB HDDs, and Array2 with 2x3TB HDDS

Carved-out a 64GB partition on Array1, and installed Windows 2012 r2 Std. (With GUI, as I am a Hyper-V noob. Once I'm acclimatized to Hyper-V, I'll uninstall the GUI) for the host OS.

What about provisioning for Checkpoints and VSS ? Currently, VSS is disabled on all volumes on the Host OS.

Shall I created a 3rd VHDX for VM2, just for VSS ? If yes, what size, and would it be fine, if I create this VHDX on Array1 ? We are happy with around 2-3 days worth of previous versions.. I don't think daily changes would be more than 1GB

Is one large 2TB VHDX fine for the data, or should is it recommended to break it up in smaller VHDXs

Is it recommended to disable checkpoints for the Domain Controller VM ? ... btw ... how does one disable checkpoint, for a particular VM ? From Integration Services ?

Any special provisioning for paging ? or anything else, for that matter ?

I'm thinking of using VEEAM Free, for back-ups.. The back-up destination would be a Synology NAS box, with a 5TB HDD. Does VSS need to enabled for backups ?

Am I over-thinking things, and shall I just keep it real simple ?

As already stated in my previous post, address the RAID issue now, RAID1 is safe, RAID10 is safer and faster. Get the client to put in 4 matching drives and go with OBR10.

Why did you install Server 2012 R2 when you have Server 2016 licensing? Also don't install the server OS to the hardware, install the Hyper-V server to the hardware. Create VM's within the Hypervisor.

If you are using a Hypervisor OS, why use VSS, use Veeam free if you must. Veeam Free has some limitations you need to be aware of.

Creation of the virtual disks all depends on what the client needs.

Most people prefer smaller virtual disks, but 2TB is also fine.

If you are using Server 2016 as the DC, follow Microsoft's recommendations for how to set it up.

DustinB3403

I totally missed this part, where are you @dr-funkenstein going to backup too?

Did you mention a backup target and I just missed it?

Edit: Does the client have local storage, off-site storage? What kind of turn around time do they need should things blow up?

Dashrender

@DustinB3403 said in Storage Provisioning For a Single Hyper-V Server Setup:

I totally missed this part, where are you @dr-funkenstein going to backup too?

Did you mention a backup target and I just missed it?

Edit: Does the client have local storage, off-site storage? What kind of turn around time do they need should things blow up?

@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:

list item I'm thinking of using VEEAM Free, for back-ups.. The back-up destination would be a Synology NAS box, with a 5TB HDD. Does VSS need to enabled for backups ?

DustinB3403

@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:

@DustinB3403 said in Storage Provisioning For a Single Hyper-V Server Setup:

I totally missed this part, where are you @dr-funkenstein going to backup too?

Did you mention a backup target and I just missed it?

Edit: Does the client have local storage, off-site storage? What kind of turn around time do they need should things blow up?

@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:

list item I'm thinking of using VEEAM Free, for back-ups.. The back-up destination would be a Synology NAS box, with a 5TB HDD. Does VSS need to enabled for backups ?

So I did miss it.

Thanks

JaredBusch

@dr.funkenstein Having two arrays is just fine, but will really limit you later. So you can do it if you really, really, think they will not grow beyond it under normal growth curves. Remember, do not buy for a tomorrow that may not happen.

That said, you cannot grow a mirrored array. So to change things later would be a backup, wipe, and restore process.

I would grab two more 3TB drives and make a RAID10. The cost now versus later, is significantly lower if you expect at all to hit space limitations.

Now on to your hypervisor. Do not, ever, install Microsoft Server onto the bare metal. Install Hyper-V Server. Period. End of story.

As for the rest of your questions, here is the answer:

Am I over-thinking things, and shall I just keep it real simple ?

Yes, you are. Every single one of those bullet points is a complete waste of your client's money. Either because it is simply over complicating things for no reason, or a complete lack of understanding what you are doing.

I am not sure who tasked you with this job, but they should be wrote up and possibly fired for trying to give your company a bad name.

I get that you are new to setting this up, and it is great that you reached out for advice. But you should not be learning, in production, on a client system FFS.

FATeknollogee

@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:

Now on to your hypervisor. Do not, ever, install Microsoft Server onto the bare metal. Install Hyper-V Server. Period. End of story.

Does this "rule" also apply to Windows Server 2016 with Hyper-V role enabled?

dafyre

@FATeknollogee said in Storage Provisioning For a Single Hyper-V Server Setup:

@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:

Now on to your hypervisor. Do not, ever, install Microsoft Server onto the bare metal. Install Hyper-V Server. Period. End of story.

Does this "rule" also apply to Windows Server 2016 with Hyper-V role enabled?

I would suggest yes. Install Hyper-V 2016, and then install your VMs on top of that.

FATeknollogee

Who came up with this rule?

dafyre

@FATeknollogee said in Storage Provisioning For a Single Hyper-V Server Setup:

Who came up with this rule?

It's not really a rule... more of a guidline really.

But if you're going to use a server as a Hypervisor, why add all the extra overhead of a GUI attached to it and all that?

Edit: My guess would be @scottalanmiller or @JaredBusch , lol.

JaredBusch

@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:

I've created 2xRAID1 arrays ... Array1 with 2x2TB HDDs, and Array2 with 2x3TB HDDS

Carved-out a 64GB partition on Array1, and installed Windows 2012 r2 Std. (With GUI, as I am a Hyper-V noob. Once I'm acclimatized to Hyper-V, I'll uninstall the GUI) for the host OS.

Created a 300GB Partition (V:) on Array1, for the 2 VM guest operating systems. VM1 will the Domain Controller (DC) has a 100GB Dynamic VHDX, and VM2 (File and Application Server) has a 150GB Dynamic VHDX.

Created a 2.7 (Max available) partition on Array2, and assigned 1.5TB to a Dynamic VHDX, for all the Data. Attached this VHDX to VM2

DELETE everything here. Completely reinstall the system. Either use your two arrays or a single OBR10 if you get new drives.

Install Hyper-V server 2016 onto the smaller array, or the single array if you go that route.

Since you are new, simply disable the firewall entirely and deal with that configuration after you have the basics up.

netsh advfirewall set allprofiles state off`

Since you have 2 NICs, you will team them and plug both into the switch.
https://mangolassi.it/topic/9704/nic-teaming-on-hyper-v/6

#open a new powershell winddow
start powershell
#get the NIC names
Get-NetAdapter
#use said names to make a new team.
New-NetLbfoTeam –Name Team1 –TeamMembers NIC1,NIC2

Example after it is created:
0_1484243455110_upload-a84f1592-fd9a-4c80-8244-2464975b3fbb

Now connect to the server from a Windows 10 machine with the Hyper-V Manager and create your vSwitch.

Once that is done, go back to your powershell window and kill VMQ.
https://mangolassi.it/topic/8358/i-hate-vmq

Get-NetAdapterVmq | Disable-NetAdapterVMQ

Now you are ready to actually do things.

What about provisioning for Checkpoints and VSS ? Currently, VSS is disabled on all volumes on the Host OS.

You just crippled your system.

Shall I created a 3rd VHDX for VM2, just for VSS ? If yes, what size, and would it be fine, if I create this VHDX on Array1 ? We are happy with around 2-3 days worth of previous versions.. I don't think daily changes would be more than 1GB

I can't even understand this thought process. Likely from a lack of understanding basics. Just forget everything.

Is one large 2TB VHDX fine for the data, or should is it recommended to break it up in smaller VHDXs

You size your drives for the workload. Each VM should have a single drive unless there is some really odd configuration needed. You are dealing with a 15 user company, there will almost certainly be no reason. They are not a snowflake.

Is it recommended to disable checkpoints for the Domain Controller VM ? ... btw ... how does one disable checkpoint, for a particular VM ? From Integration Services ?

Why in the hell would you disable checkpoints for anything? They do not magically get created. You make them. So if you do not make them, who cares if it is enabled or disabled?

Any special provisioning for paging ? or anything else, for that matter ?

No, you are not a snowflake.

I'm thinking of using VEEAM Free, for back-ups.. The back-up destination would be a Synology NAS box, with a 5TB HDD. Does VSS need to enabled for backups ?

Without a paid license, Veeam cannot run scheduled backups, nor do anything but a "VeeamZip". This is not a bad thing, if you are aware of the limitations and account for them. VeeamZips can be scheduled outside of Veeam with a scheduled task running a command line statement. Veeam added this feature back in Version 8 I think.

Everything uses VSS. You have an unhealthy fascination with disabling it.

Am I over-thinking things, and shall I just keep it real simple ?

See prior post...

I'd like to know if the above storage provisioning is fine.. Comments and suggestions, a thwack on the head (for asking these ridiculous question) , are most welcome..

The thwack is reserved for whoever told you to do this to a client system.

DustinB3403

The point of not installing Server OS # onto the hardware for a Hypervisor has always been a guideline. And the reason being is it's wasted resources and energy.

You wouldn't install XenServer under Ubuntu.

Type 1 hypervisors exist for a reason, and it's so they can manage the hardware, and be as close to the hardware as possible for the management task.

FATeknollogee

@DustinB3403 said in Storage Provisioning For a Single Hyper-V Server Setup:

The point of not installing Server OS # onto the hardware for a Hypervisor has always been a guideline. And the reason being is it's wasted resources and energy.

You wouldn't install XenServer under Ubuntu.

Type 1 hypervisors exist for a reason, and it's so they can manage the hardware, and be as close to the hardware as possible for the management task.

Windows Server 201x (installed on bare metal) with Hyper-V role enabled is a Type 1 hypervisor, not sure why you think it's not.

JaredBusch

@FATeknollogee said in Storage Provisioning For a Single Hyper-V Server Setup:

@DustinB3403 said in Storage Provisioning For a Single Hyper-V Server Setup:

The point of not installing Server OS # onto the hardware for a Hypervisor has always been a guideline. And the reason being is it's wasted resources and energy.

You wouldn't install XenServer under Ubuntu.

Type 1 hypervisors exist for a reason, and it's so they can manage the hardware, and be as close to the hardware as possible for the management task.

Windows Server 201x with Hyper-V role enabled is a Type 1 hypervisor, not sure why you think it's not.

Actually, it is a mess. It is Hyper-V + a bunch of crap in a hosed up Dom0. because it is not originally a Type 1 either. It is a Server installed directly onto the hardware, then when the Hyper-V role is implemented, the server portion is migrated to dom0.

And the real issue is, as always with Microsoft, licensing.

Hyper-V Server is freely licensed to install and nothing is tied to the install.

If you Install Server, then that license is forever tied to that hardware. Yes, you get your two VM instances,but they can never be moved because you bound them to the hardware by installing Server instead of Hyper-V Server.

Had you installed Hyper-V Server, you could spin up a new Hyper-V server, (or even XS or VMWare) and migrated them both (they do have to stay together) with no licensing ramifications. You can do this as often as every 90 days if actually needed.

DustinB3403

Jared answered for me.

Thanks Jared.

JaredBusch

@FATeknollogee said in Storage Provisioning For a Single Hyper-V Server Setup:

@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:

Now on to your hypervisor. Do not, ever, install Microsoft Server onto the bare metal. Install Hyper-V Server. Period. End of story.

Does this "rule" also apply to Windows Server 2016 with Hyper-V role enabled?

This rule has applied to all Hyper-V installations since Hyper-V Server 2012 was released. There is no other way that Hyper-V should ever be deployed for the SMB.

The exception to the rule (and only because people can be lazy) is if every single physical system was licensed with Server 20XX DataCenter. At that point you are licensed to run anything anywhere, so who cares. Be lazy, install Server on everything if you want. I still would not, but that is up to you.

dr.funkenstein

Hi,

Thanks to all for the suggestions, comments, feedback , especially Jared... I really appreciate the candour ..

@Dashrender , @DustinB3403 , @JaredBusch - Yes, RAID 10 would be ideal, and will certainly be done in the future .. But, for now, we'll just have to live with 2 arrays of RAID1

Currently, the size of the data is around 1.4TB (not de-dup'ed... once de-dup'ed, may reduce) ... This is what they've accumulated over a period of over 10 years ... I don't see them running out of storage space, for atleast another 8 months to a year

I was told to install 2012 R2, simply because it's a more mature OS, by virtue of it being around for longer .. Infact, I'd prefer working on 2016

I'm not a Powershell expert .. also, we do not have a SCCM licenses.. Remote management will be done from Windows 8x machines, using RDP.. .. Hence, I thought, I'd start-off with 2012 R2 Server ... Once everything on Host server is ready, I am planning on uninstalling the GUI, and downgrading to Server Core ...

On Windows 8x, we use RSAT to manage Windows 2012 Server. Can the same RSAT be used to managed 2016 Server, or Hyper-V 2016 ?

@Dashrender - I've been working remotely, via VPN, and yes, using iLO..

@JaredBusch - Yes, the client has been informed that upgrading to RAID10 later, would mean a complete FFR (which, I'm guess, won't be that big a headache, since we're virtualizing)

@JaredBusch - The reason for creating a separate VHDX just for VSS of data is https://technet.microsoft.com/en-us/library/cc753975(v=ws.11).aspx

Also, I haven't manually or deliberately disabled VSS on the Volume housing the VM Guest OS VHDxs ... VSS was not enabled, by default...

My main reason for installing the full server, is non-familiarity with Powershell, and lack of proper freely available GUI tools, to manage remotely ....