after hours of tshooting, I already fixed issue above.
Here it is what I do:
1. You should know the datastore where VM was stored.
2. Remove VM from inventory
3. Create new VM as usual. But instead of creating new VMDK disk, we should choose 'use existing disk'. So, choose previous VMDK file. Then follow the wizard till the end.
Here is the link for reference about this case:
3 people found this helpful
As an aside; I was having this problem over the last couple of days. I vMotioned the server to another host and retried the Veeam backup and it succeeded. Might be a little less effort than rebuilding the VM from the VMDK.
1 person found this helpful
This worked, thanks. In my case, it seems that it started after trying to migrate a machine to another host during a partly system inconsistency (a storage connection was gone for a moment, I wanted to "rescue" the VM to another host but this seems to have caused that this error in Veeam)