Carbon Copy Cloner 7.1.6 — Mac version

It's the go-to for Mac folk who want a bootable clone they can trust, not just another backup they hope will work. When a drive's on its last legs, CCC’s what you reach for.

Clone a dying disk

Legacy block-copy clones a whole volume sector by sector. It’s slow, but when a disk is throwing I/O errors, this can grab what’s still readable before it goes completely dark.

Schedule smart snapshots

Use APFS snapshots on a timed schedule to keep hourly states of your work drive. Roll back a duff edit without digging through a pile of dated folders.

Run a post-clone script

Set CCC to fire off a shell script after a task completes. Handy for ejecting a backup disk, pinging a health check, or booting a test virtual machine from your fresh clone.

Speed and day-to-day feel

CCC 7 runs light. On an M1 Mac mini with 8 GB of memory I watch it chug through a 250 GB clone while I carry on editing in Lightroom and a dozen Safari tabs. The menu bar icon sits quiet, the fans stay at idle, and memory pressure barely twitches. It's not a CPU hog — Bombich built the engine to yield to foreground apps by default, so you won't find your machine grinding to a halt mid-task.

That said, first-run copies and legacy block-copy jobs still take time. Expect a terabyte spinner to need a couple of hours over USB‑3. APFS snapshots, though, finish in seconds once the seed copy exists. Incremental backups are quick enough that you stop noticing them — a minute or two while you make tea, then the destination unmounts itself.

Stability is the quiet headline. CCC hasn't kernel-panicked a Mac in our workshop for years. It hooks into Apple's own replication APIs where it can, and falls back to its own file copier only when it has to. That matters when you're cloning a system volume you need to boot from tomorrow morning.

Pointing Time Machine and CCC at the same disk without conflict

CCC plays nicely with the tools you already use. Time Machine can run alongside it on the same destination disk — just point CCC at a separate APFS volume and both will coexist without tripping over each other. That gives you a bootable clone and a rolling hourly history on a single external drive.

If you use SuperDuper! for quick clones, CCC picks up where it leaves off — SuperDuper! for a fast one-off, CCC when you need scheduling, snapshot retention and post-flight scripting. The two don't fight for the same backup locks.

Snapshot integration reaches into Finder too. Right-click a cloned APFS volume, pick Revert to Snapshot, and you're browsing yesterday's desktop without launching CCC at all. That's all macOS plumbing, but CCC set it up. In a repair-café context, we'll often clone a customer's failing drive, then mount snapshots inside a virtual machine (UTM or VMware Fusion) to pull out individual files without touching the original disk again.

On the scripting side, CCC's ability to trigger a .sh or .py script after a task links it to Hazel, Keyboard Maestro, and simple curl health pings to a home server. One volunteer here has it fire off a Pushover notification when the weekly off-site clone completes — no cloud subscription, just a shell script and a free API key.

Booting a dead MacBook Pro from a clone when Disk Utility gave up

Last Tuesday a chap brought in a 2015 MacBook Pro that wouldn't boot beyond the Apple logo. The internal SSD was reporting SMART errors and Disk Utility had given up. We slotted it into a SATA dock on a bench Mac, launched CCC 7, and set a legacy block copy to a bare SATA SSD in a caddy. The disk threw seventeen I/O errors over the next two hours, but CCC logged each one and kept pulling what it could. By lunchtime we had a bootable clone on the bench SSD with everything intact except three corrupted photos in the Downloads folder.

We swapped the clone into the MacBook, booted it, and ran First Aid on the new volume. The customer walked out with a working machine and a fresh Time Machine schedule pointed at a portable drive. CCC didn't save a dying disk — it just grabbed the lot before the disk gave up entirely. That's what it's for.

Plug in a disk and create one simple task before building schedules

Don't try to build a masterpiece schedule on day one. Start simple:

1. Plug in an external disk with at least as much free space as your internal drive.
2. Create a single task: source is your internal SSD, destination is the external. Check Enable snapshots and set it to retain the last three.
3. Let it run once, manually. This gives you a full seed copy and a snapshot.
4. Now add a schedule — daily at 1 pm if you work from a desk, or attach a trigger so it runs when you plug the disk in.
5. Boot from the clone once, just to prove it works. Hold Option at startup, select the external, and breathe out when you see your desktop.

After that, tweak. Maybe you want hourly snapshots on your work drive alone, with a weekly clone to a rotating pair of disks kept in different buildings. CCC's task groups let you bundle these so one click (or one schedule) runs the lot.

One tip from the workshop: label your backup disks clearly. CCC shows the volume name in its task list, but when you're squinting at two identical USB‑C enclosures under a desk, a Dymo label that reads "CCC CLONE A" stops you wiping the wrong drive.

What changed in CCC 7

Version 7 dropped support for macOS Catalina, Big Sur and Monterey — it needs macOS 15 Sequoia or later. That was a deliberate cut. Bombich leaned into Apple's newer APFS replication APIs and stopped maintaining the compatibility shims for pre-Sonoma systems. For everyday use, that's a mixed bag: if you're running an older Mac that can't go past Monterey, you'll stick with CCC 6. If you've moved to Apple Silicon and keep macOS current, CCC 7 feels snappier and makes fewer trips through Rosetta-era fallback code.

The biggest day-to-day shift is the Quick Update feature. Instead of a full scan, CCC 7 compares FSEvents logs with the destination's snapshot index, so an incremental on a drive that hasn't changed much finishes in under a minute. In practice, that means you can run a backup while you're packing up to leave and it'll be done before you've found your keys.

Snapshots got smarter too. CCC 7 lets you thin them with retention policies per task — keep 24 hourly, 7 daily, 4 weekly — and it prunes them on the destination automatically. Earlier versions needed manual thinning or separate scripts. Now it's a dropdown you set once and forget. That alone saves a dozen gigabytes a month on a busy work drive.

Legacy block copy is still present for dying disks, but it's been reworked to skip unreadable sectors faster. You lose that data either way, but CCC 7 gets through a failing 500 GB disk about 30 minutes quicker than CCC 6 did on the same hardware. In a repair setting, that's the difference between a customer waiting and a customer coming back tomorrow.

• macOS 10.15 Catalina or later
• Intel or Apple Silicon Mac