In general I prefer built-in solutions. Years ago I successfully used Disk Utility for cloning.
Maybe things have changed and maybe it was just happening to me, but when Tiger was released I had serious trouble to restore with that method. That time I switched to CCC, never had any trouble anymore and I was able to clone without rebooting, too. Getting back files from a Time Machine Backup was also a big trouble for me the time a friend switched from Leopard to Snow Leopard.
CCC makes intense use of rsync. AFAIK it's a custom compiled version different to the Mac OS X built-in rsync, because that version has (had) some bugs, too. For backup tasks I have a better feeling to use a solution that never disappointed me.
Me too. Time machine has been nothing but grief and frustration for me, while CCC has performed flawlessly for over ten, maybe fifteen years. I've never used Super Duper but several podcasters I listen to seem to. The Loop or SixColors are running 15% promos on CCC currently.
[doublepost=1507037723][/doublepost]
If you're making a clone, why not make it a bootable one? You then have your "computer" available anywhere if your drives die or are failing or it's stolen. BackBlaze, etc backup your data, but as Siracusa has pointed out, they're not clones.If the purpose of a clone is disaster recovery, then there isn't any reason for the clone to be bootable. All modern Macs can boot from the recovery partition, if it exists, or over the Internet if there isn't a recovery partition. Once booted, you just clone back to the new device.