Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've opened a case with Apple. They are asking me to have only a single backup disk configured; currently I have three. Does anyone have the issue with only a single attached backup disk?
 
They've escalated my support issue. I'll be getting a callback soon.

As an aside, if I just exclude ~/Library from Time Machine backups, the problem goes away. I did exclude the Biome subfolder once and that wasn't good enough. For me, it turned out there was one other spot under Library that caused an issue.
 
  • Like
Reactions: kkclstuff
Well, I got to tier 2, but then I had phone issues (a common occurrence at my house). The person called me back once, but didn't the second time; I don't blame her. I'll pick it up again soon.
 
I've decided not pursue this further with support. The issue is getting enough airplay on a number of fronts. I'm glad I got my issue into Apple's tracking system and somewhat escalated, but I don't think it's worth my time to take it further.

It's easy to check the logs retroactively to figure out which files were locked when the backups failed. I use


For me, the files were in two places: ~/Library/Biome and ~/Library/Daemon Containers. I just excluded them from my backups and haven't had a problem since. I suppose if I left multiple users logged in, I'd have to do exclusions in more than one Library folder.

The exclusions cannot be made using the System Settings user interface; these particular directories cannot be selected. I set up the exclusions at the command line using the "tmutil" command. The man page is pretty clear on how to do it.

sudo tmutil addexclusion -p <some directory>
 
Thanks for the workaround

unfortunately its like 'wack a mole' with this small errors. Along with the "TM error", there is now a "wallpaper error" (Just popped up for me since 15.2). PS edit: I just found a workaround/solution for my Wallpaper error, posted here

I hate the saying, "just live with it" but it seems like (for all of us) time is too precious to hunt down these errors and workarounds for Apple. Feeling like Apple's priority for a polished premium product has slipped considerably.
 
Last edited:
  • Like
Reactions: !!!
I've decided not pursue this further with support. The issue is getting enough airplay on a number of fronts. I'm glad I got my issue into Apple's tracking system and somewhat escalated, but I don't think it's worth my time to take it further.

It's easy to check the logs retroactively to figure out which files were locked when the backups failed. I use


For me, the files were in two places: ~/Library/Biome and ~/Library/Daemon Containers. I just excluded them from my backups and haven't had a problem since. I suppose if I left multiple users logged in, I'd have to do exclusions in more than one Library folder.

The exclusions cannot be made using the System Settings user interface; these particular directories cannot be selected. I set up the exclusions at the command line using the "tmutil" command. The man page is pretty clear on how to do it.

sudo tmutil addexclusion -p <some directory>

Well, had another failure overnight. Another locked file reared its head in the directory

~/Library/Containers/com.apple.findmy.FindMyWidgetItems/

I think I'll add an exclusion of ~/Library/Containers.
 
interesting... I noticed today that when I put the Mac to sleep, theres no error notification on wake. But when the Mac falls asleep on its own, the error is present on wake.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.