ESX to HyperV, no D: drive

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
MichaelMcNally
Posts: 2
Joined: Thu Dec 03, 2020 8:42 pm

Thu Dec 03, 2020 8:49 pm

I exported a Windows 2012R2 server from ESX 6.0 to Hyper-V (server 2019). The system boots and everything works but the export did not include the D: drive from the 2012R2 server.
The D: drive in VMWare is a separate VMDK file but is stored on the same datastore.

For now, I'm manually copying the data from one server to the other using Robocopy. I'm wondering though is there a way to make sure that all disks are copied when converting?
Top
MichaelMcNally
Posts: 2
Joined: Thu Dec 03, 2020 8:42 pm

Thu Dec 03, 2020 10:38 pm

Well, it turns out that the drive was copied. In the 2019 Hyper-V server, the drive was offline. Set it to online and all was good.
That was unexpected.
Top
yaroslav (staff)
Staff
Posts: 2340
Joined: Mon Nov 18, 2019 11:11 am

Fri Dec 04, 2020 6:42 am

Hi Michael,

So, was the issue resolved?
Top
Post Reply

Return to “StarWind V2V Converter, P2V Migrator”