Veeam, can you please re-visit and consider this (extremely useful) feature request?
Still hitting all the previously mentioned issues when migrating VMs in smaller setups from one standalone Hyper-V host to another (hardware upgrades, OS upgrades etc).
Also saw another related post where this was achieved by hackling the identifiers within the Veeam backup database to try and resolve these issues. We had looked at this previously (and saw the way to do it) but ultimately that would leave our customers in unsupported territory if something went wrong. It does however show that re-mapping should be possible within Veeam and just needs to be implemented etc.
Can Veeam please look to implement a Hyper-V VM re-mapping tool within the UI (similar to how you can re-map backup chains) for when this need arises?
Still hitting all the previously mentioned issues when migrating VMs in smaller setups from one standalone Hyper-V host to another (hardware upgrades, OS upgrades etc).
Also saw another related post where this was achieved by hackling the identifiers within the Veeam backup database to try and resolve these issues. We had looked at this previously (and saw the way to do it) but ultimately that would leave our customers in unsupported territory if something went wrong. It does however show that re-mapping should be possible within Veeam and just needs to be implemented etc.
Can Veeam please look to implement a Hyper-V VM re-mapping tool within the UI (similar to how you can re-map backup chains) for when this need arises?
Statistics: Posted by bytewiseits — May 01, 2025 12:59 am
