VM is no longer processed by this job.

[Maieu_san]

Hi all,

I have something strange. It's not really a problem, but the message has me confused.

I have a backup job with 1 VM in it. Backup job runs successfully, so that's not the problem.
But, in the actions I see the following:
Building VM list
"VM Name" is no longer processed by this job. Make sure this change is intentional
VM size
Changed block tracking is enabled
Preparing next VM for processing
Processing "VM Name"

it says in the acions that the VM is no longer processed by the job, but a few lines lower it starts processing the same VM and the backup runs successfully.

Can someone explain this to me?

thanks in advance!

best regards,
Steven

[foggy]

Steven, have you probably re-added this VM to the job recently? Is it added as an individual VM or via some sort of VM container (folder, for example)?

[Maieu_san]

Hi Foggy,

Thanks for the quick reply!

I have indeed re-added the VM in the Job.
The VM is added directly, not in a folder.

best regards,
Steven

[foggy]

What was the reason of re-adding the VM? Was it probably re-registered in vCenter?

This message means that the given VM (its former instance) is no longer present in the job and is not backed up anymore. The message will go away once the deleted VM retention period expires.

[Maieu_san]

I'm not sure anymore why I re-added the VM.
If I remember correctly at one point the Backup job failed with the error it could not find the VM anymore, while it was still there.
I then re-added the VM and restarted the job successfully. If I'm not mistaking, that was the reason.

But if I understand correctly, this message does not mean that the backup isn't finished successfully?

best regards.

[foggy]

The backup is finished successfully, no need to worry. Probably the VM was previously migrated or has changed it's unique ID for some other reason, causing the observed behavior.

[Vitaliy S.]

If I remember correctly at one point the Backup job failed with the error it could not find the VM anymore, while it was still there.
I then re-added the VM and restarted the job successfully. If I'm not mistaking, that was the reason.

Another reason for this might by VM migration. If you're not using vCenter Server in the backup console, then moving VMs from one host to another will cause this behavior.