StarWind Software

Hi all

As a first-time user of the Starwind V2V converter, I am attempting to migrate virtual machines on Proxmox 9 to two hyper-V Windows 2022 servers. Neither server is currently in a production environment.

The first virtual machine, a Linux-based OS with a 32 GB hard drive, was successfully migrated in six hours.

The second virtual machine, a server 2022 with a 320 GB hard drive, has been stuck at 96% progress for over seven hours. Initially it only took a few minutes to reach 96%.

The servers are 15th and 15th generation Dell with NVMe storage and 40 gigabit NICs.

Monitoring the NICs in Windows, data transfer fluctuates between 5 and 7 Mbps and CPU usage fluctuates between 1 and 2% on the Starwind application.

From reading other posts about slow transfer, it appears my system is running excessively slow.

Any assistance would be greatly appreciated.

Try converting them to local files and copying them to the destination afterward.

unfortunately the local file is greyed out and will not allow me to select it, is there a way of activating it?

You can copy it to Hyper-V and convert it locally.
As a workaround, you can use something like instant recovery (e.g., Veeam or Altaro).

Why is "Local Files" not available as a destination?

The first time I went to try it it was available but then it greyed out on the second attempt....

Please let me know where you run the software.

The Software is run on the target server Windows Server 2022 Hyper-V, the source machine is Proxmox v9.

Could you please make sure you are running the software as an administrator? Thanks!

Yes I am logged in as administrator.

I have transferred the Proxmox files to the Hyper-v server and started the convert from "Local File" to "Hyper-v".

So far at 41% after 5 minutes...... I think this is the route going forward. I will let you if this works.

Thanks for your update. Glad to read that it works!

Thanks

This method has worked perfectly

You are always welcome.