Migrating to new HyperV host

[codylittle]

Hey All,

Just a bit of background, migrating from one HyperV cluster to another in a new untrusted domain.
I've read through the following:
microsoft-hyper-v-f25/moving-hyper-v-gu ... 18216.html
microsoft-hyper-v-f25/migrate-to-a-new- ... 41725.html

We would ideally like to reuse our existing backup jobs and backup disks.
From reading those other posts I'm aware that the UUID needs to match.
However, I'm unsure if this is the HyperV UUID (which will match if the VM is imported inplace) or if this is a Veeam internal UUID (since it was mentioned possibly editing the DB).

Will replication with permanent failover allow us to migrate our VMs to the new cluster without requiring a new backup chain?

Regards,
Cody

[Mildur]

Hi Cody

No, a replica VM is a new VM.
For HyperV, you have to use SCVMM or hyperV Cluster. Then Veeam can track the VM between multiple hosts.
With standalone hosts, this is not possible.

Editing the DB could be a solution, but it‘s unsupported. I can not provide the steps for that, but there is a db editing post in the forum for vcenter vms which you could check. I suggest to use supported way with sccm or a cluster instead of using database editing.

Thanks
Fabian

[codylittle]

Hey Fabian,

Thanks for the info.
So here's my new plan:

Move all the VMs onto a single Host1.
Remove Host1 from the current ClusterA.
Add Host1 to new CluserB.
Move VMs onto a new Host2.
Remove Host1 from ClusterB.

Does this sound functional or just a pipe dream?

Regards,
Cody

[Mildur]

Migrating VMs from Cluster A to Cluster B will lead to Veeam seeing them as new VMs.
The migration must happen within the same cluster to be able to continue the backup chain.

Thanks
Fabian

[codylittle]

Thanks Fabian, I guess we'll just need to look at starting new backup chains (: