Do I need to re-add a VM to a VDP job list if the VM was recreated with the same name?

[scottly]

Hello, I have a question about the way VDP functions.  How does it "see" the VMs?  Does it just go through the list of VMs and match the job list with the VMs in vCenter?  I ask because one of our users requested that we delete a VM, and deploy a fresh one from scratch.  He wanted the VM to be the same name, so I wanted to know if I would have to add it to the job again?

[a_p_]

I'm not 100% sure about VDP, but VM's are usually recognized by their VM-ID, which is assigned when they are added to the inventory. So I'd expect that you need to reconfigure the backup job.

André

[scottly]

Thanks, what's strange is that it appears VDP added the annotation to the VM summary automatically after a couple minutes of the new clone being brought up.  So, it appears it saw the new VM and automatically registered it.  The test will be to see if it actually backs up tonight, though.

[rcporto]

I agree with André, and about the new VM be recognized automatically by VDP may be due the fact you deploy the VM in a folder protected by VDP, this way VDP will automatically include the VM on backup job.

[scottly]

So I found that although VDP was able to edit the Annotations of the VM, the backup fails and when I try to the job, it removes the VM and I gives me an error when I try to re-add it.  Does anybody know if simply renaming the VM will fix the issue, or do I have to actually create a new VM?

BTW, the job isn't pointed to a folder, but to the VM itself.