StarWind iSCSI SAN
StarWind Native SAN for Hyper-V

Conversion best practice to obtain the quickest restore time

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

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

Conversion best practice to obtain the quickest restore time

Postby steve.hulsberg » Mon Apr 29, 2019 6:35 pm

I am converting some fairly large VMs from VMware to HV. I am looking at ways to reduce the conversion time. Can you please review below to see which area needs to be changed or have resources increased?

1. 10G connection from VMware hosts to HV hosts
2. VM that Starwind converter is on is connected via 10G to VMware and HV hosts
3. Starwind VM is setup as Paravirtural, however it looks like there is no option to set a specific conversion drive, so it is running on C:\ which cannot be Paravirtural
4. Starwind VM currently resides on C:\ spin disks, however it could be reinstalled on a smaller SSD
5. Starwind VM has 32GB of memory and 8 vCPUs assigned to it
6. HV hosts have a large amount of memory on them
7. Starwind HV vSAN drive is on spin media, 4TB SSD cache drives are accessible, it also could be possible to install another 4TB on either the ESXi host or HV host

When I kick off a conversion it looks to sit around 98Mbps transfer speed on the Starwind conversion machine, with 2% vCPU and 2.1 GB of memory being used.

What would best practice and the most efficient way to allocate resources to convert 2-12TB of data as quickly as possible.

Thank you,
Posts: 33
Joined: Fri Nov 09, 2018 5:02 pm

Re: Conversion best practice to obtain the quickest restore time

Postby Oleg(staff) » Thu May 02, 2019 3:52 pm

Hi Steve,
It is better to start StarWind V2V Converter on the host were you converting to.
Posts: 567
Joined: Fri Nov 24, 2017 7:52 am

Return to StarWind V2V Converter, StarWind P2V Migrator

Who is online

Users browsing this forum: No registered users and 2 guests