Upgraded my homelab!!

Last week I’ve upgraded my homelab again. Now Windows Server 2019 is GA, this setup is running Windows Server 2019 with the Hyper-V server role enable. This machines has capacity enough to run several virtual machines and also nested virtualization. Very useful to install for example a virtual Storage Spaces Direct (S2D) cluster of other Hyper-V clusters!

So let’s rock and create some virtual machines running Windows Server 2016 and 2019!!

  • AMD A8 3870K 3.00GHz 4MB FM1 Box
  • Asus F1A75-V PRO AMD A75, SATA600 RAID, HDMI
  • Corsair 32GB PC3-14900 DDR3 SDRAM Vengeance (4x 8GB, 1866MHz
  • 1 x Samsung SSD 850 EVO 250 GB
  • 1 x Crucial CT512MX100SSD1 512 GB
  • 1 x WD Cavlar Green 1,5 TB

And this setup is fast….realy fast!! The boot tinme of a virtual machine running Windows Server 2019 is around the 5 seconds!!

     

     

Example failover scenarios with Windows Server 2019 S2D cluster

In my previous blogpost, I’ve installed and configured a two node virtual S2D cluster with Windows Server 2019 within Hyper-V on my laptop (Windows 10).

Now the full infrastructure is up and running, and the first guest virtual machine is a live, it’s also nice to take a view on some failover scenarios! In the following examples, you can see the high availability and resiliency of a Storage Space Direct (S2D) cluster. It’s realy, realy, realy powerfull and absolute the feature of virtualization!!

The following scenarios I’m going to cover:

  • Live migration virtual machine;
  • Pause a Hyper-V cluster node (drain roles)
    • for maintenance, for example patching, firmware updates or driver updates.
  • Power Off a Hyper-V cluster node
    • For example a power failure or hardware failure

Scenario 1 – Live Migration:

This feature is already present in the previous versions of Hyper-V and it’s realy powerfull to migrate a virtual machine to another Hyper-V host without any downtime!

        

Scenario 2 – Pause a Hyper-V cluster node:

In this scenario I’m going to ‘pause’ a Hyper-V cluster node with the ‘drain roles’ option. This can be for maintenance, for example: Patching, firmware updates, driver updates or just investigate some issues within Windows.

     

     

As you can see, in my two node S2D cluster, we can ‘pause’ one of the Hyper-V cluster nodes and the virtual machine is still up and running!!

Scenario 3 – Power Off a Hyper-V cluster node:

In this scenario I’m going to simulate a power failure or hardware failure, just to ‘Power Off’ on of the Hyper-V cluster nodes! The virtual machine is saved for a couple of seconds, migrated to the other Hyper-V node and started again!

              

With also with a hardware or power failure, the impact and downtime is that much!! Because the power of Storage Spaces Direct (S2D), your workloads are maximum protected and available!!

Wrap Up:

In this blogpost you’ve seen some scenarios with Storage Space Direct (S2D) in Windows Server 2019. Here you can see the high availability and resiliency of a Storage Spaces Direct infrastructure. Realy powerfull and it meets all your needs for your virtualization environment.