Re-activating VBR jobs after VMs have been re-imported

[geordi]

Hi there

Due to some issues in our environment I had to rebuild some things from scratch.
Now I have the situation that VBR jobs are not recognizing anymore the VMs in the job (not available) ... the machine is on the same host as before and the host is having the same IP ... all the names are the same and also IPs.
The only thing I did was that I had to delete the VM from the ESXi inventory and re-import it.
Any thing I can do now so that VBR is recognizing that and the jobs will just work again or do I have to re-select the VMs and the next run will be a full backup?

[Gostev]

Hi, it looks like your environment rebuild process have affected unique VM identifiers that Veeam tracks all VMs with. You would have to re-select VMs, and the next run will be a full backup. Be sure to backup vCenter database to prevent this from happening in future (as this is where all unique IDs are stored by VMware). Thanks!