Time Machine Backup Failed: 3 Real Fixes That Work

Cause #1: Corrupt Local Snapshots Are Blocking the Backup

This is the one that catches most people off guard. Time Machine doesn't just back up to your external drive — it also creates local snapshots on your startup disk. If one of those snapshots gets corrupted (say from a sudden power loss or a crash mid-backup), it'll block the whole process. You'll see "Time Machine Backup Failed" or the backup just hangs at "Preparing backup" forever.

Had a client last month whose iMac showed "Backup Failed" every night for a week. They tried everything — reformatting the drive, buying a new one — but the real fix was nuking those local snapshots.

Here's how to check and clear them

1. Open Terminal (Applications > Utilities > Terminal).
2. Run tmutil listlocalsnapshots / — this shows all local snapshots on your startup disk.
3. If you see anything, delete them all with sudo tmutil deletelocalsnapshots /. You'll need your admin password.
4. Then run sudo tmutil thinlocalsnapshots / 10000000000 0 to thin them down aggressively.

This clears the logjam. After that, eject the Time Machine drive, wait 10 seconds, plug it back in, and start a fresh backup. Works 90% of the time.

Cause #2: The Backup Drive Is Full (But macOS Lies About It)

macOS has a nasty habit of not telling you the backup drive is full until it's too late. You'll see "Backup Failed" with no clear reason. Open Disk Utility, select your Time Machine drive, and look at the capacity. If it's over 90% full, that's your problem. Time Machine needs some free space to create backup metadata and run integrity checks.

I've seen this on 1TB drives that people have been using for years without ever cleaning out old backups. Time Machine doesn't automatically delete the oldest backups when space runs low — it'll just fail.

The fix: trim old backups manually

1. Open Time Machine from the menu bar (the clock icon) and select "Enter Time Machine".
2. Browse back to the oldest backup you can find. Right-click it and choose "Delete Backup".
3. Repeat until you've freed up at least 20% of the drive's capacity.

If you don't want to manually browse, use Terminal: tmutil listbackups to see all backups, then sudo tmutil delete /Volumes/YourDrive/Backups.backupdb/YourMacName/2023-01-01-123456 (replace the date with one you want to remove).

Pro tip: Don't just delete the Backups.backupdb folder from Finder — that corrupts the whole backup system. Use Time Machine or tmutil commands only.

Cause #3: Permissions on the Backup Drive Are Busted

This one's subtle. The drive itself works fine for storage, but Time Machine can't write because the permissions got mangled. Common trigger: formatting the drive with a non-Mac file system (like exFAT) or using the same drive for multiple things without properly ejecting it. I had a client who used their Time Machine drive as a shared drive between a Mac and a Windows PC — it worked for a month, then started failing every time.

The fix: repair permissions and reset the backup

1. Open Disk Utility, select the Time Machine drive, and click "First Aid". Run it twice — once for the volume, once for the disk.
2. If that doesn't work, the nuclear option: reformat the drive as Mac OS Extended (Journaled) with GUID Partition Map. This erases all your existing backups, so only do this if you're okay starting fresh.
3. After reformatting, go to System Settings > General > Time Machine Backup and select the drive again. macOS will rebuild the backup structure from scratch.

Don't use APFS for Time Machine drives on older Macs — I've seen it cause constant "Backup Failed" errors on macOS Monterey and earlier. Stick with Mac OS Extended.

Quick-Reference Summary Table

Try these in order — most people don't get past cause #1. If you're still stuck after all three, it's time to check if the drive itself is dying. Run SMART status on the drive using a tool like DriveDx. A failing drive will keep failing backups no matter what you do.