Lists the main processes of migrating A vmwarevm to the hyper-V platform.
We can see that there is a downtime for migrating virtual machines from the VMware platform to the hyper-V platform. Note the following when converting virtual machines in our actual production environment:
650) This. width = 650; "Title =" 1 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" 1 "src =" http://img1.51cto.com/attachment/201410/9/1559738_1412841233VHP2.jpg "" 461 "Height =" 484 "/>
L impact of virtual machine service interruption time on the production environment.
L virtual machines with large data volumes (such as SQL Server) should be switched off and services or business systems dependent on them should be stopped.
L fully consider the mutual dependency between virtual machines, and then determine the conversion priority of the virtual machine.
L we strongly recommend that you back up the VM before conversion.
L for virtual machines with high service downtime requirements, appropriate time conversion should be selected.
L after the conversion of the virtual machine fails, you can start the VMware source Virtual Machine to maintain business operation.
Backup: Although the source virtual machine will not be deleted or changed during the conversion process, as a best practice, we strongly recommend that you back up the virtual machine data in advance (for example, copying the entire virtual machine file to the storage server ), to prevent accidental deletion or modification of the source virtual machine during the conversion process.
Disaster recovery: The conversion may fail during the conversion process. In this case, the task of restoring the virtual machine is very simple during migration from VMware to hyper-v, because the conversion process does not delete the VMware source virtual machine, you only need to start the source virtual machine.
Migration from VMware to hyper-V platform solution (1)