So apparently there is some bug with Veeam 6.5.0.109 connecting to ESX 4 servers and sure backup. It causes sure backups to fail with the “Fail Error: The object has already been deleted or has not been completely created”

They fixed it with

“After changing the protocol to 2 and removing SSH auth from the ESX 4 hosts (in our database) we were able to successfully create a new virtual lab.”

The sql statement they used looked something like this:

select * from dbo.hosts order by name asc

delete from dbo.ssh_creds

update [VeeamBackup].[dbo].[Hosts] set protocol=2 where info like ‘VMware ESX 4.%’