Stop all disk writes immediately: if a Time Machine restore failed and the data on your backup disk or your Mac matters, do not keep retrying, do not erase anything, and do not let the backup disk accept new backups until you know what is wrong. Most failed restores come from a loose connection, a full or unhealthy backup disk, or security software getting in the way, and all of those can be checked without risking your backup. If the checks below point to a failing drive, a soldered SSD that will not boot, or a damaged backup volume, a lab can image the disk safely before anything else is tried. We are Macwest Data Recovery & Mac Repair, in business since 2006 at 12041 Wilshire Blvd, Ste 26 in West Los Angeles, and we offer same-day appointments at (310) 866-0828.
A restore copies the files, apps and settings from your backup disk onto the Mac. You can do it in two main ways: through Migration Assistant, which Apple describes in its guide to restoring your Mac from a backup, or by starting from macOS Recovery and restoring the whole system from a Time Machine backup. Which one you use depends on the situation. Migration Assistant fits a new Mac, or a Mac that has just been freshly set up with macOS. Recovery fits a Mac whose startup volume is damaged or erased.
Two details from Apple’s guide explain many reports of a restore that seems frozen. A large transfer through Migration Assistant can take several hours and may appear to pause along the way. And if an account with the same name already exists on the Mac, you are asked to replace it or rename the old one, so a restore that sits on a prompt may simply be waiting for your decision. If the progress bar has not moved for a very long time, our guide to what to do when Migration Assistant is stuck walks through how to tell a slow transfer from a dead one.
If you want a refresher on how the backups themselves are structured, we cover that in our Time Machine overview.
Apple’s support article on what to do when you cannot back up or restore with Time Machine points to a short list of causes: not enough storage space, connection problems, and VPN or other third-party security software affecting the connection to the backup disk. Apple also advises that a backup disk should ideally have at least twice the storage capacity of the Mac being backed up. A disk that is only slightly larger than your Mac has probably been pruning old backups for years, and that leaves little margin when a restore has to read a large amount of data.
In our lab we see the same pattern. A restore rarely fails for a mysterious software reason. It fails because the disk it reads from is unreliable, and the error message is the first visible symptom.
The table below matches what you see on screen to the most likely cause and the safest next step. It is a triage guide, not a diagnosis.
| What you see | Most likely cause | Safest next step |
|---|---|---|
| Backup disk does not appear in Migration Assistant or Recovery | Cable, port, hub, or power problem; or the disk is failing | Connect directly to the Mac, try another cable and port, check Disk Utility |
| Restore starts, then stops with an error partway through | Unreadable data on the backup disk or an unstable connection | Run First Aid on the backup disk; copy a large file to test the connection |
| Progress sits at “calculating” or “preparing” for hours | Very large backup, indexing, or a slow network backup | Wait, then check the connection; for a network backup, try a wired link |
| Disk is reported as read-only | File system problem on the backup disk | Run First Aid; do not erase |
| Disk clicks, beeps, or repeatedly disconnects | Mechanical failure of a hard drive | Power it off and call a lab; do not keep retrying |
| Restore works, but the Mac will not boot afterward | Damaged startup volume, or a logic board or storage fault | Boot to Recovery and check the internal drive; book a hardware diagnosis |
| Backup is missing recent files or the system itself | Backups were incomplete before the failure | Restore what exists, then look for the missing files elsewhere |
Work through these steps in order. Each one is non-destructive, so none of them can make your backup worse.
Only after all of this, and only if you have a second copy of what is on the backup disk, does Apple’s last resort make sense: erase the disk and set it up again as a backup disk, or try a different disk. Erasing destroys what is on it, so it is not a recovery step. It is a way to get a working backup going again.
Backups stored on a NAS or another Mac over Wi-Fi are slower to read and fail more often during a long restore, because any dropout interrupts the transfer. Switch to a wired Ethernet connection if you can, turn off the VPN, and check that no firewall is blocking file sharing. If the NAS is a business device with RAID 1 or RAID 5 volumes, a degraded array can look like a Time Machine error when it is really a drive that has dropped out of the set. In that case, do not rebuild the array until the data has been imaged.
If your office network is part of the problem, a provider of backup and recovery IT support can help with Wi-Fi, Ethernet, firewall and network-attached backup issues on the network side.
Sometimes a failed restore is the first sign that something else is wrong. Three situations come up repeatedly.
A hard drive that clicks, spins up and down, or vanishes from Disk Utility should be powered off. Every retry on a drive with damaged heads or surface can destroy readable data. Time Machine backup volumes are also often on external drives that have seen years of use, and a drive that was fine for backups can fail under the sustained reading of a full restore.
If First Aid reports that it could not repair the volume, or the disk mounts but the Backups.backupdb folder is empty or will not open, the file system structure is damaged. Modern Macs use APFS, and Time Machine backups on APFS disks store snapshots in a different way from older HFS+ backups, so a repair that is safe on one is not always right for the other. A lab can image the disk sector by sector and work on the image, so the original is not stressed further. Our guide on imaging before repair when a drive will not mount explains that process, and this guide to an external drive that will not mount covers the first checks.
If the restore fails because the Mac cannot see its own internal storage, or it restores and then will not boot, the cause may be on the logic board. Recent Macs have soldered storage, with the NVMe controller and NAND on the board itself, so you cannot pull the drive and read it on another computer. That moves the job from drive recovery to component-level logic board repair, which is the work our in-house engineers do with micro-soldering and forensic imaging. FileVault encryption adds a further constraint: data can be read only if the board and its security components are working or restored, which is one more reason not to experiment.
The line between a fixable restore and a recovery job is clearer than most people think. Stop and get professional help if any of these are true:
The reason to call early is practical. A drive that has just started to fail often gives up a full image. After a week of repeated restores and utility runs, that same drive may not. The data is the same, but the chance of getting it back is smaller.
We start with free diagnostics. We look at the backup disk and the Mac to find out which one holds the fault, and then we tell you the cost before any recovery work begins. Our “no recovery, no charge” policy means that if we cannot get your data back, you do not pay for the recovery. We handle hard drives, SSDs, RAID and NAS systems, and memory cards, and we repair MacBook, iMac, Mac mini and Mac Pro hardware, including liquid damage and logic board faults, so a case where the drive and the Mac are both involved stays in one lab.
We serve West LA, Santa Monica and Beverly Hills, and we work with customers in Brentwood, Westwood, Venice, Hollywood and Culver City. Our lab sits at 12041 Wilshire Blvd, Ste 26, between the 405 and Santa Monica, near UCLA and the Getty Center, so you can bring the equipment in person instead of mailing it. If you cannot wait, ask for a same-day appointment on (310) 866-0828. You can see the full range on our Mac data recovery service page, and for a Mac that will not start we have a Mac repair service in Los Angeles.
A Time Machine restore is the moment a backup is tested for the first time, and that is why it fails when people are least ready. Most backup disks go for years without anyone reading them in full. Small errors accumulate: a bad sector here, a cable that is slightly loose there, an external enclosure that has been dropped once. Backups keep appearing to succeed because writing a little new data does not touch the damaged areas. A full restore reads everything, and that is when the weak spot shows up.
We also see a second pattern, which is that the first response makes things worse. People retry five times, run three repair utilities, then erase the disk to “start fresh,” and the data they needed was on that disk. Our advice is the same every time: once a restore has failed on an important disk, do not write to it, do not erase it, and do not open the enclosure. Image it first. Working from an image means that every later attempt is made on a copy, and the original stays as it was when it arrived.
Finally, a backup is only one copy. If the Mac and the backup disk both fail, as happens in a power surge, a theft, or a spill that reaches the desk, there is nothing left to restore from. Our guides on data backup best practices and examples of data backup methods cover keeping a second copy somewhere that does not share the same risks.
— Kaya
Once you have your files back, spend twenty minutes to avoid repeating this.
For a deeper look at backups that hang rather than restores, see our checklist for a Time Machine backup that is stuck.
The most common reasons are an unstable connection, a very large backup that takes hours, or a backup disk with unreadable areas. Connect the disk directly to your Mac without a hub, try a different cable and port, and give a large Migration Assistant transfer time, since Apple says it may take several hours and seem to pause. If the progress does not change after that and the disk is making noise, power it off and call us.
Stop all disk writes immediately: cancel the restore, pause backups to that disk, and do not erase it. Then check the cable, the port and whether the disk stays visible in Disk Utility. Those checks cost nothing and cannot damage the backup.
Sometimes. Apple lists using First Aid in Disk Utility to repair the backup disk as a standard step, and it is the right first repair attempt for file system errors or a read-only disk. If First Aid fails, hangs, or the disk is clicking, stop there, because further repair attempts on a failing drive can reduce what is recoverable.
Only if you no longer need anything on it or you have another copy. Apple’s guidance treats erasing the disk, or using a different one, as a last resort for a disk that will not work as a backup. Erasing does not recover data, it removes it, so for an important backup, get the disk imaged first.
Yes. We recover data from failed backup disks, internal drives, SSDs, RAID arrays and NAS devices, and we repair the Mac itself if the logic board or storage is at fault. Diagnostics are free, there is no charge if we cannot recover your data, and same-day appointments are available at (310) 866-0828.
Your Mac chimes but the screen stays black? Learn what the chime means, which safe…
How long a MacBook battery replacement takes: hours at a local Mac lab, 3 to…
Does the freezer trick recover a dead hard drive? Learn why it fails on modern…
Data recovery diagnostics explained: what a free assessment checks, how physical and logical failures differ,…
Deleted files from an SSD with TRIM enabled: what is realistically recoverable, what to do…
How to encrypt an external drive on a Mac, unlock it, and what to do…