Skip to main content
Question

Remapping backup with AHV?

  • February 2, 2026
  • 4 comments
  • 24 views

Hi team

Can someone shed some light on this and how best to go about it.

We have Nutanix cluster A and Nutanix cluster B.
VM have been moved from cluster A with Nutanix Move, which creates a new VM on cluster B and syncs data. My guess is that it creates a new UUID

There is an existing backup to a Wasabi Repo from cluster A.
How can I re-create/re-point the backups that are on the repo so that the copied VM on cluster B can continue to use the backups already there?

I am not so sure if there is a remap function for this. I also cannot add vm from the new cluster to the existing job as it only allows me to select existing one. It appears that you select cluster first when creating the job.

My guess is I may have to create a new job and let old one age out?

4 comments

lukas.k
Forum|alt.badge.img+13
  • Influencer
  • February 3, 2026

Hi ​@gravelrider,

I haven’t used AHV for a while but as far as I remember you’re right and Veeam uses the UUID of each VM for identification.

If I remember correctly then Nutanix creates new UUIDs with a Nutanix Move since you leave a cluster (to another cluster) and the UUID has something to do with the cluster as well.

You can either work with clusters (select a cluster first, than the VM) or you can work with Nutanix Categories (aka “vSphere Tags for AHV”) - but this is also cluster-based!

 

I’d go with the most simple approach you already mentioned and - in case you got the repo capacity - let the old backups age out while backing um the moved VM with a new / different job.

 

Best

Lukas


AndrePulia
Forum|alt.badge.img+9
  • Veeam Vanguard
  • February 3, 2026

@gravelrider Which Hypervisors your are running on AOS? source and destination?


  • Author
  • Comes here often
  • February 3, 2026

Hi ​@AndrePulia Both are AHV


AndrePulia
Forum|alt.badge.img+9
  • Veeam Vanguard
  • February 4, 2026

Hi ​@gravelrider as Lukas siad, a new ID is created when moving VMs and as far as I know, there is no supported way to change the VM ID, but if you really need to keep it the same, you can try using virsh/libvirt, but I think, as you mention, it will be better to create a new one and leave the old age out. 

I would suggest you to open a support ticket before try to manually change the UUID.