Advertisements

Fail Error: The object has already been deleted or has not been completely created #VEEAM 6.5.0.109

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.%’

Advertisements

One Response

  1. Hi! Great post – I wanted to let you know that this issue has been fixed in this patch: http://www.veeam.com/kb_articles.html/KB1714

    Thanks!
    -Ben Milligan (Veeam Software)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: