Time Machine Backup Failed or Corrupted: How to Get Files Back
Our founder and lead technician, Joseph Montanti, handles cases personally.
A failed Time Machine backup means the latest backup did not finish; earlier backups may still be usable. Repeated failures can come from insufficient space, a lost connection, unavailable files or damage to the backup disk or its file system. First check whether the files you need are still on your Mac or exist only in the backup, because that determines which disk must be preserved.
On this page
What the Time Machine error is telling you
“Couldn't complete the backup” is a broad failure message. The detail underneath it matters: a full disk needs a different response from an unavailable network share or a file that macOS cannot read. Check the last completed backup date as well as the latest attempted backup.
| Message or symptom | What it means | First useful check |
|---|---|---|
| Time Machine couldn't complete the backup | The latest attempt failed. | Read the accompanying reason and check the last successful date. |
| The backup disk is not available | Time Machine cannot reach the destination. | Check its connection or network availability. |
| The backup disk image could not be accessed | The backup image could not be opened. | For a network backup, check the share and login before assuming image corruption. |
| The disk is read-only | Time Machine cannot write to it; the disk or file system may have a problem. | Preserve existing backups before repair. |
| Some files were unavailable | The files could not be accessed for this backup. | Keep the Mac unlocked and check whether cloud syncing is complete. |
| The backup disk is full | There is insufficient room for the new backup. | Check destination capacity and space on the Mac itself. |
| Backups cannot be reliably restored / a new backup is required | Time Machine cannot continue using the existing backup normally. | Retrieve needed history before accepting a new-backup operation. |
Apple's backup and restore troubleshooting covers connection, space and unavailable-file errors. Its failed-backup guidance specifically identifies read-only errors as a possible disk or file system problem.
File system information tells macOS where files and backup versions are stored. Damage there can make a backup difficult to browse even when some file contents remain readable. Physical read errors can damage access to that information too, so a corruption message needs to be considered alongside the drive's behavior.
A failing backup disk may hold your only copy. Leave a dropped or wet backup device off, as well as any backup HDD that grinds, beeps or clicks repeatedly; abandon the transfer if its files stop reading, read errors appear or the source disappears from Finder. Repairs, erasure, backup deletion and firmware changes come only after the needed files or a full image are preserved.
Retrieve files before choosing Start New Backup
When Finder opens the Mac's current documents and photos, save those folders on a separate disk before troubleshooting Time Machine. If the backup contains the only surviving version, retrieve that version or preserve the backup disk before trying to repair it.
If Time Machine says it detected that your backups cannot be reliably restored, starting over can remove history you still need. Apple explains that Start New Backup deletes the existing backup and protection is incomplete until the new one finishes. Its alternative is to choose Back Up Later and try retrieving data first.
- Choose Back Up Later when offered.
- Open the folder where the wanted file used to live, then choose Browse Time Machine backups from the Time Machine menu.
- Use the dates and arrows to find the required version.
- Restore the item and open it to check its contents. Copy the recovered file to a separate healthy device.
These steps follow Apple's new-backup guidance and file restoration instructions. Restoring through the normal interface returns an item to its original location, so pay attention if a newer file with the same name is already there.
If the original MacBook is unavailable and a restore source is not working on another Mac, check the backup password and macOS compatibility. Apple states that backups made with macOS Monterey 12 or later require macOS Big Sur 11 or later for restoration. A connection or compatibility issue should be resolved before treating the backup contents as lost.
Older Backups.backupdb folders
An HFS+ Time Machine disk has a Backups.backupdb directory containing a folder for the Mac and dated backups. On a stable, readable disk, Finder may let you open the appropriate dated folder and copy wanted files to another drive even when the usual restore interface has failed.
The path takes the form /Volumes/[Your Backup Drive]/Backups.backupdb/[Your Mac Name]/. Open a completed backup date and locate the original volume and user folder within it. Keep the backup's folders in place while copying files out; renaming or reorganizing them can disrupt the history Time Machine expects.
APFS backups and tmutil
APFS Time Machine disks use backup snapshots rather than a Backups.backupdb directory. A missing folder with that name is therefore normal on an APFS destination. Apple's built-in tmutil manual describes both structures and the commands for listing and restoring backups.
- Run
tmutil listbackupsto list completed backups associated with the Mac. - For a particular destination, use
sudo tmutil listbackups -d "/Volumes/Backup Disk" -m, replacing the volume name. The-moption attempts to mount the backups and show their paths. - Locate the wanted file in a listed backup path. Restore it to a separate healthy destination with
tmutil restore "/path/to/backup/file" "/Volumes/Healthy Drive/Recovered/", replacing both paths with real locations.
Some operations require administrator privileges and Full Disk Access for Terminal. Check man tmutil on your Mac for the installed version's requirements. Apple explains how to open these built-in command manuals. Listing backups provides paths and dates; it does not validate every file in them.
tmutil verifychecksums "/path/to/backup" compares file data with checksums recorded at backup time where those checksums exist. It reads the selected data, so reserve it for a stable, preserved backup. A mismatch is reported with !; an invalid recorded checksum uses ?. This is a verification command, not a way to repair unreadable sectors.
Why does my Time Machine backup keep failing?
A backup that repeatedly fails at the same point may be encountering a particular unavailable file. One that loses the whole destination may be dealing with its connection or storage. Start with the reported failure rather than applying every available disk repair.
For an undamaged, quiet external drive that reads steadily, check its cable and connect it directly to the Mac instead of through a hub. For a network destination, confirm that the Mac and backup device are on the same network and the share is available. Apple's connection guidance covers both arrangements.
Space is needed on both ends. Time Machine removes old backups as space is needed, but it retains the last remaining backup. A large new backup can still exceed the destination's capacity. The Mac also needs working space to create the snapshot and temporary information used for backup.
Using a larger new destination preserves the old disk's history. Excluding a large replaceable folder can reduce what a new backup needs to copy, but that folder then needs another protection method. Deleting old backup versions should be a deliberate decision after preserving anything that exists only in those versions.
If the error mentions unavailable files, keep the Mac unlocked during a manual attempt. Cloud-managed files may need to finish syncing or downloading before Time Machine can include them. A network security tool or VPN can also affect access to a network backup device.
Check failures that seem silent
Time Machine can be enabled while the last completed backup is old. Open System Settings, General, Time Machine and inspect the completion date and error details. An attempted backup or a running progress indicator is different from a completed copy.
For more detail, Terminal can display recent Time Machine log messages with log show --predicate 'subsystem == "com.apple.TimeMachine"' --last 2h. Apple's installed man log documents the subsystem filter and time window. Read messages near the failed attempt for a named file, destination or operation; some details may be omitted or redacted by the system.
The log is useful for separating repeated file-access failures from a disappearing destination. It avoids changing the backup just to learn what failed. A clean-looking log does not replace opening the files in a completed backup.
When a backup seems stuck in progress
The first backup copies much more than later incremental backups. A large file that changes frequently can also take substantial time to back up again, even when you made only a small edit within it. Virtual-machine images and other large application files can therefore make the progress look disproportionate to your recent work.
Apple also identifies applications that repeatedly access the backup disk as a source of delay. Antivirus scanning can compete for the same disk, and network performance limits a network backup. Check those conditions before deciding that elapsed time proves the drive is failing.
Apple's slow-backup guidance explains these causes. There is no single normal completion time for every Mac, disk and backup size. Continued progress on a responsive disk differs from a destination repeatedly dropping offline or a copy stuck on read errors.
After the data is preserved, current macOS and device firmware may resolve a confirmed software or compatibility issue. An upgrade coinciding with a failure is a reason to check the maker's support information, rather than evidence that a particular Sequoia or Sonoma bug caused it.
APFS, HFS+ and local snapshots
APFS or APFS Encrypted is Apple's preferred format for a current Time Machine destination. Existing Mac OS Extended backups can still appear in older setups; upgrading macOS does not make every attached backup disk identical. Finder's Get Info window shows the selected disk's format.
| Backup type | How it is organized | Useful recovery route |
|---|---|---|
| HFS+ / Mac OS Extended destination | Backups.backupdb, machine and dated backup folders. | Time Machine restoration or copying readable files from a completed date. |
| APFS destination | APFS backup snapshots. | Time Machine or tmutil using a mounted backup path. |
| Network destination | A backup disk image stored on the network share. | Restore through Time Machine when the share and image are accessible. |
| Local snapshot | An APFS snapshot on the Mac's own storage. | Time Machine can use it when the external backup is unavailable. |
Apple's disk-format guidance describes supported destinations. The local snapshot is particularly useful when you deleted a recent file and the external backup has failed, but it lives on the same hardware as the original file.
Use tmutil listlocalsnapshots / to see available local snapshots. Time Machine normally offers them automatically when restoring without the external disk. Apple says it keeps hourly snapshots for about 24 hours and removes snapshots as space is needed; it also retains an additional last-successful-backup snapshot until space is needed.
The local-snapshot documentation explains those limits. A dead internal drive takes those snapshots out of reach along with the live files. They are useful recent versions, but the external copy still matters.
Time Machine protects files such as your apps, documents and photos that were not part of the macOS installation. Apple's backup overview describes that scope. A cloud placeholder also needs its actual file available locally to be copied; syncing and an independent backup serve different purposes.
Repair a preserved backup, or recover its readable contents
First Aid checks formatting and directory structures. Once the needed files have another verified copy or the backup disk is imaged, open Disk Utility and choose View, Show All Devices. Start First Aid at the last volume under the backup device, then work upward through volumes and containers to the device itself, following Apple's repair order.
An error that First Aid cannot repair can reflect file system damage even without a mechanical fault. Repeating the same unsuccessful repair adds little. Recovering readable files from the preserved copy may be more useful than trying to make the original backup usable for future automatic backups.
For a stable disk whose file system cannot be opened, recovery software can work from a full disk image. Disk Drill's byte-to-byte backup function saves an image to separate storage, and its scan guidance explains scanning that image. The destination needs room for the image and any recovered files.
TestDisk can locate supported lost partitions, including APFS signatures, but that is different from rebuilding a Time Machine history. Its supported-function list separates partition detection from file recovery. Choose a recovery method for the actual file system and save extracted files outside the source image.
A drive with physical failure needs a hard drive recovery assessment before software can make a useful copy. The same applies when the only backup is inside an inaccessible Time Capsule or NAS: first determine whether access failed at the network, enclosure or disk. A network error does not require dismantling the storage device.
If the backup was accidentally erased, a new file system may have overwritten some old information. On an SSD, deallocation through TRIM can make previous contents inaccessible before a physical erase has finished; the SSD controller's cleanup process is separate from ordinary file copying. Encryption and missing backup metadata can further limit what a scan retrieves.
After the wanted files are safe, a new Time Machine destination can provide future protection without relying on the damaged disk. Open a few restored documents and photos from that completed backup. Seeing their contents checks something the “backup finished” notification cannot show you.
Get help with data recovery
Bring your device to our Lincroft lab during opening hours, or mail it in.
How to mail your deviceThe $100 diagnostic is non-refundable once diagnostics start, and donor drives or replacement parts you approve are non-refundable once ordered, even if recovery fails.
Published by MDrepairs
MDrepairs is a data recovery and electronics repair lab in Lincroft, New Jersey. Our founder and lead technician Joseph Montanti films real cases for our YouTube channel, showing tools, repair steps and recovery outcomes.
Keep reading
- External Drive Says “The Parameter Is Incorrect”: Data-Safe Checks
- External Hard Drive Freezes File Explorer or the Computer: Safe Next Steps
- “The Semaphore Timeout Period Has Expired” During a Drive Copy
