I don’t understand how CCC can be a replacement for a backup. Isn’t it just cloning the drive?
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
I don’t understand how CCC can be a replacement for a backup. Isn’t it just cloning the drive?
Yes it clones the drive; and all the changes I make. It works for me exactly the way I need it too; I love TM; but right now it is a mess for me. Example: I use two tb crucial ssd's for my TM; For me when I setup a TM drive; TM will not allow any other files on that drives. Example if I files on that drive when I select it to use as TM drive it erases that drive. Once the drive is set up for TM I cannot store any other files on that drive. TM locks that drive. Have been using CCC works for me and my situation. Other situations are different; but TM is a mess for me right now. I have TM ever since it was introduced; this is the first time it has not worked.
I hope you are right. If you ruin a file for whatever reason, you won’t be able to go back in time and restore the good version of it if you don’t notice the problem immediately.
Just reporting my own mistakes here…
I'll chime in as well - Apple recommended I install 21D5039d to collect logs (apparently this build has new logging to capture these issues), and it seems to be fixed now.
Now getting hourly backups complete without issue with no exclusions in the ~/Library folder.
Now getting hourly backups complete without issue with no exclusions in the ~/Library folder.
I agree with 100%, I hope this works too. For me; this works. This might not work for other people. I would love to see TM work the way it is supposed; but for me it doesn't come close. It worked great is every OSX up thur Big Sur. But for me Monterey has not. My setup might not work for others.
I've had to restores files three or four times since I'm on Monterey, and I can report that it worked in all cases.
I see. Since i might need to do a full reinstall and I'm gonna restore from time machine.
My machine is defective sadly so yeah. Gonna need to restore it if I send my machine away .
My encouragement to people here has mainly been to not rely one specific solution for backups. Even before the Monterey problems, I would have still say 90 to 95% reliability for Time Machine as a whole. So it's just good practice to have other solutions handy, even if not actively used on a regular basis. Just having them available when needed is what matters.
Well, after excluding my ~/Library/Metadata directory from Timecapsule backups, everything worked fine for a couple of days, up through yesterday actually. Today its failing again on the Metadata directory, so apparently removing it and having Monterey recreate it is not any kind of permanent fix. The log showed:
error 17:07:44.499695-0500 backupd Failed to proactively acquire device lock assertion on lock state change (0). error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
error 17:07:44.538435-0500 backupd [ERROR] Couldn't get account descriptors from daemon - Error Domain=NSCocoaErrorDomain Code=4099 UserInfo={NSDebugDescription=<private>}
error 17:07:57.909384-0500 backupd Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Curtis’s M1 iMac/2022-01-17-170736/Data/Users/crubel/Library/Metadata error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
error 17:07:58.808415-0500 backupd Failed postflight for destination <APFSDestination /Volumes/SuperDuperDisk TimeMachineBackups>
error 17:07:58.963882-0500 APFSUserAgent Cannot remove volume for disk=0x140105cd0 desc=0x140009390 bsd_name=(null) vctx=0x0
I excluded that same Metadata dir from Timecapsule Options again and the backups completed OK. So at least in my case there is a definite issue with the Metadata directory like it was in use or some sort of security permissions or something else new for Monterey I am not aware of yet. Either way this is an Apple issue and they will need to fix it or remove Timecapsule from the operating system apps since it is definitely not reliable to use it and your backup app needs to be extremely reliable...
error 17:07:44.499695-0500 backupd Failed to proactively acquire device lock assertion on lock state change (0). error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
error 17:07:44.538435-0500 backupd [ERROR] Couldn't get account descriptors from daemon - Error Domain=NSCocoaErrorDomain Code=4099 UserInfo={NSDebugDescription=<private>}
error 17:07:57.909384-0500 backupd Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Curtis’s M1 iMac/2022-01-17-170736/Data/Users/crubel/Library/Metadata error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
error 17:07:58.808415-0500 backupd Failed postflight for destination <APFSDestination /Volumes/SuperDuperDisk TimeMachineBackups>
error 17:07:58.963882-0500 APFSUserAgent Cannot remove volume for disk=0x140105cd0 desc=0x140009390 bsd_name=(null) vctx=0x0
I excluded that same Metadata dir from Timecapsule Options again and the backups completed OK. So at least in my case there is a definite issue with the Metadata directory like it was in use or some sort of security permissions or something else new for Monterey I am not aware of yet. Either way this is an Apple issue and they will need to fix it or remove Timecapsule from the operating system apps since it is definitely not reliable to use it and your backup app needs to be extremely reliable...
I got the same response from Apple, however I didn't want to install the beta. Thanks for confirming that it does fix it. This is good news!
The command is a workaround, it excludes all failing files from backup:
Not having those folders in backup is totally fine: you can safely remove them and once you use the Find My Widgets, they will be automatically regenerated.
Did anyone tried macOS 12.2 RC?
Bash:
sudo tmutil addexclusion -p ~/Library/Containers/com.apple.findmy.FindMyWidget*Not having those folders in backup is totally fine: you can safely remove them and once you use the Find My Widgets, they will be automatically regenerated.
Did anyone tried macOS 12.2 RC?
Last edited:
Yep, installed here and it is still working correctly after the last beta release. Looks like 12.2 officially fixes this!
Hopefully after 12.2 comes out, and we see after a month or so that things are working. I think it's finally time for me to set this thread to resolved. In the event people still have issues, someone could start an M1 specific thread for time machine issues as that's what it's primarily affecting.
Whoever said 4GB of data can take days to transfer between computers.... this isn't the 80s dude. xD
I can transfer 4GB of data over wireless in a short manner of time. A direct connection should be even faster.
Anyways, I use time machine for my DJ laptop backups and I too am having issues after switching to a new laptop on Monterey. I've now wiped my drive (I'm sweating bullets of paranoia because if my DJ laptop suddenly dies right now... that is SO much work down the drain), formatted in APFS (Not Case-sensitive), and hoping this works.... this really sucks.
I can transfer 4GB of data over wireless in a short manner of time. A direct connection should be even faster.
Anyways, I use time machine for my DJ laptop backups and I too am having issues after switching to a new laptop on Monterey. I've now wiped my drive (I'm sweating bullets of paranoia because if my DJ laptop suddenly dies right now... that is SO much work down the drain), formatted in APFS (Not Case-sensitive), and hoping this works.... this really sucks.
I initially said that as the initial upgrade last year caused issues. However, for me it's sorted and things are normal now. Most of the ones here still having issues are Apple Silicon owners. That's why I made the suggestion above that if people still have issues after about a month with 12.2, it might help to start a separate Time machine thread for Apple Silicon users specifically. This has clearly become two separate issues since I started the thread.
That's not true. If you make sure to leave Carbon Copy Cloner's "safety net" feature enabled, it will also save copies of older versions of changed or deleted files. It keeps doing this until you run out of space on the backup drive, at which point it will delete the oldest files first. It's nowhere near as intuitive to restore the individual files as Time Machine -- you have to dig through the backup directory to find the files -- but they're there.
There is such a thread: https://www.macrumors.com/2021/12/08/time-machine-initial-backup-error/
Good to know, I didn't realize this existed since I don't own an Apple Silicon Mac, so I have no reason to look for such threads currently. Anyway, I'm glad this exists for the specific issues.
I wanted to also add to the above post: I'm really grateful my thread was able to help people come together and express the problems that came up from them in addition to my own. Now apple has done something about it according to those running 12.2 RC, and with the thread I just looked at created by Macrumors now people have multiple resources so they don't have to depend on just one source.
If that’s possible, then it’s something else than just cloning the drive (which I was originally responding to). But good thing CCC can do that as well.
It's doing both here: providing an exact dupe of the source drive and also preserving modified/deleted files by adding a single folder at the root level.
Last edited:
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.