Veeam Job fails after upgrade to vSphere 5.1

Now that vSphere 5.1 is been out a little while, there are more and more upgrades happening.  One problem that I run across while upgrading is that the Veeam backup job fails the next morning if you aren’t aware of what happens.

During the upgrade to vSphere 5.1, the ESXi servers now have a different UUID.  Since Veeam uses the UUID to distinguish objects, it now sees different UUIDs, and the backup job will fail:

Error: Host with uuid ‘37363536-3536-4d32-3231-333930315039’ was not found

In the backup logs, you will also see:

<01> Error Host with uuid ‘37363536-3536-4d32-3231-333930315039’ was not found at Veeam.Backup.Core.CHost.GetByJobsByUuid(String uuid)

One thing you will be able to do, is still browse all of the vSphere resources inside of Veeam.

The fix is actually quite simple, and should be done after the upgrade and before the next backup to avoid a failure. Otherwise, afterwards will have to do.


Simply revoke the Veeam licenses assigned to the hosts.  Under the Veeam menus (depending what version you have) select Lincense Information, and click Licensed Hosts.

Highlight the servers that were upgraded to 5.1 and select Revoke.

That’s it!  When the backup job runs again, Veeam will automatically fill in the blanks with the licensing and the new UUIDs.


No related content found.

Tags: , ,

6 Responses to “Veeam Job fails after upgrade to vSphere 5.1”

Leave a Comment

2013 | 2014 | 2015 | 2016


Voted Top 100 vBlog 2016