Clonezilla: Disk Imaging and Cloning
clonezilla.org
clonezilla.org
I don't want to besmirch the name of someone's good work of course. But I used Clonezilla a couple years ago and it was antiquated in both interface and features compared to Reflect. A live image and a resize while doing an intelligent copy of the actual in-use data (vs a whole-disk forensic image) is absolutely no problem. It's by far the easiest thing I've ever used for disk-to-disk clones and imaging.
Clonezilla takes a solid knowledge of Linux even to get the job done in many cases, it's not full featured, and I found it was not particularly solid on my hardware. I preferred the plain Ubuntu LiveCD versus it, or at a minimum SystemRescueCD if you insisted on a rescue-oriented livesystem.
Neither tool used 7zip/p7zip to hit maximum compression, but it's easy either way. You do that later on your fileserver.
I'd argue that the interface for setting up incremental backups could be better, and scheduled tasks can result in an unkillable prompt - when my laptop isn't on my LAN, I don't want the backups to run at all.
(I used it about a month ago to attempt to clone a failing drive after Clonezilla choked and died horribly. It got significantly further, not sure if going to it first would've helped more.)
Last year when migrating to a new HDD I cloned the Windows partition using Clonezilla, just to be met with BSOD immediately. I wasted 2 days trying to figure out what's the problem, Windows boot recovery, driver injection etc. After 2 days I created a Macrium Reflect live media, cloned the original partition again with it and voila! Windows booted successfully in the first try.
I'll never use Clonezilla again because I value my time.
We're a linux-mostly environment and CZ has been absolutely great for our IT staff in standardizing our desktop images. We use USB images that starts the cloning process automagically on boot.
We've had mixed results using CZ over the network for cloning (PXE boot).
All in all though, it's been a great tool to have and we're very grateful for it.
Over ten years old (like Clonezilla) SystemImager does it better with rsync and file-based imaging. No support for Windows, so maybe that's the 'killer feature' of CZ.
I've tried to find it again several times to no avail. I have a bunch of backups that I would be interested in accessing without having to restore to disk in their entirety (as explained below):
http://unix.stackexchange.com/a/52684
Edit: Apparently a sparse VM disk works:
karma. people assign a lot of value to their fake internet points and posting\reposting popular things is great way to get them
I have never used Clonezilla.
I haven't used SuperDuper in a few years, but when I did use it I had no problems. I switched to Carbon Copy Cloner because it had a few more features. However, you need to pay for CCC (there is a free trial). SD is completely free if you just want to clone entire disks, and you only need to pay if you want extra features.
When I say that CCC and SD copy "most" of the files, what I mean is they attempt to be smart. E.g. they omit files in a .Trash directory, and they omit various cache and temporary files.
IMO if your data is important to you, then you should clone it to two separate drives from your Mac's HDD. Which means you can use the free SD and the trial CCC and make one clone with each. Better safe than sorry.
Even at that, whenever I make full backups I like to use an independent method to check that the data is correct. Previously I used to do something like this at the root of both the source and the destination:
find -x \
. \
-type f -print0 \
| xargs -0 -n 100 -x md5 \
| sort > /tmp/manifest.source
I would then compare the two result files and see what was copied. Unfortunately that tends to be noisy because as I mentioned not all files are copied. I eventually wound up writing a Python script instead of that shell script. My Python script helps cut down on the noise by e.g. not checksumming files in .Trash directories.I would much rather trust a program like CCC than Clonezilla. The CCC developer is very responsive to email and to bug reports. His program exists to make backups of Mac partitions. He doesn't need to worry about reiserfs, btrfs, ntfs, etc. Instead he spends his time worrying about quirks in OS X, nee macOS. And that's all. I trust him to get it right because that's his livelihood.
I tried Clonezilla out back in September on my Windows machine, which was running fine at the time.
I never asked or specified that Clonezilla change a single byte on the drive.
After a failed attempt to backup to a network volume, I found that Windows booted into a black screen with a mouse cursor, and nothing else.
Windows repair didn't fix it. I ended up just buying a whole new SSD and moving on, but wow.
Also, you needed to buy a whole new SSD? You are aware that an SSD is rewritable, right?