Backups failing when vMotioned?

[hongman]

Hi

It seems whenever we vMotion a VM to another host, Veeam seems to "lose track" of where the VM has moved to and unless we manually delete and re-add the VM in the job, it fails.

This doesn't seem right to me? The VM's are all added via the vCenter.

[veremin]

I'm wondering what exact errors you see.

In fact, having VMs added to the job via vCenter should make the job vMotion aware. In other words, the described behavior doesn't seem to be correct; and you might want to open a ticket with our support team and let them investigate it directly.

Thanks.

[dellock6]

Any change you added the VM by crawling this tre path? vCenter -> Host -> VM. Or maybe selecting the host as the dynamic container for the job?
Because as Vladimir already told you, vCenter helps in tracking the VM when it moves, and for example storage vmotion is temporarely disabled during the job...

Luca.