Job failed: <VM name> is no longer processed by this job

[malenkijrobot]

Hello,

we are running Veeam B&R v8 (patch 2b build 2030 installed today) with vSphere 5.5

All of a sudden, the daily backup job (rev. incremental) shows all the VMs "failed" during the job execution, with this message "VM_NAME is no longer processed by this job. Make sure this change is intentional"
The jobs ends without any backup completed. Checking for the job's properties, we are not able to recalculate the correct size of the data payload.

The only change we made today, was modifying the vSphere ESXi names in the vSphere inventory (they were added by the IP address, and we rejoined by the FQDN/hostname).
Even after a rescan, and even after we re-joined them via the IP address, it looks like the backup job is no longer able to communicate correctly with the vCenter and/or the ESXi servers.

Is there any way to correct the existing jobs (we have a couple of weekly backup jobs, too) or should we just recreate them from scratch?

--
m.

[Vitaliy S.]

Hello,

Every time you re-register hosts (including VMs located on these hosts), all VM receive new moref ID from the vCenter Server. So after this action all VMs are treated now as new ones.

You can try to contact our technical team, as they might be able to assist you depending on current situation you have > VM moved to new vCenter

Thank you!

[malenkijrobot]

Hello and thanks for your reply.

We opened a ticket with Veaam support.

Thanks

--
m.

[malenkijrobot]

Hello everybody,

long story short: the support engineer confirmed that the best thing to do is re-add the VMs to each job, since their ID is changed each time the vCenter is somehow modified.
Synthetic full is recommended.

Backup running now ...

--
m.

[Vitaliy S.]

Thanks for the update. Re-adding VMs does help, however the trick that has been mentioned above should also do its job.