Skip to main content
Question

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

  • July 7, 2026
  • 1 comment
  • 15 views

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.

1 comment

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.