This isn't necessarily a Veeam issue exactly, but being Veeam related I expect that others here have probably run into this and might be able to suggest a solution.
I have a SureBackup job set to test one VM out of our daily Veeam backup job. It spins it up on the backup repository, which is also Hyper-V host containing a couple of guests. We also have System Center 2012 in our environment, and VMM manages all of our hyperv hosts. When Veeam creates a 'new' VM each day for the SureBackup job, System Center notes the new guest and adds it in VMM. A short time later, Veeam verifies the restored VM and is running successfully, then deletes the new it. VMM still knows about the VM, but marks it as "missing" since it has been removed from the host. Every day, the process repeats, and another "missing" vm is added to the list. This ends up creating alerts in OpsMgr for each of the missing VM's as well. I go in periodically and delete a bunch of "missing" surebackup VM's, but it seems to me that there's probably something I can change in the configuration of either Veeam, VMM, or the Hyper-V host, that would stop this from happening.
Does anyone know how I can resolve this issue, rather than simply cleaning up symptoms after the fact?