This is how my previous post about how to run Hyper-V inside of KVM came to be. Since we were able to do instant restores of the backups into Hyper-V, we first needed a Hyper-V server to serve as a target host. Or in our case, Virtual-to-Virtual (OpenStack to Hyper-V) Instant Restore to Hyper-V

Meaning you can do a Physical-to-Virtual conversion with the use of a backup. Something that is available, is Instant Restore to Hyper-V. This option is not available for machines backed up with Veeam agent. Where you can actually start up groups of VMs with interdependencies to check that whole applications work as they should after a restore. Now, if we had our VMs running on VMware or Hyper-V, Veeam has a built-in backup verification solution they call SureBackup. Which is why we’re using Veeam Agent for Windows to backup both our virtual and our physical windows servers.

While Veeam has very good integrations with VMware, Hyper-V and Nutanix, it still doesn’t have any integration into OpenStack. So, to back up our windows servers, we use Veeam Backup and Replication. Which means we can’t just base ourselves on file backups for anything running on windows, we need full image backups to be able to do reasonably quick restores. And while we try to mostly utilize open-source solutions, there are times when that’s just not the best way to go.Ĭertain software need to run on windows server, and windows is stateful code. Our main virtualization platform is OpenStack, which is awesome. TLDR: check the script on github Windows backup on OpenStack This post is about how we’ve set that up. One of them being a way to automatically verify that our Windows server backups are functional. As mentioned in my previous post, we have some interesting projects involving Hyper-V.

Veeam backup physical server