Veeam backup error: TASK FAILED

[logos]

Goodmorning,

I had an error inside my Veeam environment. This error came out after an our maintenance we did to a customer.
To be precisely we have moved the Vcenter VM from an ESX to another for some tests and then we have moved back to the primary. At now veeam in his schedule gives this error:

Task failed Error: Object VCENTER not found.

We have checked if the VM was in the correct ESX because we have a license for only one and there was.

Could you help me to understand this error?

I'm sorry if this is the wrong place to open an issue, in that case, could you explain me how to do it?

Thanks all

[foggy]

For any technical issue, you should open a support case using our support portal (step-by-step instructions are also provided when you click New Topic).

Btw, seems that vCenter VM ID has changed after its migration. Veeam B&R tracks VMs by their unique moref ID. Every VM re-registeration in the virtual infrastructure (like on moving VM between standalone hosts) changes this identifier causing the VM to be treated as a new VM. How did you move the VM to another host?

[logos]

i explain you all my scenario:

- We have 2 ESX configured in cluster.
- All Our VM are inside ESX2
- To do a Failover test, we disconnect AC Power cables to the ESX2
- All VMs were migrated to ESX1.
- We powered on ESX2 and we Have moved manually all VMs from ESX1 to ESX2

This is what we did.

The strange thing is that all VMs exept the Vcenter work normally.

i have 2 possbile ideas:
- Try to change this UNICE ID that Vcenter has (if it is possible)
- Try to remove and add again the Vcenter Backup Job

otherwise must i do something else?

Thanks in advice

[veremin]

So, you're trying to say that every other job (apart from vCenter one) works as expected, aren't you? Then, you can recreate corresponding vCenter job and map it to the existing backup.

Thanks.

[logos]

So, you're trying to say that every other job (apart from vCenter one) works as expected, aren't you?

Yes it's right.

Then, you can recreate corresponding vCenter job and map it to the existing backup.

Ok. i'll try to do it.

Thanks.

[Cokovic]

I assume that you backup your vCenter directly from the host right? If so then a vMotion and even a storage vMotion is going to change the unique ID of the VM and you have to remove and readd the VM in your job.

For the other VMs i assume you have selected them over your vCenter in your job config and this will prevent the unique ID to change in such case.

[logos]

I configured a new backup Job. Now it seems working.
Now my question is: If the Vcenter moves to another ESX i always must recreate Veeam Backup job?


Thanks in advance

[veremin]

Adding virtual machine through standalone host makes a backup/replication job vMotion-unaware, thus, after migration has taken place, it’s always necessary to recreate a backup/replication job. Thanks.

[logos]

Thanks for all.
Now i recreate the job and it works fine.
if someone need the solution:

SOLUTION TASK FAILED ERROR: just remove and recreate backup Job for the VM.

Thanks again. Have a nice day


Nicola

[veremin]

You’re welcome. Should any additional help be needed, don’t hesitate to let us know. Thanks.