Backup Hyper-V Host | What Does It Mean & Is It Necessary?
In most cases, backup Hyper-V host is not necessary. In this article I will elaborate 3 reasons that support this view, and explain what will be stored if you backup Hyper-V host.
What does Hyper-V host backup mean
Hyper-V is Microsoft's free, enterprise-class, and Type 1 hypervisor that runs directly on physical hardware and creates and manages virtual machines without an underlying operating system. The physical hardware is called the host.
Unlike host-level backups, backing up a Hyper-V host means preserving hypervisor settings such as storage, networking, roles, permissions, and virtual switch configuration.
Should you backup Hyper-V host?
The choice of whether to back up the Hyper-V host is based on your own needs. However, in most cases, there is no need to back up the Hyper-V host because what really matters are the backup of virtual machines. Here are some reasons not to back up the Hyper-V host.
Reasons why no need to backup Hyper-V host
◆ Reason 1: Reconfiguring Hyper-V host is quick and easy
Ideally, there should be only clients on the Hyper-V host. Therefore, reconfiguring a Hyper-V host is a very simple and quick process that takes only a few minutes to complete. At the same time, restoring a Hyper-V host can take a long time and waste storage space.
◆ Reason 2: There is no direct way to backup Hyper-V host
Unfortunately, there is no direct and easy way to backup Hyper-V hosts. You can only choose some workarounds, for example, exporting configuration information through Powershell.
◆ Reason 3: Virtual machines should be flexible to migrate to other hypervisors
Virtual machines should be independent and not rely on the Hyper-V host, so that you can easily restore or migrate them to other hosts, or even other hypervisors. Hyper-V is just one of these platforms.
Workarounds to backup Hyper-V host configuration
As stated before, there is no direct way to backup Hyper-V host. In most cases, backing up Hyper-V virtual machine itself is enough to restore all essential data.
But if you think that based on your situation, reconfiguring the Hyper-V host will take a lot of time, or if you have a situation where you need to ask someone else to restore and operate your virtual machine, then you may want to look for some workarounds for backing up Hyper-V host.
You can retrieve and save your Hyper-V host information via Powershell for later reconfiguration. Here are some basic Powershell cmdlets you can use:
- Retrieve Hyper-V host information. Running just the Get-VMHost cmdlet will return the least default information, so you need to run the Get-VMHost | fl cmdlet to get more.
Get-VMHost | fl
- Retrieve the storage configuration of the Hyper-V host.
Get-Disk
Get-Partition
Get-Volume
- Retrieve the physical network adapter configuration.
Get-WmiObject -Class Win32_NetworkAdapterConfiguration -Filter IPEnabled=True
- Retrieve the Hyper-V virtual switch configuration.
Get-VMSwitch
Besides, if you want to migrate your Hyper-V virtual machine to another host, or even other hypervisors, Hyper-V Manager provides a very convenient built-in feature. You can right-click on your virtual machine and select Move to open the Move wizard.
Backing up Hyper-V VMs to protect your VM data (Free)
As I mentioned before, it's not a must-step to backup Hyper-V host, backing up Hyper-V VMs is what really matters. After all, this is where your critical business data are placed.
Besides, backup VMs once is not enough. If you want to keep up-to-date backups or multiple restore points, you still need to take backups regularly.
Here I introduce you to a free Hyper-V backup software -- AOMEI Cyber Backup. It can automatically backup multiple Hyper-V VMs, and clearly list all restore points.
Next I will demonstrate how to quickly create a complete backup task of multiple Hyper-V VMs in 3 simple steps. You can click the following button to download the freeware.
*You can choose to install this VM backup software on either Windows or Linux system.
3 simple steps to backup multiple Hyper-V VMs
1. Bind Devices: Access to AOMEI Cyber Backup web client, navigate to Source Device > Hyper-V > + Add Hyper-V to add a host. And then click … > Bind Device.
2. Create Backup Task: Navigate to Backup Task > + Create New Task, and then set Task Name, Backup Type, Device, Target, and Schedule.
- Device: cover multiple VMs on the host in one backup task.
- Target: selecting to back up to a local path, or to a network path. Used paths will be saved in Favorite Storage for handy selection.
- Schedule: choosing to perform full or incremental backup, and automate execution daily, weekly or monthly according to the frequency you specified.
3. Start Backup: Click Start Backup and you can select Add the schedule and start backup now, or Add the schedule only.
Created backup tasks will be listed and monitored separately, for progress checking, schedule changing and restoring.
While the Free Edition covers most of VM backup needs, you can also upgrade to enjoy:
▶ Backup cleanup: Configure a retention policy to auto delete old backup files and save storage space.
▶ Restore to new location: Create a new VM in the same or another datastore/host directly from the backup, saves the trouble of re-configuring the new VM.
Summary
In this article, I analyzed 3 reasons why backup Hyper-V host is not necessary in most cases. The most important thing is always to back up Hyper-V VM itself, in which you can restore entire VMs with almost all the essential data when needed.
But if you think that based on your situation, reconfiguring your Hyper-V host will take a lot of time, or if you have a situation where you need to ask someone else to restore and operate your VM, then you can export your host configuration via Powershell. But it may be a waste if you spend a lot of time and effort on backup Hyper-V host.