I have been in IT for 20 years and worked both in house for small company and large corporations. I have worked for several MSP's in the past also and even I find this content helpful. I have worked with clonezilla in the past but never used this feature. I had a VM in proxmox that I needed to move it to virtualbox. This process worked almost perfectly. I just needed to tweak a couple of things in the new VM to make it work on the new host. Would of had to do that no matter what method i used anyway. Thanks for sharing this! you bring great value to the community.
I've been a user and fan of Clonezilla for many years now, so much so that I enjoy watching videos of people doing the things I do lol. I must say, this video was nicely put together and knowledgeable.
I was playing in my lab with FOG project software for ipxe cloning/imaging/deployment. I believe it also uses partclone same tool as clonezilla. nice tool.
Thanks a lot Tom, this looks good; I have most of my installs already doing nightly and frequents with Acronis Server for their virtualized Windows; primarily for automation and routine. I've been aware of Clonezilla but haven't dipped into it, and looks great in many conditions (you don't need restore dates on migration or full current operational)
I just migrated a test Windows 10 VM from ESXi 6.7 to XCP-NG 8.2 in my homelab. Working great so far, just had some trouble getting the NIC to detect on XCP-NG but that was fixed by changing the template from W10 to Debian in XCP-NG. I use Citrix Hypervisor + XenCenter at work and decided I wanted to get familiar with Clonezilla and XOA before I pitch it to the team if we use it in production. Most of our V-V are using vCenter converter (yeah I know its EOL and I wish we'd find another solution). As always thanks for the tutorial Tom.
While this is useful as an agnostic solution, which is absolute praise for clonezilla, specifically with VMware and Windows (and some of the big linux distros) there is an incredible tool that can do a clone like this live and even preform incremental syncs before cutting over. That's not useful when using a hypervisor that isn't VMware related or a linux distro that isn't supported, but it's a far better experience than clonezilla in a situation where it can be used.
This is pretty neat, I like that it just does it over the network. No extra drives! Regarding the hypervisor you used, I'm debating on trying out XCP-NG. I've been using proxmox but XCP looks interesting. Have you tried Proxmox before and if so do you prefer XCP to it? Thanks for the videos :)
Great video. Used it to move ESXI 7.0 host off VMware work station to my Dell R620 Server. The server would not recognize the drives for installation. It was driver issues from the installation disk (I think). Any how it worked
excellent walk through thank you for creating, a few questions . . . q1. any issues you foresee using this to move a vmware player [ or hyper-v ] windows 11/10 install to a physical machine install where the latter boots into clonezilla iso using usb boot stick? q2. does clonezilla iso support detection and enabling of intel SoC wifi adapters and/or realtek usb nano dongle adapters so that you can boot physical machine and receive clone over a wifi network? q3. any issues you foresee with the cloning of windows 11/10 from vmware player [ or hyper-v ] or different intel x86 isa 64-bit system setup to a new more current hardware setup?
Hi, I tried to do it exactly that way but no luck. On my Proxmox I had it all set up as you, but it showed me this: ''Error! No existing partitions or no unmouted partitions are found! To use Clonezilla to save or clone a partition, the source partition must exist or be unmouted! If you are sure the partition exists in this machine, mabe the kernel is too old? Press Enter to exit...'' How can I over come this? Thank you.
@@LAWRENCESYSTEMS Rescuezilla is a new project that started in 2019 that extended the (at the time) abandoned Redo Backup & Restore. The project was dead and resurrected was "Redo Backup and Restore" which was renamed to "Redo Rescue."
You cloned a debian VM, so clonezilla boots ok in that VM, but if you create a Window 10 VM and try to boot clonezilla it gives an error with the NIC and won´t allow the VM to connect with the physical machine which is ready. Does this method works only with Linux OS or is it supposed to work with windows as well? To be able to use the network feature of clonezilla make the job a lot easier and the disk2vhd method IMO.
I found a way to solve the problem described above. It´s a bypass but works great and you can clone any windows disk from a source computer to the XCP-NG VM disk using clonezilla.
@@tepitokura I do it this way: Create a new VM with a linux system, let´s say CentOS 7. Add a disk with the same size or bigger than the on you are cloning from the windows machine. Boot the VM CentOS 7 with clonezilla and do the same with the windows computer using a pen drive with clonezilla. Setup the clone to work on the network. After the cloning finishes stop the VM CentOS machine and detach the disk from the VM CentOS. Create a new VM with the same windows (delete or detach the disk created with the new VM) and attach the disk that came from the VM CentOS to the new VM Windows. Start the new VM Windows and it should work ok. I´ve cloned more than 10 Windows computers doing this way and it has worked pretty well so far. Hope it helps.
Clonezilla is a very simple tool, if you want a more complete and permanent solution (also open source), the Fog Project does the job perfectly! fogproject.org