Time Machine Backup Taking Forever on Mac
Short answer
A first backup copies everything, so 500GB over USB 3 takes roughly 4-8 hours and the same over Wi-Fi can take two days. Check real progress with tmutil status in Terminal rather than the menu bar estimate, which is unreliable for the first hour. A backup is only stuck if the bytes copied figure stops increasing for over an hour.
On this page
The first Time Machine backup is slow in a way that makes people assume it has failed. Ten hours in, the estimate still says six hours remaining, and the number has barely moved since lunch.
That is usually correct behaviour. Time Machine’s first run copies your entire startup disk — system, applications, documents, photo library, every one of the several million small files macOS keeps. Subsequent backups copy only changes and finish in minutes.
What normal looks like
| Destination | Approximate first-backup time per 500GB |
|---|---|
| Thunderbolt or USB 3 SSD | 2-4 hours |
| USB 3 hard disk | 4-8 hours |
| USB 2 hard disk | 15-30 hours |
| Network drive over ethernet | 8-20 hours |
| Network drive over Wi-Fi | 24-48 hours |
The spread is mostly about the destination, not the Mac. A spinning hard disk writes small files slowly, and a Time Machine backup is overwhelmingly small files. Wi-Fi adds protocol overhead on top of a slower link.
If your figures are in the right column’s range, nothing is wrong and the correct action is to leave it plugged in overnight.
Check real progress, not the estimate
The menu bar estimate is calculated from recent throughput and is close to meaningless during the first hour, when Time Machine is still scanning. For a figure that actually means something, open Terminal (Applications → Utilities → Terminal):
tmutil statusYou get the current phase and, during copying, bytesCopied and
totalBytes. Run it twice a few minutes apart. If bytesCopied has increased,
the backup is working regardless of what the estimate claims.
The phase field is the other useful part. PreparingSourceVolumes and
FindingChanges mean it has not started copying yet — normal, and on a disk
with a large number of files it can last twenty minutes or more before the
first byte moves.
When it is genuinely stuck
Three signs, and you need at least one:
bytesCopiedunchanged for over an hour with the Mac awake.- The same backup restarting from zero repeatedly.
- An error about the backup disk being unavailable or read-only.
Work through these in order.
Restart the Mac and the drive. Eject the drive properly, restart, reconnect. This clears a surprising share of stalls, particularly ones that began after a macOS update.
Check the cable and the port. A backup that crawls on one port and runs normally on another is a cable or hub problem. Connect the drive directly to the Mac rather than through a hub or display for the first backup.
Look at the drive’s own health. Disk Utility → select the drive → First Aid. A disk developing bad sectors slows to a crawl before it fails outright, and Time Machine hitting those sectors looks exactly like a stall.
Check for a process holding the disk busy. Open Activity Monitor, set View
to All Processes, and look at the Disk tab. backupd should be near the top. If
something else is competing — an indexer, a sync agent — the backup is sharing
bandwidth it needs. A Mac running hot with nothing
open covers reading that screen
properly.
Exclude what you do not need backed up
The fastest backup is a smaller one. System Settings → General → Time Machine → Options holds the exclusion list.
Worth excluding on most Macs:
- Virtual machine disk images, which change wholesale and get recopied every backup.
- Docker’s disk image, for the same reason.
- A downloads folder full of installers.
- Media libraries already backed up elsewhere, if you are certain they are.
Worth keeping in: everything else. The temptation to exclude the system folder to save time is a mistake, because a backup without it cannot restore a working Mac, only files.
Spotlight and the first backup
Spotlight indexes the new backup volume while Time Machine is writing to it, which means two processes fighting for the same disk. On a mechanical drive the effect is noticeable.
macOS normally handles this sensibly, but if you have a Mac where indexing seems to be competing badly, what to do when Spotlight indexing gets stuck explains how to check and, if necessary, exclude the backup drive from indexing.
Backups that start over every time
A backup that never completes and restarts from the beginning is a different fault from a slow one. The usual causes:
- The drive disconnecting mid-backup. Sleep settings, a loose cable, or a bus-powered drive that browns out. Keep the Mac plugged in and prevent sleep while the first backup runs.
- A corrupted sparsebundle on a network destination. Network backups are more fragile than direct-attached ones and occasionally need deleting and starting fresh.
- The drive being full with no room to thin old backups. Time Machine deletes the oldest backups automatically, but a drive smaller than your data cannot hold even one.
Realistic expectations
Leave the first backup running overnight with the lid open and the Mac on power. Most finish by morning. Once that one completes, hourly backups copy only changes and typically take one to five minutes, which is why nobody notices Time Machine again until they change drives.
The honest limit is the hardware. A USB 2 enclosure or a Wi-Fi network destination will never be fast, and no setting fixes that. If a first backup over Wi-Fi is impractical, connect the drive directly for the initial run and move it to the network afterwards — the incremental backups are small enough that the link speed stops mattering.