Time Machine backup estimate

You plug in your backup drive, Time Machine kicks off, and then you see it: a Time Machine backup estimate of roughly one month. One. Month. I've seen this on dozens of Macs and the reaction is always the same. People assume something is catastrophically broken, start Googling, and end up with a pile of contradictory advice that either doesn't apply or makes things worse. So here's what actually works, based on fixing this problem regularly.

What Causes a Bad Time Machine Backup Estimate?

Before throwing fixes at it, it helps to understand what's actually going on. Time Machine calculates its estimate by looking at how much data it needs to copy and dividing that by the current write speed to the destination. So if the estimate says one month, it's basically saying: at the speed I'm currently writing, this will take 720 hours. That's either a sign of an enormous amount of data, a very slow drive, or both.

The most common cause by far is a first backup on a Mac with a large internal drive. If you've got 500 GB to 1 TB of data and you're backing up to a traditional spinning hard drive over USB 2.0, the maths genuinely does produce horrible estimates. A slow USB hard drive might sustain 20 to 30 MB/s in real-world conditions. At 25 MB/s, backing up 600 GB takes roughly seven hours. That's fine. But if the drive is struggling, dropping to 5 MB/s, the same job becomes 33 hours. Add some restarts and you're looking at days, not hours.

The second big culprit is Spotlight indexing. When macOS is indexing your drive (which happens after an update, a migration, or when you first plug in a new drive), it hammers the disk constantly. Time Machine is competing for the same read bandwidth. The backup slows to a crawl, the estimate balloons, and people panic. The fix here is just to wait. Spotlight finishes, disk pressure drops, and the estimate comes back down.

Then there's the disk format issue. Time Machine needs either APFS or Mac OS Extended (Journaled) as the destination file system. If someone has plugged in a drive that was previously used with Windows and formatted as exFAT or FAT32, Time Machine will either refuse to use it or behave very strangely. This one catches people out more than you'd expect.

Repeated disconnects are another nasty one. If the cable is loose, the hub is unreliable, or the drive is going to sleep mid-backup, Time Machine can't finish its current pass. It marks the backup as incomplete and starts again next time. You end up in a loop where the backup never actually finishes and the estimate just keeps resetting. Worth knowing: if you're curious how to track actual completion times from the command line, our article on cmd show completion time covers how to surface that information on macOS.

Finally, there's drive health. An ageing hard drive with bad sectors will retry writes repeatedly, grinding the effective speed down to almost nothing. The drive might not be dead yet, but it's struggling. This is the scenario where the estimate genuinely does keep climbing rather than settling, and it's the one that warrants the most urgent attention.

Time Machine Backup Estimate Quick Fix

Start here. These steps take five to ten minutes and fix the problem for most people.

More Time Machine Backup Estimate Solutions

If the quick fix didn't sort it, these intermediate steps cover the most common underlying causes. Most people find the answer here.

Advanced Time Machine Backup Estimate Fixes

These steps are for situations where the basic fixes haven't worked, the estimate keeps climbing, or backups seem to be stuck in a loop. You'll need Terminal for some of this, but nothing here is particularly risky if you follow the steps carefully.

Worth mentioning: if you're running into backup issues on Windows machines in your household or office as well, the troubleshooting logic is quite different. Our Windows backup shareware troubleshooting guide covers the common failure points on that side of the fence.

One more thing on the software side. Time Machine is Apple's built-in solution and it's genuinely good for most people. But if you're finding it consistently unreliable, especially for large datasets or network destinations, it's worth knowing that dedicated backup clone software exists that handles these scenarios better. These tools give you more control over scheduling, exclusions, and destination management, and they often produce faster initial backups because they're optimised specifically for cloning large volumes. We'll have a specific recommendation in this space shortly.

Preventing a Slow Time Machine Backup Estimate

Most of these problems are avoidable. Here's what actually makes a difference, in order of importance.

Keep the drive connected permanently. This is the big one. If Time Machine can run its small hourly incremental backups, it never has to do a massive catch-up job. People who disconnect their backup drive for weeks and then reconnect it are essentially forcing a near-full backup every time. The estimate goes through the roof because the job genuinely is enormous.

Use decent hardware. A USB 3.0 or Thunderbolt SSD will back up your Mac several times faster than an old spinning hard drive on a USB 2.0 connection. The difference isn't marginal. We're talking about a job that takes 12 hours on a slow drive finishing in under 2 hours on a fast one. If you're buying new backup hardware, spend a bit more on an SSD. It's worth it.

Exclude the right things. Virtual machine images, game libraries, and video scratch disks change constantly and are often enormous. They create huge amounts of churn in your backup set. Exclude them and back them up separately (or accept you'll reinstall them if needed). Your actual documents, photos, and application settings are what Time Machine is really for.

Check that backups are actually completing. The Time Machine menu bar icon will show the last successful backup time. If that date is weeks ago and you thought it was running fine, something has been silently failing. Make it a habit to glance at it occasionally.

Don't ignore slow backups. If your backups used to take two hours and now they're taking ten, that's a warning sign. Drive wear, cable degradation, and connection issues all creep up gradually. Catching them early means you still have a working backup when the drive eventually fails. Replacing a backup drive proactively is a lot less stressful than discovering it died the same week your Mac's internal drive gave up.

Time Machine Backup Estimate: Summary

A Time Machine backup estimate of one month is alarming but almost always fixable. The vast majority of cases come down to one of three things: a large first backup on slow hardware, a dodgy or indirect drive connection, or a disk format problem that's been silently causing issues. Work through the solutions in order, starting with the connection check and disk format verification, and you'll almost certainly find the culprit before you get to the advanced steps.

The key things to remember: don't stop a running backup (it just resets progress), make sure the destination is formatted correctly, exclude large files that don't need versioning, and keep the drive connected so Time Machine can do its job in small chunks rather than one giant catch-up run. Get those basics right and your Time Machine backup estimate should stay sensible going forward.