HyperV to VMware

[Ciso_2021]

Hi guys.

We have one customer who always used different backup system with theirs hyper v.
We took over theirs ict infrastructuur and we want to migrate theirs infrastructure from hyperv to VMware and also we want to sell them veeam license.
Can we migrate the hyperv VM to VMware with the free edition of veeam or we need a payed version ?
They are at hyperv2016 I don’t know if this compatible with the free version of veeam to restore it to VMware 7.x
Last question is, if the backups are encrypted and we lost the encryption key. There is no way to decrypt them?
When the backup is encrypted with key can / could it be encrypted by the ransomware if it get attacked ?

Thank you for your answers

[Regnor]

Technically you can migrate VMs from Hyper-V to VMware via Instant Recovery. In order to finalize the process you'll have to Storage vMotion them to your production storage.
But please be aware that you're not allowed to provide your customers any services with the free Community edition; this would violate the license terms.

Regarding encryption. If you lose the encryption password/keys, then no one will be able to restore those backups. As an additional security, with Enterprise Manager you can create recovery keys.
And no, encrypting backups won't protect from ransomware as the backups are still regular files.

[Ciso_2021]

Thank you for your answer.
So we have to order a license before we start doing the migration.
When you says vmotion, do you mean from the veeam server to the VMware server.

[Regnor]

During the Instant Recovery process the virtual disks will be provisioned from the backup storage.
So to finalize the process, you'll have to move the disks to the production VMware storage.
If you have the right VMware license you can use Storage vMotion, if not you'll have to do the migration offline.

[Ciso_2021]

Thank you for your answer.
the VM that will be restored on the VM, does it needs to have vMware tools installed before ?
i dont want to have any dead blue screen or anything.


thank you

[Regnor]

I would install the VMware Tools afterwards. That way all the necessary drivers get installed correctly.
Just be aware that if you're planing to use the VMXNET3 NIC, the VM won't come up online on the first boot as it has no network connection. Same goes for the pvSCSI adapter.

[Ciso_2021]

Thank you for your answer.
before we want to start the migration, i have created a hyper v server at our LAB and created a server 2016, ive backed it up with our production VEEAM and restore it to the vMware.
unfortunately the VM is not booting up with the error "inaccessible boot device".

[Ciso_2021]

We got it sourted out.
Thank you

[Ciso_2021]

One issue noted, during the Instan Recovery the restore is really slow 20MB/S.
the VEEAM is in the Vmware Server and the storages are SSD.
The bottelneck is Target
the VM is 1TB big but its taking ages.
when i took the backup over the physical 1GB network on the LAB it went quick with 160MB/S.
The VEEAM has 10GB VMXNET3 with the latest installed vMware Tools.
any suggestins what could be the cause?

Thank you

[Ciso_2021]

I don’t mind leaving it’s running for a day. My concern is as long as the vm is migrating.
Can our users works and the changes they’ll breng to theirs files will be migrated too ?

[Regnor]

Bottlebeck target looks like your either your production/VMware storage is too slow or, depending on how you access it, the connection is the problem.
If you have Storage vMotion licensed, the users will still be able to work, but the performance is going to be degraded.
Without Storage vMotion the VM needs to be offline.

[Ciso_2021]

I am testing this on a single VMware host without vcenter to use vmotion.
When you days the vm needs to be offline do you mean power off the mounted vm when it’s mounted ?

[Regnor]

Yes, without Storage vMotion the VM needs to be powered off before you can move it to a different storage. In that case you could also try to use Quick migration: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

[Ciso_2021]

Thank you for your answer.
do you mean the original VM or the one on the backup ?

[Regnor]

At least the restored VM needs to be offline during the migration.
And probably you will also want to shutdown the original VM to prevent anyone working on it or doing changes. If you keep let it running, you'll have a gap between the original and restored VM.

[Ciso_2021]

I have tried it and shut both down ( the original and the one that got published during the mount )
After it’s migrated it shows inaccessible boot device with blue screen.
Tried to install VMware tools on the VM but somehow hyper V doesn’t allow it to be done on its VM.
I hope someone with a clue why this happens to me.

[Regnor]

Take a look at this article. http://woshub.com/bsod-error-0x0000007b ... 7-2008-r2/
I've seen this issue sometimes when converting agents to VMs and it could be solved by enabling the missing drivers.

[Ciso_2021]

Thank you for your answers.
we have managed to get the issue resolved with vMware. appear something with LSI drivers ect...
now we have the the VM al over on ESXI running fine, however when i add the VM to the daily job it errors out "veeam cannot add volumes to the snapshot "
after checking the rss i see
do i have to remove those Hyper IC Software ?

after deleing the Hyper VSS

Code: Select all

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{74600e39-7dc5-4567-a03b-f091d6c7b092}]
@="Hyper-V IC Software Shadow Copy Provider"
"Type"=dword:00000002
"Version"="1.0.0.0"
"VersionId"="{c797fff9-2c3e-453c-a3e9-cc7673a6c732}"

the backup is working

just want to inform if someone else may have this issue