Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Resolved Time machine experiencing multiple issues on Monterey (my personal issue resolved)

From the first 12.0.1 and 12.1 right now on my MBP 2021 ARM . I always got the TM issue where it backed up and then it doesn't really complete the backup.

What I did to fix it permanently is to first do a backup to the disk. While the screen is awake. Until it's done. Don't skip the cleaning up process. Let it run. If you don't want to worry it having the screen off just use Amphetamine. When it's done it should be fine. You'll see the last backup date and confirm that it works. After that it should be able to backup every time even with screen off .

And I've been able to reproduce on how to make it problematic again.
If you,
1. Install a new MacOS Update
2. Use Onyx with the Maintenance tab which cleans things.
It'll happen again and to fix it you can do the usual again.

This has been consistent for me and I didn't even need to add any exclusion etc to the TM . Although I don't know if 12.2 fixes it. We'll see
 
  • Like
Reactions: Brian33 and ignatius345
MacinMan said:
I haven't tried to do a CCC clone on Big Sur, or Monterey, but I used it on an external drive which had Mojave, to put it back on my older MBP without waiting for the installer and having to configure it from scratch. That worked perfectly and the MBP boots fine. How is the success of bootable clones with Big Sur, or Monterey at this time? I know there have been problems, and they've been fixed, but since I've never tried it for myself was just curious on how reliable it is.
Click to expand...
I believe things are ironed out with regard to that. But I have to admit I haven't really tried booting off a clone in since Big Sur and M1 Macs happened.
 
white7561 said:
From the first 12.0.1 and 12.1 right now on my MBP 2021 ARM . I always got the TM issue where it backed up and then it doesn't really complete the backup.

What I did to fix it permanently is to first do a backup to the disk. While the screen is awake. Until it's done. Don't skip the cleaning up process. Let it run. If you don't want to worry it having the screen off just use Amphetamine. When it's done it should be fine. You'll see the last backup date and confirm that it works. After that it should be able to backup every time even with screen off .

And I've been able to reproduce on how to make it problematic again.
If you,
1. Install a new MacOS Update
2. Use Onyx with the Maintenance tab which cleans things.
It'll happen again and to fix it you can do the usual again.

This has been consistent for me and I didn't even need to add any exclusion etc to the TM . Although I don't know if 12.2 fixes it. We'll see
Click to expand...
There are a few posts here by people saying that there issues have been fixed with 12.2, and they have tried under the RC, and have said the problems they were having are resolved. I haven't seen anyone post to suggest otherwise yet.

As far as the screen off issue do M1 based macs have the option like intel based macs to simply sleep the screen, but not the whole system? That might be the problem there. The other problem might have to deal with the screen lock feature some how. Try disabling that if want to try it. With 12.2 coming out any moment though, it might be more worth it to just wait, install the update and see if the issues are gone, and then move on from there.
 
MacinMan said:
There are a few posts here by people saying that there issues have been fixed with 12.2, and they have tried under the RC, and have said the problems they were having are resolved. I haven't seen anyone post to suggest otherwise yet.

As far as the screen off issue do M1 based macs have the option like intel based macs to simply sleep the screen, but not the whole system? That might be the problem there. The other problem might have to deal with the screen lock feature some how. Try disabling that if want to try it. With 12.2 coming out any moment though, it might be more worth it to just wait, install the update and see if the issues are gone, and then move on from there.
Click to expand...
That's the thing. At first it didn't make any sense to me. Since i always backup when connected to power. And I disabled the sleep when screen off when on power. So when the screen is off. It's not sleeping at all.

So the other thing I'm thinking is the lock screen. Since the only difference between it having the display off and on for me is that if it's off it's locked.
 
white7561 said:
That's the thing. At first it didn't make any sense to me. Since i always backup when connected to power. And I disabled the sleep when screen off when on power. So when the screen is off. It's not sleeping at all.

So the other thing I'm thinking is the lock screen. Since the only difference between it having the display off and on for me is that if it's off it's locked.
Click to expand...
That's how I use my iMac, screen sleep, but no system sleep, and screen lock is on. If you go back to my original post of the thread you will see my issue was mainly speed of completion. It eventually resolved itself, and I've been using Time Machine as I had been in Big Sur with all my same settings. So as I've said a few other times, these issues are most likely Apple Silicon specific, since for the most part Intel users haven't been reporting issues here. I also know that Intel Macs with a T2, and Apple Silicon macs also have tighter hardware security than Intel Macs pre T2. So also might be a factor there. The issues have always been permissions related it seems for Silicon users. So we'll see what happens when 12.2 comes out to the public.
 
MacinMan said:
That's how I use my iMac, screen sleep, but no system sleep, and screen lock is on. If you go back to my original post of the thread you will see my issue was mainly speed of completion. It eventually resolved itself, and I've been using Time Machine as I had been in Big Sur with all my same settings. So as I've said a few other times, these issues are most likely Apple Silicon specific, since for the most part Intel users haven't been reporting issues here. I also know that Intel Macs with a T2, and Apple Silicon macs also have tighter hardware security than Intel Macs pre T2. So also might be a factor there. The issues have always been permissions related it seems for Silicon users. So we'll see what happens when 12.2 comes out to the public.
Click to expand...
Yep we'll see I guess. But yeah for me. My way always works . No need to exclude anything
 
white7561 said:
Yep we'll see I guess. But yeah for me. My way always works . No need to exclude anything
Click to expand...
Just FYI: even though this is slightly off topic, I quit letting my Mac sleep because I use Plex Media Server, and other streaming platforms and it would always cause issues when the mac went to sleep. Turning off the screen saves the most power anyway. Granted, I don't have a battery to worry about other than the UPS.
 
MacinMan said:
Just FYI: even though this is slightly off topic, I quit letting my Mac sleep because I use Plex Media Server, and other streaming platforms and it would always cause issues when the mac went to sleep. Turning off the screen saves the most power anyway. Granted, I don't have a battery to worry about other than the UPS.
Click to expand...
Yep true. I don't sleep when the screen is off if I'm charging it since well there isn't any reason to do it. I'd rather have it awake so every apps can update and receive notifications since I'm charging anyways. MBP 16" M1 uses like 2w 3w max without display. (Depends on peripheral and CPU usage etc)
 
Just giving a quick update, I have updated to 12.2 on my 27" late 2015, iMac and the initial Time Machine backup after the update completed in about 15 Minutes at most 10 at least. This is a good sign as my initial issue was speed. Considering it completed so quickly shows that it's working correctly. I am hoping those who have been ongoing issues will finally be able to come to resolution now after the update, without anymore trouble.
 
The macOS 12.2 is out.

Although I still see the "device assertion error", the backup works. and even after I removed exclusions (FindMy Widgets) I added, it still be able to complete the backup. They managed to fix the issue.
 
  • Like
Reactions: ozarkcanoer
Extrawdw said:
The macOS 12.2 is out.

Although I still see the "device assertion error", the backup works. and even after I removed exclusions (FindMy Widgets) I added, it still be able to complete the backup. They managed to fix the issue.
Click to expand...
Did you try starting a fresh backup on a clean drive? just in case there is something left from the old backup(s) that might be causing the error to show up, and to also make sure it's going to work from ground up?
 
Extrawdw said:
The macOS 12.2 is out.

Although I still see the "device assertion error", the backup works. and even after I removed exclusions (FindMy Widgets) I added, it still be able to complete the backup. They managed to fix the issue.
Click to expand...
Only completed 1 time machine backup since installing 12.2 - but it worked normally. Running a second one now (I use 2 Backup Drives), Both were newly formatted with encryption. This MBP M1 MAX came with Monterey from factory and has NEVER before today completed a Time Machine backup (and I tried most of the work arounds). So far promising, let's wait a few days....
 
  • Like
Reactions: ozarkcanoer, MacinMan, Brian33 and 1 other person
likegadgets said:
Only completed 1 time machine backup since installing 12.2 - but it worked normally. Running a second one now (I use 2 Backup Drives), Both were newly formatted with encryption. This MBP M1 MAX came with Monterey from factory and has NEVER before today completed a Time Machine backup (and I tried most of the work arounds). So far promising, let's wait a few days....
Click to expand...
That does sound promising, you've been one who hasn't been able to get it to work at all, even with the suggested workarounds. The fact you got it to complete normally sounds like really good news.
 
I think I misunderstood as well, I thought we were talking exceptions here, and that's why i said it would be better to remove them in order to confirm the problem was fixed.
 
MacinMan said:
I think I misunderstood as well, I thought we were talking exceptions here, and that's why i said it would be better to remove them in order to confirm the problem was fixed.
Click to expand...
yes that’s my question. How i remove that command ?
tmutil addexclusion ~/Library/Containers/com.apple.findmy*
 
Pskordilis said:
yes that’s my question. How i remove that command ?
tmutil addexclusion ~/Library/Containers/com.apple.findmy*
Click to expand...
You should be able to simply remove the exceptions from the Time Machine Preferences. Open system Preferences Click on Time Machine Click options. Select the excluded items in the list and click - to remove them. Then that should be all you need to do.
 
  • Like
Reactions: ozarkcanoer
MacinMan said:
You should be able to simply remove the exceptions from the Time Machine Preferences. Open system Preferences Click on Time Machine Click options. Select the excluded items in the list and click - to remove them. Then that should be all you need to do.
Click to expand...
That’s the problem. Even if i enter that command and resolve my problem, i don’t see any exclude items in the options section.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back