foggy wrote: However, what you could probably do is asking support for assistance in editing Veeam B&R database to reflect the migration so that jobs could continue normally.
I had already done that before posting this. The support technician that worked my ticket, unfortunately, didn't believe there was any way to do it. I figured I might have better luck posting on a forum where it might be seen by people who have some ideas how to do it, instead of simply relying on one person's experience.
I'm a firm believer that just because something hasn't been done before doesn't mean that it is impossible. This theory is based on another theory that anything is possible depending on how badly you want it.
Since we don't have the space or time to create new full backups every time we move a VM, I figured other people might have had the same requirements/experience and would be willing to contribute to a solution. I certainly am.
In the meantime, we are performing backups from our replicas (provided by Hyper-V, not Veeam), which all reside on a single machine. This appears to be a good workaround as we can move machines among the source machines, but the replicas always stay in the same place. We only seem to have minor issues with resource locking, etc. that clear themselves up on a retry. Better than before, but still not exactly ideal.
If anyone wants to take a crack at this with me, please let me know.