I had a strange problem with one of my VM’s. The VM-ID was changed and this change was not forwarded to my vCenter server. I use Veeam Backup for creating backups and the job skipped this VM with the following error:
This problem can be solved by restarting the services on the ESX server and the vCenter server.
The following command will do this on the ESX Server.
service mgmt-vmware restart
For vCenter (Windows) you can do this from the command line:
net stop "VMware VirtualCenter server"
net start "VMware VirtualCenter server"
After restarting the services, the backup job completed successfully.
2 thoughts on “Veeam Backup: VM “vmname” (ref: “vm-##”) is “invalid””
Wow! Thank you! I always wanted to write in my site something like that. Can I take part of your post to my blog?
Hello Guru, what entice you to post an article. This article was extremely interesting, especially since I was searching for thoughts on this subject last week.