Backup says VM is unavailable

[patrickwilson412]

Hello,

I recently tested migrating one of my VM's from one ESXi host to another. Even though I've moved it back to the original host, the Backup fails and I'm getting an error stating the VM is unavailable. Is there a way to fix this other than re-creating the job?

[Egor Yakovlev]

Hi Patrick.

Were those hosts in a same vCenter or standalone ones?
If later, than MoRefID change is expected by VMware, thus VM with new ID is treated as New.
Re-add it to the backup job and it will be processed again.

/Thanks!

[patrickwilson412]

Yes, both hosts are in the same VCenter.

I'm sorry but I don't understand what you mean by this. "If later, than MoRefID change is expected by VMware, thus VM with new ID is treated as New.
Re-add it to the backup job and it will be processed again."

[foggy]

Hi Patrick, how exactly did you perform the migration? vMotion shouldn't result in such behavior as it preserves the VM ID. If the VM ID changes, then Veeam B&R treats the VM as a new one - in this case you need to re-add it to the job again to continue backing it up (please mind the full VM data read).

[patrickwilson412]

I did it through vmotion. I'll try re-adding it to the job. Thanks.

[foggy]

Then this is unexpected. Seems that at some point VM IDs have changed.