iMac M4 (2024), MacBook Pro M3 (2023) both under MacOS 15.2
I’m getting notifications that “TimeMachine couldn’t complete the backup ‘Time Machine’; Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked” on both ARM machines both running MacOS 15.2. The message occurs after waking from sleep. But AFAICT it doesn’t resume when the Mac is unlocked; I have to manually restart the backup.
In addition, the iMac refuses to run Folding@Home (for TidBITS!) when “idle” (asleep); my previous iMac 27 (2019 Intel) and MacBook Pro (2019 Intel), both also with 15.2, never had either problem.
I’m wondering if there’s a connection…does it have something to do with ARM vs. Intel? Or is there some system setting to allow/prohibit a process from running in the background? Neither Time Machine nor F@H is available on the list of items allowable in background, and “Log out when idle” has never been set on either machine.
You know, I’d forgotten about it, but I saw those same messages (or very similar) after updating to 15.1 or 15.2 (or possibly even both). I never interpreted the “will resume” part of the message to mean there was a backup that was pending, so I never did any manual intervention. And, as is often the case, those messages just stopped appearing after maybe a week or two, and haven’t come back. I’m on a MBP M1 Pro, TM set to run every hour.
It’s been about two weeks since I set up the iMac, so maybe there’s hope, but the MBP didn’t show that dialog in August when I got it. I was out of town for September through early December, and when I set up Time Machine again to the same disk, the dialogs started. Mystery!
Interesting. The messages also appear on mu MBP Pro M1. They have never stopped, and I have to manually intervene to make TM back up… Surely someone else is having this problem too…?
I seem to remember that I only saw the message when my Mac woke from sleep in the morning. I don’t recall seeing it on wakeup during the day. And it was not consistent: some mornings there was no message. But even when the message appeared, TM resumed operating after I dismissed the message (perhaps not immediately, but at least with the next hour’s backup). So our situations are a bit different after all. I wish I had more to say other than “it fixed itself.” I hope someone else can provide something more helpful!