The object has already been deleted or has not been complete

[DonMa]

Hi everyone,

our backup always fail to find the VMs after moving them from one ESX host to another. I always get the error: "The object has already been deleted or has not been completely created"
The easiest way to resolve this problem is to remove the VM from the backup list and then readd it. It is however not very efficient because we are using vSphere DRS (VMs are moved to another ESX-Host automatically for the purpose of Load balancing) and we run incremental back up daily.
I get the same result, when the VM is migrated to another ESX and then back to the original ESX. The back up job cannot find the VM again.

Is there anyway to prevent this problem? like automatically updating the back up list?

We are using veeam backup version 8, Vcenter 5.1 and two ESX-Server (Dell Poweredge and IBM x3650)

Thanks in advance !

[Vitaliy S.]

Do you have a vCenter Server added to the Veeam backup console? How jobs are configured via containers or you've added your VMs explicitly?

[DonMa]

we created a backup job and added the VMs explicitly (the ESX Server were shown and we got to choose, which VMs we want to backup)

No vCenter Server was added.

[Vitaliy S.]

This is the issue, you need to use vCenter Server connection in the Veeam B&R server to make your backup jobs "vMotion-aware". With standalone hosts every time you migrate the VM, it receives new moref ID, and makes 3rd party software treat it as new VM.

[doboscs]

Hi,

i have the same problem and we use only vcenter server connection.

We are using Veeam 8.0.0.2084 & Vcenter 6.0.0

Thanks!

[Vitaliy S.]

Can you please tell us if you did any migration/restore tasks for these VMs by any chance? How many VMs are affected by this behavior?

[doboscs]

We have 4 affected VMs, on backup job in "Virtual Machines" section when i push recalculate i see the vm size is 0. Under the discovered VMs section (Veeam Virtual Machines section)i see the affected VMs.
We us DRS in vmware with vcenter & if the VMs is moved to another esx server the backup going to fail.

[veremin]

If VMs are added to backup jobs through vCenter connection, migration should not result in such behaviour. So, kindly, reach our support team to investigate it closer. Thanks.

[Vitaliy S.]

While you're investigating this unexpected behavior with our support team, you can re-add these VMs to the backup job, map them to existing backups and continue protecting them with backup jobs.