All Time Machine backups take too long

2018 Mac mini running macOS 12.6.1. I have an 8TB USB drive connected to the machine with two volumes on APFS. One volume I use to Time Machine backup my laptop over the network, and that seems to work just fine. The other volume is a local Time Machine volume for the mini. This is a fairly new disk and it was all working fine for a couple of weeks, but now the local backup takes forever and seems to find hundreds of thousands of files to backup. It takes over 24 hours to complete. Then the next time Time Machine starts, it all happens again, hundreds of thousands of changes found and it runs for 24+ hours. It's almost like the mini doesn't recognize that it only has to do an incremental backup. I know for sure there aren't all that many changes between each backup run. I've double checked the Excludes From Backup options and that all looks reasonable (it excludes both the local and remote TM volumes, iCloud, OneDrive, and Dropbox folders). I can't find anything else that would include so much changes. It estimates the size of a full backup at 1.68TB which appears to be the entire Macintosh HD (303.64GB available of 2TB). I can't find any other settings that would cause TM to do a full backup every single time and I've rebooted the machine at least once to see if that fixes the problem, to no avail.


I can't upgrade this machine to Ventura yet due to compatibility issues. Any ideas what's going on or what to look for?

Mac mini 2018 or later

Posted on Dec 2, 2022 5:29 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 31, 2022 4:02 PM

Following up with the resolution and information I've found.


Thanks for the BackupLoupe recommendation. It's a great tool and ultimately provided me with exactly the information I needed to figure out what was going on. Aside: I've had some trouble with BL getting stuck when indexing aborted TM backups, but the company/developer behind it is responsive and we're trying to work out the resolution of that problem.


For my TM performance problems, BL not only helped me identify old cruft that I didn't need (like Application Support files for apps I no longer use or have installed), but it also helped me understand why it was mysteriously trying to back up huge amounts of small files. Not only did this consume too much of my TM partition, but it also is what I think caused the backup to take so long. It turns out that I use the Backblaze online backup service, and that has a cache folder that contains copies of files during upload, log files, etc. Once I excluded /Library/Backblaze.bzpkg from my TM backups, performance returned to what I expected and seems to be operating well now. I confirmed with Backblaze that it's essentially okay to exclude this directory from TM. It'll cause a little extra work to recover things if I lose /Library/Backblaze.bzpkg and need to do a Backblaze restore, but it's fairly easily recovered and it doesn't compromise my backups.

Similar questions

19 replies
Question marked as Top-ranking reply

Dec 31, 2022 4:02 PM in response to Tesserax

Following up with the resolution and information I've found.


Thanks for the BackupLoupe recommendation. It's a great tool and ultimately provided me with exactly the information I needed to figure out what was going on. Aside: I've had some trouble with BL getting stuck when indexing aborted TM backups, but the company/developer behind it is responsive and we're trying to work out the resolution of that problem.


For my TM performance problems, BL not only helped me identify old cruft that I didn't need (like Application Support files for apps I no longer use or have installed), but it also helped me understand why it was mysteriously trying to back up huge amounts of small files. Not only did this consume too much of my TM partition, but it also is what I think caused the backup to take so long. It turns out that I use the Backblaze online backup service, and that has a cache folder that contains copies of files during upload, log files, etc. Once I excluded /Library/Backblaze.bzpkg from my TM backups, performance returned to what I expected and seems to be operating well now. I confirmed with Backblaze that it's essentially okay to exclude this directory from TM. It'll cause a little extra work to recover things if I lose /Library/Backblaze.bzpkg and need to do a Backblaze restore, but it's fairly easily recovered and it doesn't compromise my backups.

Dec 12, 2022 12:25 PM in response to pumpichank

pumpichank wrote:


Since the MyBook is a rotational drive, maybe it would be better to format it with HFS+ instead?

Thanks for providing the diskutil output. That verifies, to me, what the actual configuration of this drive is.


Yes, I would suggest that you reformat the drive for HFS+. You can then create as many partitions as required for how you want to use this drive. Alternately, if you only plan on using it for Time Machine, one partition would be sufficient, as TM will create separate files for each Mac you will be backing up into it.

Dec 15, 2022 1:04 PM in response to pumpichank

From my experience with Time Machine, using apps, like Parallels, would cause TM to have to back up the entire VM machine any time you used Parallels. There are other examples of this.


TM uses a number of techniques to determine what files have changed, and these same techniques have changed since TM was first introduced.


To help determine what files are being backed up with each back up, I would rely on the following two apps:

  1. BackupLoupe
  2. Mints Ref: Time Machine 16: Reading a normal backup in Catalina using Mints - The Eclectic Light Company

Dec 4, 2022 7:13 AM in response to pumpichank

I don't have a solution for you, but, you can format the volume as APFS, and once you select that volume for the Time Machine backup it gets the (Case Sensitive) added automatically by the operating system.


As for the number of changes that Time Machine finds (my entire startup disk is less than 60 GB), and on my system Time Machine also finds 100's of thousands of changes, yet takes less than 4 to 5 minutes to complete.


Are you backing up to an SSD or rotational HD. I have found that starting with Big Sur and now Monterey, anything but an SSD causes issues.

Dec 12, 2022 9:15 AM in response to pumpichank

Just to be sure I understand. Is this MyBook drive configured with a single APFS Container with two APFS Volumes, or two separate APFS Containers, each having a single APFS Volume.


To help clarify the configuration, please post a screen shot of the results of this command in the Terminal:


  • diskutil list external


Also, FYI. Time Machine (TM) will back up to drives formatted in either HFS+ or APFS. The latter format was designed to work best with SSDs.

Dec 12, 2022 11:17 AM in response to Tesserax

Hi Tesserax, thanks for the follow up. Yes, this is an 8TB MyBook configured with a single APFS Container and (currently) three APFS Volumes. One is for a machine that will soon be decommissioned, so it'll go back to two volumes. Here's the output below.


Also, FYI. Time Machine (TM) will back up to drives formatted in either HFS+ or APFS. The latter format was designed to work best with SSDs.

Since the MyBook is a rotational drive, maybe it would be better to format it with HFS+ instead?


Here's the output requested. I renamed the machines to Remote1 and Remote2 to indicate the machines that are currently backing up over the network. Local is the machine that the MyBook is attached to, and the one that is super slow (both remote machines are actually pretty fast).


/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +8.0 TB     disk3
                                 Physical Store disk2s1
   1:                APFS Volume ⁨Remote1 Time Machine⁩     485.8 GB   disk3s2
   2:                APFS Volume ⁨Local Time Machine⁩     1.7 TB     disk3s3
   3:                APFS Volume ⁨Remote2 Time Machine⁩   290.6 GB   disk3s1

Dec 12, 2022 5:33 PM in response to pumpichank

The most significant bottleneck would be the connection type used between the source and destination for TM backups when it comes to using external drives. The next would be the internal connection type within the drive itself.


Although using encryption for backups will cause an overall performance penalty, it will not be significant.


FWIW, I too have a 2018 Mac mini (now running macOS Ventura.) I use three different backup destinations for TM:

  1. A Synology NAS over the network.
  2. A WD MyBook Pro directly connected via Thunderbolt. Since the MyBook Pro is a bit older, I have to use a TB2 to TB3 adapter.
  3. An OWC miniStack STX (my latest addition to TM backup devices) directly connected via TB3.


I do not encrypt my backups (personal choice) so I don't have any comparison data available, but I can tell you that the OWC is "night & day" different in data transfer rate performance over the other two methods. I have the OWC configured with a 2TB NVMe M.2 PCIe SSD & a 6TB SATA HDD. I use the later for TM; the former is being used as a "clone" to quickly regain access to my mini should its internal SSD drive fail.

Dec 4, 2022 12:28 PM in response to MargeHomer

Thanks MargeHomer. I'm backing up to a WD 8T MyBook, and the weird thing is that it used to work great. Yes, the first backup takes a long time, but after that, the incrementals go pretty quickly. The MBP laptop also backs up to a volume on the same drive over the network and that one works great. It's almost as if macOS loses any record of what it backed up before and always does a full backup.

Dec 10, 2022 1:04 PM in response to pumpichank

It's still much slower than I expect and it seems like it's backing up way more data than it should be. Like multiple gigs every run, even though I know files aren't changing that often. But it does seem to be completing as when I look in my Time Machine folder, I can see multiple days that are getting backed up. I sure which TM would produce a log so I could understand exactly what is getting backed up and maybe I'd be able to exclude some more folders.

Dec 12, 2022 8:55 AM in response to pumpichank

I tried to use `tmutil compare` to see what what actually being backed up. I see a few things that are suspicious, like /Volumes/.timemachine and a bunch of ~/Library/Application Support/com.apple.ap.promotedcontentd and ~/Library/Calendars/Calendar Sync Changes, and a few other things. Nothing all that big though. The thing is `tmutil compare` itself takes a very long time. It still hasn't completed. So back to at a loss for what's going on here. That said, `tmutil listbackups` is showing that backups are completing, so I dunno what to do next. I guess short of any other suggestions, I'll just live with it.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

All Time Machine backups take too long

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.