Shulou(Shulou.com)06/02 Report--

On the left is my personal WeChat. If you need further communication, please add WeChat. On the right is my public account "Openstack Private Cloud." If you are interested, please pay attention.

The virtual machine used at ordinary times is win10, which runs on the virtual machine of vmware5.1. Sometimes, when using it, there will be a stuck situation. I want to migrate to the PVE environment for use. To prepare for migration using clonezilla, document the migration process.

First download the ISO image of clonezilla live CD. The file I downloaded is clonezilla-live-2.5.6-22-amd64.iso, then upload it to ESI storage and mount the ISO image in the cdrom of the vmware virtual machine.

Modify the virtual machine startup order, cdrom first startup:

Restart starts to enter clonezilla:

It is very important to select the mode below. Here, you need to select "remote-source" to indicate that this machine is the remote source, that is, here is the source end!

Here's how to start configuring the target virtual machine:

Create a virtual machine in a PVE virtualization environment, note that the disk uses IDE, write through, and the disk size is consistent with the original virtual machine:

Input: sudo ocs-live-netcfg

The same is true for the second disk.

How long it takes depends on the disk size. After waiting for a few hours, the C and D disks are migrated successfully. Start the target virtual machine of the PVE environment:

After entering the system, I found that the original D drive was occupied by the CD-ROM drive. I can adjust it again in the system.

Start successfully! Migration successful!

Summary:

Clonezilla is to realize data migration from the bottom disk data copy and boot through the boot system (debian system). After both the source system and the target system enter the boot system, it can be directly understood as two hosts installed with debian linux. IP addresses can be directly set on them to realize data transmission and migration within the same local area network.

The actual menu navigation of the original version of clonezilla may have some differences. The key point to pay special attention to is to select "remote-source" when selecting the source system mode. Here, I fumbled for a little time. At the beginning, I selected "remote-dest", which happened to be reversed. In the final confirmation, I carefully looked at how to prompt the source system disk to be erased and stored in time.

Earlier, I migrated through nfs network disk, that is, first put the backup data of the source system on the nfs server, and then import the backup data from the nfs server on the target system. Later, I found on the Internet that two hosts can be copied directly on the same local area network, which is more convenient.

Clonezilla's migration method is not only valid for PVE v2v, but also for p2v.

A prerequisite for clonezilla data migration is that the target system disk cannot be smaller than the source system disk. This problem, because I use lvm-thin as the storage pool of the virtual machine in the PVE environment, the disk space allocated in the target system PVE will not really occupy the allocated space. The space used in the lvm-thin mode is the real data space. For example, the space allocated to the virtual machine D disk is 300G, but the data in the D disk is only 10G. Then, in the lvm-thin resource pool, It takes up only 10G of space. When doing this, you need to monitor the space usage of lvm-thin, otherwise it will overflow space, you can directly view it through the lvs command:

For example, pve2-lvm-sdb above is the storage pool where VM drive C is located, which is 33.40% used, and pve2-lvm-sdc is the storage pool where VM drive D is located, which is 14.07% used.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.