Fix Time Machine When Stuck on “Preparing Backup” in Mac OS X

Mar 31, 2014 - 27 Comments

Time Machine Time Machine is by far the simplest way to keep regular and reliable backups of a Mac, and usually the automatic backups start and finish without any incident. On some rare occasions though, Time Machine may get stuck* on the “Preparing Backup” stage for an inordinately long amount of time, causing a backup to never start, let alone finish. It’s these failed backup attempts that we’re looking to remedy here.

We should point out that if you haven’t backed up a Mac in a while, say a few months, it’s normal for the “Preparing Backup” stage of Time Machine to take a while to gather data before beginning, particularly if you have a large drive to backup. What’s not normal is for the Preparing Backup stage to take 12-24 hours, getting stuck in that stage overnight or all day long, for example (unless perhaps you have some truly absurd amount of disk space, then it may take that long and be normal).

Time Machine stuck on Preparing Backup

Anyway, having consistent and reliable backups is important, so lets fix this specific Time Machine issue in OS X.

Stop the Currently Failing Backup Attempt Before Beginning

The first thing you need to do is cease the currently failed backup attempt while it is stuck on “preparing backup”, this is easy enough:

  • Open the “Time Machine” settings panel within System Preferences (get there from the  Apple menu or Time machine menu)
  • Click the little (x) icon until the backup attempt stops

Stop a Time Machine Backup

When the progress bar disappears and it no longer says “Preparing backup…” you’re good to begin the troubleshooting process outlined below.

1: Trash the “inProgress” File

Now that the backup is stopped, the first thing to do is trash the Time Machine placeholder file found on the backup drive:

  1. Open the Time Machine drive in the Finder and navigate to the “Backups.backupd” folder
  2. Open the folder within Backups.backupd that is the name of the current Mac which is stuck on preparing
  3. Put this directory into “List View” and sort by ‘Date Modified’, or just search the folder for a file with a “.inProgress” file extension
  4. Delete the “xxxx-xx-xx-xxxxxx.inProgress” file

Time Machine inProgress file

The .inProgress file is always in the form of xxxx-xx-xx-xxxxxx.inProgress, where the first 8 digits are the year-month-day (date) and the next 6 or so digits are random numbers, followed by the inProgress file extension.

Just trash that file, it should be about 3kb or so.

2: Reboot with the Time Machine Drive Connected

Next, give the Mac a good old fashioned reboot while the Time Machine drive is connected to the Mac, you’ll see why that matters in a moment:

  1. Pull down the  Apple menu and and choose “Restart”
  2. Once booted, let Spotlight run completely (you can either just wait it out or watch the mdworker, mrs, and related processes in Activity Monitor)

This should cause OS X to re-index the attached Time Machine drive if it’s needed, which may be getting in the way of Time Machine backing up properly thus causing the computer to get stuck on “Preparing Backup” for a very long time. Even if the drive has been recently indexed by Spotlight, a reboot still appears to be necessary, whether to resolve whatever issues are occurring with backupd or not.

3: Initiate a Backup as Usual

Now that the Mac has rebooted with the Time Machine drive connected, you can start a back up yourself. The easiest way to do this is through the Time Machine menu icon or the System Preferences:

  • Pull down the Time Machine icon and choose “Back Up Now”

You will still see a “Preparing backup…” message but it should be gone within a few minutes, depending on the size of the hard drive, the speed of the Mac, and the size of the backup to be made. At this point, your Time Machine backup will proceed as expected, so just let it run and you’re good to go again.

* For those who like to get technical, when “preparing backup” gets stuck, the actual ‘backupd’ process is usually doing nothing at all, with no disk activity or CPU usage shown from Activity Monitor, fs_usage, and opensnoop. Admittedly a bit advanced, but those tools show a definitive way to demonstrate this specific issue and resolution.

Enjoy this tip? Subscribe to the OSXDaily newsletter to get more of our great Apple tips, tricks, and important news delivered to your inbox! Enter your email address below:

Related articles:

Posted by: Paul Horowitz in Mac OS X, Tips & Tricks, Troubleshooting


» Comments RSS Feed

  1. This is awesome. Thanks for posting! Time Machine is great, but when it misbehaves, it’s hard to understand how to fix it.

  2. Thanks for another useful article, but how about the other end of the process when TM reports, “Cleaning Up” for ages? (Actually doing it as I write this)

  3. Kees says:

    Thanks for the useful post!
    The six ‘random’ digits in the inProgress file actually show the time, displayed in 24-hour notation: hhmmss.

  4. Ed says:

    Great stuff.

    How about a further article telling us how to fix the issue if TimeMachine resides on a network drive!

  5. r says:

    Why even bother with mdworker on the backup disk? Put the backup drive into Spotlight’s privacy section so it never indexes it. Done.

  6. buck says:

    I would suggest checking console and filtering for backupd before going through this process. If it’s doing a deep event scan then it is normal for it stay on preparing for a long time and should be left alone.

    • Ph says:

      sudo fs_usage backupd will tell you what it’s doing, if it’s doing nothing then it’s safe to proceed

      • buck says:

        That is not completely accurate. That just displays File-system usage for backupd. There are actions that wouldn’t fall under that. I would suggest using console to be certain.

  7. TT says:

    Sorry about the stupid question, not very computer savvy here, but what does “Once booted, let Spotlight run completely (you can either just wait it out or watch the mdworker, mrs, and related processes in Activity Monitor)” mean?
    How do I make the Spotlight run? Do I need to start anopther program or what? Can you please explain this bit — what should I exactly do?


    • Martin says:

      The Spotify magnifying glass in the top right. If you click it you’ll see an “Indexing Network” window appear, unless the indexing has finished of course :-)

  8. Catherine Kelleher says:

    I had same problem with preparing backup getting stuck, i deleted inprogress back up and restarted. I started new back up now saying 16 hours remaining? Why is this

  9. Daemion Cunningham says:

    What do you mean by, let Spotlight run completely?

  10. Joseph N. says:

    I deleted the .inprogress file and restarted. Prompted TM to “back up now”. 24 hours later it was still saying “Preparing Backup…”
    Stopped it and once more I deleted the file, restarted and asked TM to backup.
    I was hopping it will start backing up before I have to go on mandatory Social Security retirement.
    What could I be doing wrong? Other people were successful getting TM to work using the outlined steps.
    My external TM still has 34.5 GB available (on a 3TB external FW HD).
    Would appreciate any help I can get. Thanks.

  11. stephan says:

    FWIW, my “Preparing Backup…” also seemed to be irrevocably stuck, with nothing suspicious in the Console logs and not too much disk activity to be noticed. But I then opened terminal and ran

    sudo fs_usage backupd

    as suggested by Ph in one of the comments. And judging from the output it is actually traversing the entire file system for attribute data (which takes time, even though it is not causing as much I/O in Activity Monitor as I had imagined)…

    I imagine this is equivalent to a deep traversal, even though the logs do not mention that one was required. So the only thing here will be to sit it out – stopping the backup presumably just means the partial traversal will be discarded before a backup is completed and the state saved for the next iteration…

  12. John says:

    I’m having this problem since changing to a time capsule for wireless backups. But I cannot see anything like you describe. Instead of the Backups.backupd file I used to have with my old attached hard drive, I now have a folder called bands which contains literally thousands of files called things like 1a50d up to eb48 and also files,,, Info.bckup, token, Info.plist.

    So I can’t even do manual restore anymore.

    Any idea what’s going on here?

    • kjw says:

      I also have a folder called bands and nothing else. Mine doesn’t even show the file names as the spinning indicator icon never stops spinning. Since I can’t see the disk in disk utility I can’t even fix it in disk utility…. Don’t know if you are using OS X yosemite but for me its been a complete disaster. Worst OS X upgrade ever. Terrible Wifi connectivity.

  13. Mark Armstrong says:

    Last back up was 19 March 2014. It might have been the time I upgraded to Lion but I’ve moved house etc.

    Anyway, followed your instructions but the deleting of .inprogress file unsuccessful.
    The process just keeps on showing the revolving blue/white bar.
    Items to delete shown as 0.
    Any ideas how to progress?
    Thanks for original post.

  14. Mark Armstrong says:

    Re above comment.
    Just noticed that all other items are folders.
    The in.Progress item I an trying to delete is a ‘package’

    Really doesn’t want to be deleted!

  15. Keith Mewes says:

    Simple fix that worked for me.

    I have a client’s MBP with issues due to the 250GB HDD being full. I wanted to run a backup before messing with the disk (it had never been backed up before).

    I plugged in a new Seagate USB3 HDD and started a TimeMachine backup. After more than 12hrs it was stuck on the indexing problem.

    Followed your instructions and now it is backing up without mentioning the indexing step!

    Thank you.

  16. John Holland says:

    I tried all of these procedures on my Leopard 10.5.8 partition. Nothing has worked. I am now getting cycling between Preparing…, Finishing… for several hours. Indexing took over 3 hours. Last backup was 2 weeks ago. backupd activity continues to indicate both CPU and Disk Activity. Backup disk image shows on my Desktop and backup Time Capsule Data file shows in finder window. Guess I’ll just let it continue for a couple more days, don’t know what else to do.

  17. Paul Jackson says:

    Followed the instruction and it worked first time for me, thanks.

  18. Peter Robinson says:

    In the latest Yosemite, these instructions no longer seem valid.
    — the Backups.backupdb folder is NOT in the time machine volume now, accessible through the folder. Instead, you need to locate it through Finder->Go->Go to folder and there enter
    /Volumes/Time Machine Backups/Backups.backupdb/
    –You will then see the name of the machine you are backing up. Double click on the folder, and you will get the list of devices you are backing up, including yours.
    — the xxxx-xx-xx-xxxxxx.inProgress is NOT a file, about 3kb or so. It is now a “package”, 5.3 GB in my device.
    — I deleted this package from the folder; I had to give my password to do so
    I did not attempt to reboot, etc. As far as I can see, in Yosemite this does nothing relevant to time machine.
    Now, having done that — I still seem to be no further advanced. Time machine is still “preparing backup”, as it has been for several days now. The “in progress package” is still, well, in progress, growing ever large.

Leave a Reply


Shop for Apple & Mac Deals on

Subscribe to OSXDaily

Subscribe to RSS Subscribe to Twitter Feed Follow on Facebook Subscribe to eMail Updates