I have MacBook Pro (2.3GHz Intel Core i7, 16 GB RAM, 512 GB SSD - late 2013?) and Time Machine backups data via network to our internal OS X Server. But when Time Machine is running backups, my computer is completely frozen. Webpages are not loaded, Apple Mail doesn't load/show messages at all, etc. But my colleague doesn't have such problems with his MacBook with the same HW configuration.

What could be wrong?

  • Have you looked at pondini.org/OSX/Home.html? Aug 17, 2015 at 11:51
  • You mention two apps that depend on networking to work properly; are other, non network related apps affected? Aug 17, 2015 at 11:51
  • @JaimeSantaCruz - yes, the whole system is completely frozen.
    – jnemecz
    Aug 17, 2015 at 11:52

1 Answer 1


I found an article that suggests some troubleshooting steps, I'll summarize it here:

  1. Test the drive: copy some files to find out if your read / write speeds are normal. This will help you rule out your internal or server drive.
  2. Check the drive for errors: Again, you can check internal and server drives for errors (bad blocks, permission problems).
  3. Run a general maintenance routine: you can follow the steps they propose here.
  4. Back up in Safe Mode: reducing the system to a bare minimum may help in isolating the problem.
  5. Uninstall or disable drive-monitoring or scanning utilities: Antivirus and other drive scanning software may get triggered by Time Machine activity.
  6. Disable Spotlight: and check for other processes that may be scanning the disk permanently.

There are a couple of additional suggestions on the article, check it out if this steps do not solve your issue and for a full description of each step.

Also, your colleague may provide a good comparison for troubleshooting: you said your hardware is identical, so:

  • Is the software setup the same? Any differences may point out the culprit.
  • If software setup is similar, testing hardware on both machines can give you comparison points. For instance, what happens if they use the same Time Machine destination?

Finally, check the Activity Monitor prior to and while Time Machine is running, to single out resource hogs.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .