There’s a particular sinking feeling that comes with a failed Time Machine drive. It was supposed to be the insurance. Now the Mac is gone, or the files are gone, and the backup won’t mount either.
Time Machine backups are recoverable more often than people assume — but how the recovery goes depends heavily on how the backup was stored, and that’s worth understanding before you let any tool touch it.
Three formats, three situations
Directly attached drive, HFS+ (older macOS). Time Machine wrote your files as a normal folder tree with hard links standing in for unchanged files. This is the friendliest case: even a badly damaged backup usually yields recognizable folders full of real files. You don’t need Time Machine or even a Mac to read the results.
Directly attached drive, APFS (Big Sur and later). Backups are stored as APFS snapshots. More efficient and more robust in normal use, but harder to pull apart when the container is damaged, since the snapshot metadata is what ties everything together.
Network backup — Time Capsule, NAS, or shared Mac. The whole backup lives inside a single .sparsebundle file, which is a disk image split into thousands of small band files. This is the most fragile arrangement. A handful of corrupt bands can make the entire bundle refuse to mount, even though the vast majority of your data is sitting right there.
The good news on sparsebundles is that they’re a known format. A bundle that macOS won’t mount can usually be assembled and read anyway, and the loss is limited to whatever lived in the damaged bands rather than the whole thing.
Common failures and what they mean
“Time Machine must create a new backup for you.” macOS decided the existing backup’s identity or structure is invalid. It’s about to start fresh. Say no, and disconnect the drive — if you let it proceed, it starts writing over the backup you still need.
“The backup disk image could not be accessed” / error -1. Sparsebundle mount failure. Usually structural damage, sometimes a network hiccup during a write.
Verification failure. Time Machine periodically verifies backups and will announce that yours is unreliable. Treat it as an early warning: copy what you can off immediately rather than waiting for the next failure.
The drive is slow, clicking, or unmounting. That’s the hardware, not Time Machine. Backup drives are frequently the cheapest disk in the house, running in a warm enclosure, spinning up and down all day for years. They fail like any other drive — see clicking or freezing.
Free evaluation. Firm quote before any work begins.
What not to do
Don’t let Disk Utility “repair” it as your first move. First Aid on a damaged Time Machine volume can discard the very structures a recovery would use, and on a physically failing drive it adds hours of stress. Image first.
Don’t reformat and start a new backup. This is what macOS will nudge you toward, and it destroys the old backup completely.
Don’t run repeated mount attempts. Each one is more reads on a drive that’s already struggling.
Don’t delete “old backups” to free space while troubleshooting. That operation rewrites structural metadata.
What recovery looks like
Image the drive first, then work from the copy — same as any other case. From there:
On HFS+ backups, the folder tree comes out directly. Hard links make the on-disk structure unusual, but files are files and they extract with names and dates attached.
On APFS backups, snapshots get parsed from the image and individual point-in-time versions pulled out. Often you don’t need every snapshot — the most recent complete one is usually all anybody wants.
On sparsebundles, the bands get reassembled into a mountable image and the file system read from that. Missing or damaged bands mean losing whatever they held, not the entire backup.
One thing that helps a lot: tell me which files actually matter. Time Machine backups are enormous and full of system files, caches, and dozens of versions of the same document. A recovery targeting your Photos library and Documents folder is faster and cheaper than a bit-perfect reconstruction of a 4 TB backup nobody needs in full.
And the uncomfortable question
If the Time Machine drive failed, where else does this data exist?
A single backup drive isn’t a backup strategy — it’s one additional copy, and it’s the copy running the hardest. If both your Mac and your backup drive have now failed, that’s not bad luck so much as a system with no redundancy in it. Worth fixing once this is sorted.
The bottom line
Time Machine backups usually survive worse damage than people expect, especially the older folder-based ones. The two moves that turn a recoverable backup into a lost one are letting macOS start a fresh backup and letting Disk Utility repair it in place. Decline both, then image the drive.
Time Machine drive not mounting? Start a case — tell me whether it was plugged directly into the Mac or backing up over the network, and roughly what macOS version. That determines which of the three formats we’re dealing with.