I understand that Veeam tracks VMs using their unique identifier in vcenter, but I wondered if there was a way to map previously backed up VMs to their new IDs in the event of a host being removed and re-added?
We had a situation last night where a host wasn’t joining back into venter after a datacenter power down - it looked like the vpxa agent was crashing - the host momentarily reconnected after selecting ‘connect’ but immediately disconnected again.
In hindsight I should have just manually reinstalled the vpxa agent, but it was late, wasn’t thinking at my best and I just removed and re-added the host to get vcenter to reinstall it for me. This got us back with a full functioning cluster and I went to bed.
The backups are due to kick off again later this afternoon, and I know Veeam will create duplicate, active full backups for those VMs registered on the host I re-added.
We don’t have a great deal of backup repository space, so I wondered if there was a way I can map these new ID’s to the existing VMs in the backup job? It’s probably worth noting that we target VM folders for our backup jobs, so new VMs are picked up automatically.