MENU
Windows Server 2016 Hyper-V Backup Rises to the challenges
Posted by Didier Van Hoye on September 19, 2016
4.5/5 (2)

Introduction

In Windows Sever 2016 Microsoft improved Hyper-V backup to address many of the concerns mentioned in our previous Hyper-V backup challenges Windows Server 2016 needs to address:

  • They avoid the need for agents by making the API’s remotely accessible. It’s all WMI calls directly to Hyper-V.
  • They implemented their own CBT mechanism for Windows Server 2016 Hyper-V to reduce the amount of data that needs to be copied during every backup. This can be leveraged by any backup vendor and takes away the responsibility of creating CBT from the backup vendors. This makes it easier for them to support Hyper-V releases faster. This also avoids the need for inserting drivers into the IO path of the Hyper-V hosts. Sure the testing & certification still has to happen as all vendors now can be impacted by a bug MSFT introduced.
  • They are no longer dependent on the host VSS infrastructure. This eliminates storage overhead as wells as the storage fabric IO overhead associated with performance issues when needing to use host level VSS snapshots on the entire LUN/CSV for even a single VM.
  • This helps avoid the need for hardware VSS providers delivered by storage vendors and delivers better results with storage solution that don’t offer hardware providers.
  • Storage vendors and backup vendors can still integrate this with their snapshots for speedy and easy backup and restores. But as the backup work at the VM level is separated from an (optional) host VSS snapshot the performance hit is less and the total duration significantly reduced.
  • It’s efficient in regard to the number of data that needs to be copied to the backup target and stored there. This reduces capacity needed and for some vendors the almost hard dependency on deduplication to make it even feasible in regards to cost.
  • These capabilities are available to anyone (backup vendors, storage vendors, home grown PowerShell scripts …) who wishes to leverage them and doesn’t prevent them from implementing synthetic full backups, merge backups as they age etc. It’s capable enough to allow great backup solutions to be built on top of it.

Let’s dive in together and take a closer look.

Windows Server 2016 Hyper-V backup
(more…)

Please rate this

Hyper-V backup challenges Windows Server 2016 needs to address
Posted by Didier Van Hoye on September 12, 2016
4.75/5 (4)

Introduction

Personally I have been very successful at providing good backup designs for Hyper-V in both small to larger environments using budgets that range in between “make due” to “well-funded”.  How does one achieve this? Two factors. The first factor is knowing the strengths and limitations of the various Hyper-V versions when you design the backup solution. Bar the ever better scalability, performance and capabilities with each new version of Hyper-V, the improvements in back up from 2012 to 2012 R2 for example were a prime motivator to upgrade. The second factor of success is due to the fact that I demand a mandate and control over the infrastructure stack to do so. In many case you are not that lucky and can’t change much in already existing environments. Sometimes not even in new environments when the gear, solutions have already been chosen, purchased and the design is deployed before you get involved.

Windows Server 2008 (R2) - 2012 Hyper-V Backup
(more…)

Please rate this

Don’t Fear but Respect Redirected IO with Shared VHDX
Posted by Didier Van Hoye on August 25, 2016
5/5 (2)

Introduction

When we got Shared VHDX in Windows Server 2012 R2 we were quite pleased as it opened up the road to guest clustering (Failover clustering in virtual machines) without needing to break through the virtualization layer with iSCSI or virtual Fibre Channel (vFC).

First of all, you need to be aware of the limits of using a shared VHDX in Windows Server 2012 R2.

  1. You cannot perform storage live migration
  2. You cannot resize the VHDX online
  3. You cannot do host based backups (i.e. you need to do in guest backups)
  4. No support for checkpoints
  5. No support for Hyper-V Replica

If you cannot live with these, that’s a good indicator this is not for you. But if you can, you should also take care of the potential redirected IO impact that can and will occur. This doesn’t mean it won’t work for you, but you need to know about it, design and build for it and test it realistically for your real life workloads.

active guest cluster node is running on the Hyper-V host

(more…)

Please rate this

Why moving from Windows Server 2012 R2 to 2016 for Hyper-V
Posted by Romain Serre on August 16, 2016
5/5 (1)

Windows Server 2016 will be released the next month said Microsoft the last month. Windows Server 2016 brings a lot of new features compared to the last Windows Server version for Hyper-V, networking and storage. In this topic I will try to convince you to move from prior Windows Server edition to Windows Server 2016 with eight reasons.

Virtual Server (more…)

Please rate this

Shared virtual hard disks in Hyper-V 2016
Posted by Oksana Zybinskaya on August 9, 2016
4.67/5 (3)

Datacenter

A new feature called VHD Set for Hyper-V in Windows Server 2016 has been introduced by Microsoft. It allows sharing virtual hard disks between several servers in order to implement guest cluster easily without using complex technologies such as NPIV, virtual HBA, or virtual SAN.

As VHD Set, Shared VHDX enables sharing a virtual hard disk between multiple virtual machines. This feature is useful for implementing a guest cluster where shared disks are required (e.g., SQL Server AlwaysOn/FCI or File Servers).

(more…)

Please rate this