While you can backup just a Hyper-V Host, we strongly advise against it since you lose out on a lot that Servosity Backups offer.
Backups of a Hyper-V Host work as any other backup however, here are some limitations with just backing up a Hyper-V Host and not the VM's:
-
You can't virtualboot the VMs locally if they're backed up this way
- We don't have an images of the VM's themselves only copies of the Virtual Hard Disk files
- Those VHD's can be restored and connected to a VM but there is no way for us to Virtualboot them
-
Backups running on the host volumes can cause the VM's to be paused while a VSS snapshot is taken for the backups
- To take images of the host volumes, the running VM's might be paused or experience issues when VSS is called on the host
-
You cannot boot any of those hosted VMs in the cloud
- Similar to above, we only have copies of the VHD not backups of the VM's themselves so we won't be able to boot those VM's in the cloud
-
Booting the host in the cloud is useless because the cloud VM cannot run any of the VM's contained within it
- Since Cloud booting works by spinning up a VM in the cloud, our running VM of a Hyper-V host cannot run VM's within it
-
Our team would be unable to assist with any restores of the client VMs, just of the host or its files/folders.
- Our team is only trained in restoring files using our Backup images, they won't be able to assist with mounting a VHD and restoring files in that way
Due to these limitations, we strongly advise against running backups solely on a Hyper-V Host. If the Hyper-V host has some other roles that need to be backed up, we strongly recommend backing up the Host and any other VM's that are crucial for that company.
If you have any questions about this, please feel free to reach out to us at Support@Servosity.com.