Skip to main content
Question

Unable to backup a Hyper-V host due to VBR BIOS UUID error

  • July 7, 2026
  • 2 comments
  • 26 views
J

I am a first time Veeam customer trying to set up a new test environment using a trial license in hopes to purchase it. 

I have one physical HPE server that is running the Veeam VSA installed from the latest ISO file.  This is the only backup repository.  I have a second physical HPE server that is running Windows Server 2022.  This has a tape drive connected to it.  This also is the windows mount server.  I also have a laptop that I’m using just for management purposes with the console installed. I have a third physical server with Hyper-V on it.  I was having no issues backing it up but I created a new virtual machine with 2 large disks for testing and pointed it at the VSA iso file and during install chose the Veeam Enterprise Manager option.  I am not totally certain but believe this is what broke backups for me.  Now when I try to backup any of the virtual machines on this Hyper-V server I get an error “Unable to detect the VBR BIOS UUID. This error likely appears because the Veeam Software Appliance cannot be added to backups jobs to protect itself.”  I have since deleted that VM but still cannot back up any of the other standard windows VMs on that host.  I have removed that physical server from VBR and even uninstalled the agent and all components and reinstalled everything.  I still get the same error.  Any assistance is appreciated. Thank you.

      2 comments

      matheusgiovanini
      Forum|alt.badge.img+9

      Hi,

      Maybe this KB can help as a starting point:

      https://www.veeam.com/kb4205

      It explains that Veeam uses the BIOS UUID to uniquely identify machines, and issues can happen when the UUID is duplicated, missing, or detected incorrectly.

      Since your error mentions “Unable to detect the VBR BIOS UUID” and the VSA possibly being included in the backup job, it may be worth checking for any stale inventory reference or UUID conflict.

      That said, as this involves the Veeam Software Appliance and may require checking the VBR configuration/inventory, I think it would be better to open a Veeam Support case as well.

      Matheus Giuliano Giovanini | Senior Backup & Data Protection Engineer | Tech Lead | Veeam Legend | Blog: techdirectarchive.com
        J
        • jerrypanski
        • Author
        • Not a newbie anymore
        • July 8, 2026

        Hi Matheus, I read that article but haven’t found anything that has helped me fix this particular issue.  To add some more detail, I am able to backup the Hyper-V host itself which I would imagine I wouldn’t be able to.  I do see the UUID is not null on the server.  I am just not able to backup any virtual machines.  I even created a brand new VM thinking that should have no issues but it also fails with the same error.  I know 3 things I did that may have caused such an issue.  As I’m learning the product, I now know these things aren’t right but figured they would be easy to clean up.

        1-I originally added the host as an IP address.  This is because it was a test environment without DNS properly set up and figured it would just be a quick and easy way to test backups/restores.  I’ve since set up DNS and added it as the FQDN.

        2-I had it in 2 protection groups at once accidently.  I have since cleaned up everything on both sides.  On the host side I have even tried uninstalling everything and removing C:\Programdata\Veeam, reg keys, etc.  After reinstalling still no luck.

        3-I created a VM on this same host server using the VSA Iso file and choosing the second option to install Enterprise Manager.  I think this is what caused my issues.

        I read this article: 

        and it sounded like replacing Windows based Enterprise Manager with the appliance is the right thing to do.  I figured since it was a new test environment might as well test it.  Unfortunately, I think this is what caused all my pain.  It seems to see it as the VSA itself even though that VM is now completely deleted.  I would imagine this is supported but maybe not?  How would I check for any stale inventory reference outside of what’s listed in the VBR inventory?  Is there a way to check the Veeam database?  I guess I will open a ticket if that is allowed during a trial period. Thank you.

        Terms & ConditionsAccessibility statement