Backup & Recovery

Could it then be a permissions error? Do you get the same error if you add the vCenter in Veeam with an AD account granted administrative permissions? This would probably be something better to post on the Veeam forums rather than here.

Even though using an administrative AD account, the error persists, vCenter is integrated with AD, the hosts are not.
But I tested the hosts individually in Veeam, using the root user, then I try to perform a direct backup of the host, the error persists.
I put it on the Veeam forum, but so far no response.

What account exactly are you using? And can you show a screenshot inside vCenter where it lists its permission?

As I said before. I am using the account administrator@vsphere.local, vCenter was added in Veeam with this account.
Right at the beginning, I created a Veeam account with Administrator permission, it did not work, so I started to use the account administrator@vsphere.local
I am sending the image with users and feeds permissions.

I wait and thanks !

If you login to vCenter with administrator@vsphere.local, can you take a snapshot of any VM? See also this post. Also look at this post that discusses free space on the datastore where the Veeam proxy resides in comparison to the disk to be processed.

Yes, the snapshot occurs normally, there is also enough space in the Veeam Repository, Veeam Backup and Veeam Proxy are on the same machine, it is a Dell physical server with 48GB of RAM.

I am sending two more images with a test I just made, trying to backup a single virtual machine.

Thanks for your avalaiable

I'd recommend opening a support case with Veeam for this issue. After some research, there are various conditions which can produce this result and without logs and analysis it's impossible to tell. Their support is very good and should be able to help you out. If/when you log a SR, put the number in your post on the Veeam forums.

Okay, I'll do it again.

Thank you !

Problem solved. Following the guidelines of Veeam support, I installed the Microsoft Visual C ++ 2008 Redistributable Package (x64), then I performed a backup and it worked.

Greetings !

Hello Ivanildo, did it need to be specifically 2008?  On our backup server we already have Microsoft Visual C++ 2005, 2010, and 2013 Redistributable Packages installed and our backups started failing with this error this week.

amigo , estou com mesmo problema para restaurar um backup do instant recovery.

Você apenas instalou o Microsoft Visual C ++ 2008 Redistributable Package (x64) ?

fico grato se responder.

I had the same error. Changing the parameter Config.Defaults.security.host.ruissl to true helped me (Host --> Configure --> System --> Advanced System Settings):

hello, can you tell me where such a window is located?

 I know this is years later but still I wanted to send you a quick "thank you!" because you have saved us from a major headache. This has solved our issue, finally. You're awesome. No idea why our backups suddenly started failing, they worked before, we didn't update veeam or ESXi/vCenter nor did we change that settings but they just suddenly stopped working. Strange but at least it's resolved now

Good Day! 

sorry for jumping here, but I need your assist if you don't mind. 

I have the same error "Failed to open VDDK disk" and during the last few days I was trying to troubleshoot based on the solutions provided above, but the same error still happen. 

during your troubleshooting, did you try something else?? 

thanks a lot. 

I had a similar error. This is a new setup. And the solution for me was to enable vmkernal services on the network adapter reachable from veeam server. On every host. I think it is either vMotion or Provision weeam use. Be careful when changing in production:

You are a life saver

Tank you ! For your quick solutions

There are multiple troubleshooting 

1. Remove problematic vm from backup and re-initiated backup

2. vmotion vm on other host then try backup

3. disable proxy (https://communities.vmware.com/t5/forums/replypage/board-id/2004/message-id/18131)

4. making a new job