Instant Recovery Nutanix VM in VMware ESXi ...

[Didi7]

Hello guys,

why did Veeam choose to configure the V2V-ed VM in VMware with an E1000 instead of an VMXNET3 adapter? PowerOn and the VM works without VMware Tools or what is behind this decision?

Why not make it as an option and ask, which kind of adapter to use in the V2V-ed target machine?

Regards,
Didi7

[Didi7]

Also, I would like to add, that during migration to production the target VM in VMware ESXi has VMDKs named correctly, if there is only one VMDK attached to the VM, whereas when more than one VMDK is attached to the original VM, the naming is suboptimal.

Example 1:
One VM named TEST01 with one HDD results in a target VM with one VMDK named TEST01.vmdk (first HDD)

Example 2:
One VM named TEST02 with two HDDs restult in a target VM with two VMDKs named TEST02_3.vmdk (first HDD) and TEST02_2.vmdk (second HDD)

Why not name it correctly TEST02.vmdk (first HDD), TEST02_1.vmdk (second HDD) ?

It is even more of a chaos with more HDDs

Regards,
Didi7

[Mildur]

Hi Didi 7

Let me check if we have an option to configure a VMXNET3 NIC.
For the VMDK naming. May I ask if you have checked the names after a second restore?
Naming them _2 and _3 sounds to me like there was already a disk on the datastore with _1 and _2

Best,
Fabian

[Didi7]

Hello Mildur,

well the original VM is a Nutanix-VM, so the original name of the disk is e.g. ...

vmdisk_uuid: "3ed48547-d72b-4b9e-8216-e5c04e645a11"



And no, there was no directory, nor a disk of the migrated VM on the target VMFS lun before.

Regards,
Didi7

[tyler.jurgens]

While I would also love the option to see a vmxnet adapter rather than a E1000 adapter, this is generally done to ensure the VM comes up with working networking immediately after the instant recovery. Otherwise you would need to install VMware tools to be able to get a working network connection. If your goal is to be up "instantly" then that time matters. That said, I would love to have the option.

[Didi7]

Ok, that was my original assumption!

Nevertheless, for those who use Instant Recovery for V2V-migrations and not for fast recoveries without the need to install VMware Tools, an option to choose, which adapter type to use in the target, would be nice.

Maybe see it as some kind of feature request

The question why V2V-ed Nutanix vdisks from VMs with more than one HDD are named incorrectly, is still unknown?

Regards,
Didi7