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.
Resolved Time machine experiencing multiple issues on Monterey (my personal issue resolved)
- Thread starter MacinMan
- Start date
- Sort by reaction score
@MacinMan,
thank you and all others on this thread for discussing these issues with TM on Monterey (12.0.1, now 12.1).I experienced most of what was mentioned here!
I have a brandnew iMac 24" 2021 (M1) with 1TB SSD internal and G-RAID 6TB and G-DRIVE 14TB external HD.
now I have a working timemachine backup again, after done these steps:
1) in recovery mode, disk utility checked all filesystems on all disk, volumes, containers and medias: no errors.
2) in Terminal found all "...findmy..." files, put them into a file to make a zsh shellscript:
tmutil addexclusion -p /Users/xxx/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems
tmutil addexclusion -p /Users/xxx/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople
tmutil addexclusion -p /Users/xxx/Library/Containers/com.apple.findmy.FindMyWidgetItems
tmutil addexclusion -p /Users/xxx/Library/Containers/com.apple.findmy.FindMyWidgetPeople
3) ran this file with zsh TMfindmyExcl.txt
4) and now TM works as expected!!!
great, have got back confidence in my TM, but still waiting that apple fixes theses TM issues...
kind regards, Gérard.
So far, I haven't heard anything major from anyone who tested and reviewed the first beta. In fact, so far it doesn't seem to contain anything major. So maybe in later betas something will show up.
Oddly, I've had zero problems with Time Machine on my 14 inch 2021 MacBook Pro, with either Monterey 12.0 or 12.1. Super Duper on the other hand, no bueno. Same issue with failure to "Bless the Drive". Dave at Shirt Pocket suggested I not do an OS backup, but instead perform a Smart Update and select copy all files.
I'm wondering if the new Macs are coming defective from the factory? the 2021 models would be a possibility, but that doesn't explain the problems with the 2020 M1 Macs. The only other possibility is a firmware bug because people are being affected differently. I would think if it was one specific problem, more people would be consistent in what they are reporting. However what I've seen just by watching this thread is people are having similar problems, but others aren't, and then then there are those all over the map with experiences.
I've been cleaning up my iMac over the past few days and getting rid of stuff I don't use anymore, and I've increased my speed and storage quite a bit. It was never slow, but startup speed has improved, as well as user login speed.
Is Time machine able to backup to multiple drives at the same time, or is it limited to one disk at a time ?
Ok so I reinstalled Monterey (with format) on my M1 Mac Mini, and now TimeMachine seems to work fine.
Glad to hear you have resolved your issues. I'm still seeing an issue with CCC where after some time of the system running, e.g. a couple weeks straight that snapshots are reported to be taking up large amounts of space on the system drive. I can usually just delete the snapshots, and reboot and it's fine. Time Machine is working as it should.
I noticed there is a toggle switch in the snapshots window for CCC, will turning this off disable snapshots in CCC?
I'm not exactly sure why it's using them anyway, since I don't currently use it as my active backup solution.
I just check status from time to time in the dashboard.
I've had this issue since updating to Monterey, with all three of my Time Machine targets.
Today I used "log show --style syslog --last 30m --predicate 'senderImagePath contains[cd] "TimeMachine"' --info --debug" to see which files it had issues with and saw that they were all large files in iCloud Documents.
I told Time Machine to exclude the iCloud Documents folder and now have successful backups (initial and a few incremental so far) to all three target disks.
I realise it might not be so simple a fix (more like workaround) for everyone of course, but thought it worth mentioning just in case it helps anyone.
Today I used "log show --style syslog --last 30m --predicate 'senderImagePath contains[cd] "TimeMachine"' --info --debug" to see which files it had issues with and saw that they were all large files in iCloud Documents.
I told Time Machine to exclude the iCloud Documents folder and now have successful backups (initial and a few incremental so far) to all three target disks.
I realise it might not be so simple a fix (more like workaround) for everyone of course, but thought it worth mentioning just in case it helps anyone.
This might not help anyone but this what I have found.
System. 2017 Imac, 64gig ram, 1tb ssd; fully updated Monterey.
TN 2tb ssd; formated APFS; encrypted; attached using a usb3.1 Akitio dual enclosure.
Results: TM was a total mess; it never got out of preparing the backup or when it did it never finished.
Same drives installed in Thunderbolt 3, Akitio QuadX 4 bay enclosures. Zero problems; backups completed quickly. Not one issue. Backups completed on time; able to restore without issues.
Same SSD's decrypted; in the USB 3.1 enclosure still have every issue described above.
Moved the drives into my QuadX enclosures. Zero issues with TM.
I moved two 12tb HGST Drives into the USB 3.1 enclosure; not one issue; they backup and perform with out issue.
It has been over a month since make the changes. All is well.
I have over 96tbs of in two Quadx 4 bay enclosure; and the USB 3.1 enclosure.
Not saying this is a solution; just saying this works well for me.
System. 2017 Imac, 64gig ram, 1tb ssd; fully updated Monterey.
TN 2tb ssd; formated APFS; encrypted; attached using a usb3.1 Akitio dual enclosure.
Results: TM was a total mess; it never got out of preparing the backup or when it did it never finished.
Same drives installed in Thunderbolt 3, Akitio QuadX 4 bay enclosures. Zero problems; backups completed quickly. Not one issue. Backups completed on time; able to restore without issues.
Same SSD's decrypted; in the USB 3.1 enclosure still have every issue described above.
Moved the drives into my QuadX enclosures. Zero issues with TM.
I moved two 12tb HGST Drives into the USB 3.1 enclosure; not one issue; they backup and perform with out issue.
It has been over a month since make the changes. All is well.
I have over 96tbs of in two Quadx 4 bay enclosure; and the USB 3.1 enclosure.
Not saying this is a solution; just saying this works well for me.
Hey everyone, it's been some time since I've seen activity here. So: was just wondering if people finally were able to resolve their issues, or if everyone is just waiting for New year's to be over so Apple is back to work.
Everything working here, in fact, after cleaning up my system and removing stuff I don't need, or use, everything (including bootup is considerable faster.) Question: and this is somewhat off topic, but it's still Mac related. I've run into situations lately where I've needed to do some tasks in windows, and a VM didn't cut it. So I had to boot camp on my MBP to do it. Since it's older, and mainly a test box now. I used that. What happened was, I discovered on Christmas day that LG finally had released a firmware update for the Blu-ray writer I have from them. The flasher is windows only with no way to pull the firmware out and flash it in a command line like Pioneer offers. Anyway, I directly connected the drive to a windows VM with fusion, as a USB device vs just using the shared drive function. The flasher recognized the drive, but never started the update. Moved it to the MBP with bootcamp and it flashed instantly and now it's back on the iMac and works fine with the latest firmware. MakeMKV shows the drive's firmware in the console, so with the flasher saying it was successful, and then seeing the updated firmware on the Mac, I know it worked.
Question, does Bootcamp still work in Monterey on Intel Macs? I know I've heard that with Fusion drives, windows gets put onto the mechanical drive. So, is there a way to fix this so it works in a VM, or should I just boot camp the iMac.
Was simply curious to see what thoughts you all had.
Thanks
Everything working here, in fact, after cleaning up my system and removing stuff I don't need, or use, everything (including bootup is considerable faster.) Question: and this is somewhat off topic, but it's still Mac related. I've run into situations lately where I've needed to do some tasks in windows, and a VM didn't cut it. So I had to boot camp on my MBP to do it. Since it's older, and mainly a test box now. I used that. What happened was, I discovered on Christmas day that LG finally had released a firmware update for the Blu-ray writer I have from them. The flasher is windows only with no way to pull the firmware out and flash it in a command line like Pioneer offers. Anyway, I directly connected the drive to a windows VM with fusion, as a USB device vs just using the shared drive function. The flasher recognized the drive, but never started the update. Moved it to the MBP with bootcamp and it flashed instantly and now it's back on the iMac and works fine with the latest firmware. MakeMKV shows the drive's firmware in the console, so with the flasher saying it was successful, and then seeing the updated firmware on the Mac, I know it worked.
Question, does Bootcamp still work in Monterey on Intel Macs? I know I've heard that with Fusion drives, windows gets put onto the mechanical drive. So, is there a way to fix this so it works in a VM, or should I just boot camp the iMac.
Was simply curious to see what thoughts you all had.
Thanks
Waiting on Apple, the only way I can get it to consistently work is to exclude the entire ~/Library folder.
Until Apple fixes this, I stopped using Time Machine. It is the only issue I have in my MX1, I used to have Parallels on the replaced Intel 2019 MAC running Windows 10 on a VM. Gave that up too, though it is possible to use on an M1.
I've tried all the suggestions I could locate in this thread and Time Machine still will not complete.
I excluded all the Find My locations, that didn't work. Next I ran First Aid on all disk objects, that didn't work. Next I turned Time Machine off completely, manually deleted all local Time Machine snapshots and tried to start over, still no dice.
I excluded all the Find My locations, that didn't work. Next I ran First Aid on all disk objects, that didn't work. Next I turned Time Machine off completely, manually deleted all local Time Machine snapshots and tried to start over, still no dice.
The one that worked for me was not excluding Find My. I excluded /Library/Metadata on December 6 and Time Machine has worked perfectly for me since then.
I read 23 pages with the problem from 27 October. Today 31 December problem still not solved. And thats how Apple respect their customers? Thats how "it just works"? I support Apple from 2007. I have the most of their products, i am almost a fanboy and i fight and tease my friends with their "outdated" laptops. The funny thing? Windows users watch posts like those here and they laugh so hard. Shame on you Apple. Some of us live from your products professionally, and now we can't make a simple ***** backup!!!!!
Last edited:
I have been getting the “Waiting for first backup to complete” message all the time, with no record of prior backups, yet the backups are there. I have been running TM backups for about 3 days. So on a whim I just went in and excluded the 4 folders /Users/.../Library/Containers/FindMyWidgetIntentsItems, /Users/.../Library/Containers/FindMyWidgetIntentsPeople, /Users/.../Library/Containers/FindMyWidgetItems, and /Users/.../Library/Containers/FindMyWidgetPeople. The first hourly backup after these folders were excluded just completed. I got a notification that the first backup on the disk had been completed, and everything looks correct in the status (plus I can restore from the TM backup) - see below.I know @matthewnp had success for a few days with this before it failed again, so we'll see if it continues to work. But some small workaround progress!
Been reading through all of these suggestions with no luck so far. Got my new MackBook Pro M1Pro back in November and have not had a successful backup yet. Initially, I was using my previous backup disk (which shouldn't be an issue), and was running into the error `Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked.`
Tried a few things, talked with Apple Support, no resolution. Ended up getting a new external hard drive since I was going to need a larger one soon anyway. Thought I backed up successfully as I didn't receive any error messaged, but there is no history of a backup. Works perfectly on my wife's M1 Air. Tried Safe Mode, Tried removing the volume for my computer on the external HD and re-adding to TM. Tried First Aid on the disks. No luck. Reached out to Apple Support on chat and they immediately escalated it to senior phone support after I mentioned all of there attempts had been done before they could suggest them. The guy on the phone suggested reinstalling Mac OS, which was the one thing I hadn't tried. Still no luck. This is insane, how can this not be solved through Apple if it's been going on for months, especially with a service that's been around for so long.
Tried a few things, talked with Apple Support, no resolution. Ended up getting a new external hard drive since I was going to need a larger one soon anyway. Thought I backed up successfully as I didn't receive any error messaged, but there is no history of a backup. Works perfectly on my wife's M1 Air. Tried Safe Mode, Tried removing the volume for my computer on the external HD and re-adding to TM. Tried First Aid on the disks. No luck. Reached out to Apple Support on chat and they immediately escalated it to senior phone support after I mentioned all of there attempts had been done before they could suggest them. The guy on the phone suggested reinstalling Mac OS, which was the one thing I hadn't tried. Still no luck. This is insane, how can this not be solved through Apple if it's been going on for months, especially with a service that's been around for so long.