whichever suits your purpose (live for single machine cloning, server for multicasting), and do your thing. I think for 800 GB it took about 20-30 mins.Now Clonezilla will recognize it. It has a nice handy X-Windows setup automatically for you. So as you said, you add the other drive to your VM in VMWare. It also includes GParted, which if you didn't know, is a handy linux partitioning application. If you download that ISO file, it is actually a live, pre-configured version of DRBL, that has both Clonezilla Live and Clonezilla Server on it. Ok, so what I did over the weekend in a test to clone 1 PC to many was to run Clonezilla Server in a VM. I found this and it looks like a decent writeup at a glance: (VLAN and subnets and things prevent easy access and bandwidth was important)īasically if you want to keep a small size and save the files off the virtual environment that could be your best option, especially if you need to do it routinely. There is also a way to get CloneZilla to boot to and save to a SAMBA share but I never really worked with that as my network wasn't really set to allow access that way. can restore these 'static' images at will) (took 1 copy of 5 special VMs saved it and backed up the save. Granted this was for a one time purpose, but it works. Then deleted the floater to restore space. I attached that floater to another VM - copied the files across the network to a 'back up NAS' and wiped the floater. Disconnect the B drive and power up vm normally. Created a lets say 20GB vxd called B, and attached it to machine A - booted to Clonezilla and saved the clone From C to the 'new hard drive' (N) then shutdown VM. How often do you need to use Clonezilla?īasically what I did (storage space was limited) was I had a 'floating' hard drive in vmWare.

Clonezilla iso image.