Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Time Machine error
- Thread starter Jamacfer
- Start date
- Sort by reaction score
It just depends on what software you're running and how you are using the computer. It also depends on how observant you are; you simply might not be noticing that overnight TM backups are failing. Have you queried the logs to confirm there have been no errors?
Add the FindMy widget to your desktop. Then ensure that TM backups do run overnight while your computer is locked. I think that's a reliable way to trigger it. As soon as you unlock your computer, look for the error in the Time Machine section of System Settings. If you let a new backup run before you check, you won't be aware that a backup during the night failed.
I normally run Time Machine backups manually so haven't run into the problems that are being described here but out of curiosity I decided to try your test. FindMy on the desktop, computer set to sleep and Time Machine backups to run every hour. As near as I can tell, Time Machine ran as expected with no errors displayed in System Settings. Running 15.6.1 on an M1 Studio Ultra.
I appreciate you running that test. When my computer is asleep, backups run less frequently than hourly. But, if you see evidence that the backup was made without error while the computer was asleep, then that's great information.
People who run manually will never have the issue. At the moment the TM backup starts, a disk snapshot is made. Certain files on that snapshot are inaccessible if the snapshot is made while the computer is locked.
My backups didn’t happen every hour overnight as well. Would there be some way for me to check if there were any problem files in the snapshots? There weren’t any errors in Time Machine System Settings.
Sorry I didn't respond sooner. Assuming the backups you care about ran in the past 8 hours, then in Terminal you can run.
Code:
log show --last 8h --predicate 'process=="backupd"' | grep "Failed to acquire"You could put any length of time. You'll probably get no output, which means you had no errors. Post #185 shows an example of output having the error.
Yeah it was fixed for me, but now has resurfaced with 15.6. It seems to only do it when the computer display is asleep (my computer is set to never sleep). I close out the notification (and do nothing else) and subsequent backups are completed without any error.
Thanks for taking the time to help me with this. I let Time Machine run on Auto overnight and ran your script in Terminal before another backup was made. I don't know what's different between your setup and mine but I didn't get any errors. Thanks again for your help.
I decided to remove my Time Machine exclusion just to test the waters. I haven't had any errors over the last few nights. In the past I would always have a problem with the bluetooth-related milod daemon. So, my reliable failure example is failing me. If the problem resurfaces, I'll reintroduce the exclusion.
I believe behavior is the driver for the problem - what software is run and how the computer is used. I haven't intentionally done anything different for the last few nights, but it was mostly over the weekend and I wasn't working with my computer during the day as much. Now that a new work week has started, it will be interesting if the problem comes back.
I believe behavior is the driver for the problem - what software is run and how the computer is used. I haven't intentionally done anything different for the last few nights, but it was mostly over the weekend and I wasn't working with my computer during the day as much. Now that a new work week has started, it will be interesting if the problem comes back.