The first part: P2V migration
P2V migration requires the use of VMware vCenter Converter Standalone 5.0, the software provides an easy to use solution that can be, other virtual machine formats and third-party image formats to automatically create VMware virtual machines from physical machines (running Windows and Linux). Through an intuitive wizard-driven interface and a centralized management console, Converter Standalone without any disruption or downtime can quickly and reliably convert multiple local and remote physical machine physical machine. Through the operating system to perform static snapshots of clients on the source machine before data migration, to ensure the reliability of conversion. Cloning achieve non-destructive thermal conversion by the source server downtime or reboot. VMware vCenter Converter to become the industry's widespread use P2V migration tool.
This example uses the physical machine running Windows remote source heat clone (P2V).
Schematic analysis:
The following step 4 described cloning thermal migration process. You can use the conversion wizard to set up conversion tasks, perform all of the cloning tasks Converter Standalone components. The following workflow is an example of remote hot cloning, clones in this process is not physical machine downtime.
1 Converter Standalone prepares the source machine for the conversion. Converter Standalone installs the agent on the source computer, the agent creates a snapshot of the source volume.
2 Converter Standalone prepares the virtual machine on the target computer. Converter Standalone creates a virtual machine on the destination machine and the agent copies the source volume to a target computer in the computer.
3 Converter Standalone completes the conversion process. Agent required to install the driver allows the operating system to boot the virtual machine and the virtual machine will be customized (e.g., changing the IP information).
4 Converter Standalone uninstalls the agent from the source computer (optional).
Virtual machine ready to run on the target server.
The formal implementation P2V migration:
First, log in to the control interface, select "Convert your computer."
Second, select "Turn on the computer's." And enter the remote machine you want to connect to migrate physical IP address, login, password and operating system family information. Then "Next." (Note: the source physical machine is a windows server 2003 server)
Third, select "Automatically uninstall these files after successful import", then press "Yes." To migrate physical machines to install agents.
Four, IP address, login and password input target ESXi 5 host. Then "Next."
Fifth, the system automatically recognizes the physical machine to migrate the computer name (for example named "the PC"), to select "next."
Sixth, select ESXi 5 "data storage" and "Virtual Machine Version" (Note: Select version: Version 8). After confirming "Next."
Seven parameters choose to migrate. (For example: Select the data you want to copy, select the partition you want to migrate the information, services and network cards, etc.) confirmation, select "Next."
Eight, review the information to confirm, select "Finish."
Nine, when VMware vCenter Converter Standalone 5.0 Migration Wizard, click "Finish", officially began migration.
Ten, after the successful migration of virtual machines can run properly on ESXi 5.
After the first migration into the system manually delete the old NIC driver, and then install vmware tools
| Open a command line window (run cmd), type:
|
|||||||||||||||
| 1)set DEVMGR_SHOW_NONPRESENT_DEVICES=1 |
|||||||||||||||
| 2)devmgmt.msc |
|||||||||||||||
| In the pop-up "Device Manager" window. Select "View" --- "Show hidden devices" |
|||||||||||||||
| Then expand "Network adapters" children, you can see some of the card information display transparent icons, |
|||||||||||||||
| This information is a physical card information source server. Then choose transparent unloading equipment, |
|||||||||||||||
| RAS sync adapters for proper system device does not need to be uninstalled. |
|||||||||||||||
After completion of the above, P2V migration basically completed, the system migrated operating results and the physical machine running on a virtualization platform, but do not forget to install vmware tools. Whether the agent has been installed on the automatic unloading system work is migrated 5.0 post-migration migration checks VMware vCenter Converter Standalone.
The second part: P2V Migration simultaneous analysis
一、，官方文档中描述“调整 FAT 卷大小或压缩 NTFS 卷大小，或更改目标卷上的群集大小，则不能使用同步选项。”
针对官方该描述进行以下实验验证：
被迁移是一台物理服务器，迁移向导在迁移要复制的数据时，可以通过手工调整迁移目标磁盘分区大小。在“目标大小”中选择“键入大小（以 GB 为单位）”然后通过手工，输入目标分区容量。经测试核实如果把目标分区容量设置小于源分区，就不能选P2V同步选项，如果把目标分区容量调整大于或等于源分区，P2V同步不受影响。
实验例子：源服务器C盘 25.34 GB， D盘 14 GB
1、在“目标大小”中选择“键入大小（以 GB 为单位）”。划分目标服务器分区的容量小于源服务器对应分区容量。
2、同步选择：同步更改--克隆后立即运行。
3、P2V向导在最后步骤提示，因为P2V迁移的目标卷容量调整了，并且目标卷容量是压缩了（即小于源卷容量），无法启用同步。
4、重新在向导中把P2V迁移目标分区大小调整为保持大小（即：保持原始源卷大小）或者调整容量大于等于源分区容量时，同步可以正常执行，P2V迁移向导可以顺利完成。
二、P2V迁移完成后，可以手工执行多次同步。
P2V迁移过程中，通过实验核实迁移同步，可以手工多次执行（备注：在目标虚拟机迁移完成后，进行过启动运行，关闭目标虚拟机再手工执行同步，测试P2V同步继续生效）：
1、同步选项设置：选择“同步更改”--“克隆后立即运行”，不选择“执行最终同步”（避免P2V迁移任务完成后，任务自动结束，不能再手工执行多次同步），“转换后”要手工勾选“在目标虚拟机上安装Vmware Tools”，其他选项默认。
2、P2V首次迁移完成后，向导会自动做一次自动同步，由于向导没有把迁移作业自动结束，在首次同步后还可以进行多次手工同步。
小结：
When synchronization test, verified the target virtual machine after the P2V migration, you can start running, not before the end of the manual, you can synchronize multiple times in the P2V migration. If you choose to perform the job in the P2V wizard synchronization, met the target virtual machine is running, the target virtual machine automatically turns off synchronization wizard with the execution, synchronization is complete and then manually start the target virtual machine