Free Webinar
September 5 | 11am PT / 2pm ET
Automate your daily and time-taking
Hyper-V administration with PowerShell!
Speaker: Ivan Ischenko, Solutions Engineer, StarWind
Posted by Alex Bykovskyi on November 13, 2018
StarWind V2V Converter: Now with Physical to Virtual (P2V) conversion option!

One, two, three … Let’s roll! StarWind presents an updated functionality of V2V Converter. The utility enables conversion of a physical machine into a virtual one (P2V) and other way around. For example, you have a server with Windows Server 2012R2 installed running some critical application. With physical-to-virtual (P2V) entire host or specific physical drive (or volume) can be migrated. What else? The pressure is on! Now your VMs can be migrated directly between Hyper-V and ESXi (and backwards). Moreover, StarWind V2V Converter offers bi-directional conversion between all the major VM formats: VMDK, VHD/VHDX (Windows Repair Mode aware), QCOW2, and StarWind native IMG.

Learn More

Posted by Oksana Zybinskaya on January 16, 2018
Choosing proper V2V converter for smooth VM migration

Migrating your VMs from one hypervisor to another may be a bit of a challenge if you don’t have some decent virtual machine converter at hand. Different hypervisors have their own proprietary VM formats: VMDK, VHD and VHDX, QCOW, you name it. The problem is that one VM format can be not supported on other platforms. In this case, a V2V converter is a must-have. Now, the question arises: which converter should I choose?

Learn More

Posted by Askar Kopbayev on March 27, 2017
Virtual workload migration with VMware

It is quite surprising how many companies migrate virtual workload nowadays. There could be different reasons – expiring contract with the service provider, move to the new office, consolidation of resources to minimize Capex and Opex, but in every case, companies need efficient and flexible V2V migration solution. Very often people think of migration in terms of moving data from one place to another. However, migration is much more than that. For instance, you would probably want VMs to keep the same IP addresses after the migration. Which means you need to consider stretching VLANs between the source and target locations in case you cannot migrate all VMs in particular subnet in one go. You must plan a network cutover too.

Learn More