Backup job failed after host is moved to another VMWare clus

[CoffeeCup]

Hello,

We are running around 70 backup jobs from VMWare cluster. Every time after VM is moved from host to host within cluster or relocated to different datastore the backup job failed with the error message “Task failed Error: The object has already been deleted or has not been completely created”. It’s easy to fix by re-adding the VMs to the backup job but could be time consuming.
Is this error related with incorrect job setup or it’s just the way Veeam works? Is there any way to get rid of this issue or faster way to fix it instead of re-adding the VMs to backup job?

Thank you

[csinetops]

That doesn't sound right. We Vmotion VM's between hosts and or data stores all the time in our cluster and the jobs run without issue.

I'd open a support case so they can check your settings etc.

[foggy]

Are you adding VMs to the jobs by selecting them under vCenter server?

[CoffeeCup]

No, historically all jobs were added by selecting the specific cluster host - that is why I think the way the jobs are setup is the reason for this issue. Should all the jobs be added via vCenter?

Thank you

[foggy]

Yes, that way they will be vMotion-aware.

[CoffeeCup]

Thank you, I'll set the test job via vCenter and re-test it.