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)

I'm joining the conversation again... Bought myself a new 2TB Samsung SSD. And on trying the initial backup the FindMy fix workaround didn't work. Even though it has worked for me twice before. I haven't tried the other exclusions mentioned previous, I can't be bothered in all honesty.

For now I am sticking with CCC. It seems to work flawlessly every time and it means I am getting my money's worth out of it.
 
Last edited:
randomgeeza said:
I'm joining the conversation again... Bought myself a new 2TB Samsung SSD. And on trying the initial backup the FindMy fix workaround didn't work. Even though it has worked for me twice before. I haven't tried the other exclusions mentioned above, I can't be bothered in all honesty.

For now I am sticking with CCC. It seems to work flawlessly every time and it means I am getting my money's worth out of it.
Click to expand...
Check the Console for relevant errors. Filter on "backup" and look for warnings/errors. It's very likely to be other files and folders causing similar issues. If you get the 104 error at the very end of the backup attempt, it's almost certainly that and the files/folders to exclude will be right there in the logs.
 
PixelSushiRobot said:
  • ~/Library/Shortcuts
Click to expand...
Haven't had problems with this one yet, but I'll keep an eye on it, thanks!

I've also noticed that Monterey sometimes seems not to release the Time Machine volume properly. Symptoms are that Time Machine keeps "Preparing backup" for an unusual long time, then cancels the backup. The log shows something like Backup failed (18: BACKUP_FAILED_TARGETVOL_NOT_FOUND - The backup disk could not be found.)

It looks like Time Machine fails to unmount the volume, then later tries notices that and tries to unmount it, but can't do it for some reason. However, after a reboot of the Mac, the problem is gone. This looks like another Time machine related bug in Monterey.
 
My backups to my NAS are failing. In my logs, I'm often getting:

2022-01-10 05:05:44.971639+0000 localhost backupd[471]: (TimeMachine) [com.apple.TimeMachine:General] Failed to eject disk4s2 using DiskManagement, error: {
Action = Eject;
Dissenter = 1;
DissenterPID = 0;
DissenterStatus = 49168;
Error = "-69691";
Target = disk4;
}

2022-01-10 10:14:46.618706+0000 localhost backupd[462]: (TimeMachine) [com.apple.TimeMachine:General] Backup failed (21: BACKUP_FAILED_DISK_IMAGE_NOT_MOUNTED)
 
rafisaar said:
When the problem does occur, before you get it resolved, there will be a huge backup file with inProgress in its name. This is a partial backup and you can actually do a "Show Package Contents" on it and start browsing inside your backed up files (at least I can with HFS+, maybe this is now restricted with the Read-Only APFS???)
When TM fires back up, it will pick up this inProgress file and use it to continue to back up what else needs to be backed up. In my multiple trials before I got it resolved, I often deleted this file to start from scratch. But I then realized that wasn't necessary and leaving that file in place actually made the next attempt run faster, until I finally got it resolved.
I did turn off automatic backups until I got this resolved and ran test backups manually.
Click to expand...

How can I access this inProgress file?
 
dhokes said:
2022-01-10 10:14:46.618706+0000 localhost backupd[462]: (TimeMachine) [com.apple.TimeMachine:General] Backup failed (21: BACKUP_FAILED_DISK_IMAGE_NOT_MOUNTED)
Click to expand...
Might have the same cause as #603

Does it work after a reboot? Also try rebooting the NAS in case it's holding open file handles.
 
  • Like
Reactions: dhokes
Searching the net a bit for
Code: 
2022-01-10 12:36:07.068945+0000  localhost backupd[482]: (TimeMachine) [com.apple.TimeMachine:General] Failed to mount 'disk5s1', dissenter {
    DAStatus = 49218;
}, status: (null)
it looks like that's yet another TM bug in Monterey. :-(
 
I've got an 8TB external hard drive formated in Mac OS Extended (Journaled) however I can't set up Time Machine with this unless I delete all the data off it first?! :/
 
dhokes said:
I've got an 8TB external hard drive formated in Mac OS Extended (Journaled) however I can't set up Time Machine with this unless I delete all the data off it first?! :/
Click to expand...
This happens with any drive that is setup for TM. TM will no long let you store date on the drive except TM. I am an avid user of CCC; I removed my two time machine drives and have setup 4 SSD's as CCC backups. They are set to run CCC at 4 different times during the day. Also, I can still use any extra space on those drives for data. Example I moving almost a 1tb of movies to one of those drives to rip the DRM from those files.
 
maverick100 said:
This happens with any drive that is setup for TM. TM will no long let you store date on the drive except TM. I am an avid user of CCC; I removed my two time machine drives and have setup 4 SSD's as CCC backups. They are set to run CCC at 4 different times during the day. Also, I can still use any extra space on those drives for data. Example I moving almost a 1tb of movies to one of those drives to rip the DRM from those files.
Click to expand...
CCC?
 
Hey all, sorry for the off topic question, but this isn't worth starting it's own thread over. Why do some apps do this?

HandBrake 1.4.2 is currently the newest version available.
(You are currently running version 1.5.1.)?

1..5.1 is the latest on the page (not listed as beta) However the sparkle updater didn't pick up the update and downloading from the site and updating, now shows this. Handbrake isn't the first app to do this, but I was curious as to why they do this for public release software? Anyone know? Thanks.
 
MacinMan said:
Hey all, sorry for the off topic question, but this isn't worth starting it's own thread over. Why do some apps do this?

HandBrake 1.4.2 is currently the newest version available.
(You are currently running version 1.5.1.)?

1..5.1 is the latest on the page (not listed as beta) However the sparkle updater didn't pick up the update and downloading from the site and updating, now shows this. Handbrake isn't the first app to do this, but I was curious as to why they do this for public release software? Anyone know? Thanks.
Click to expand...
FWIW - I rarely use HandBrake, but have it. After seeing your post I checked my version and I was on 1.4.2, so I tried to update it. The updater stated I was on the latest version 1.4.2. Their web site indeed has 1.5.1 and I downloaded it manually. After downloading 1.5.1 and running it, it's updater states the same as you see. My guess is that it has nothing to do with the OS, and the issue is with the info the developer has on the server where the App updater checks. Maybe if you send a note to the developer is an easy fix. Hopefully this developers cares more than Apple does about the TM issues. Thanks for the tip - as I now have HandBrake 1.5.1
 
likegadgets said:
FWIW - I rarely use HandBrake, but have it. After seeing your post I checked my version and I was on 1.4.2, so I tried to update it. The updater stated I was on the latest version 1.4.2. Their web site indeed has 1.5.1 and I downloaded it manually. After downloading 1.5.1 and running it, it's updater states the same as you see. My guess is that it has nothing to do with the OS, and the issue is with the info the developer has on the server where the App updater checks. Maybe if you send a note to the developer is an easy fix. Hopefully this developers cares more than Apple does about the TM issues. Thanks for the tip - as I now have HandBrake 1.5.1
Click to expand...
You're welcome. I'll give it a few days and see if it sorts itself out. It might have something to do with that app now being a universal binary, and the sparkle info not fully being updated to reflect both platforms now. When some apps I use started adding a silicon specific arch there were version differences between the two for a while. Handbrake is usually solid, so I'm sure the developer will correct any issues asap.
 
After reading through this thread and trying everything that worked, then didn't work again on the next page, the only thing that has worked for me the first time is excluding your homedir files: ~/Library/Metadata directory. This was on my new M1 iMac running macOS 12.1 at the moment and a brand new WD USB-C 5TB drive partitioned in half with one 2.5 partition for SuperDuper! and the other for TimeMachine. SuperDuper! I've been using for many years now and its always been reliable for me, no matter the storage device, so it had to be used again now to get at least some sort of reliable backup.
Next I have TimeMachine setup to do its automatic backups to test this and see if its really working with this patch or not. The question I have though is, what's in this directory and do I need to copy it back in after at TimeCapsule restore or will MacOS be OK with just recreating it??
 
curtgrubel said:
After reading through this thread and trying everything that worked, then didn't work again on the next page, the only thing that has worked for me the first time is excluding your homedir files: ~/Library/Metadata directory. This was on my new M1 iMac running macOS 12.1 at the moment and a brand new WD USB-C 5TB drive partitioned in half with one 2.5 partition for SuperDuper! and the other for TimeMachine. SuperDuper! I've been using for many years now and its always been reliable for me, no matter the storage device, so it had to be used again now to get at least some sort of reliable backup.
Next I have TimeMachine setup to do its automatic backups to test this and see if its really working with this patch or not. The question I have though is, what's in this directory and do I need to copy it back in after at TimeCapsule restore or will MacOS be OK with just recreating it??
Click to expand...
The easiest way to test that is once you have a backup of those files, delete your current copies, and reboot. See what the system does. If you have issues, restore your backups.
 
The easiest way to test that is once you have a backup of those files, delete your current copies, and reboot. See what the system does. If you have issues, restore your backups.

I tried to backup the Metadata directory but not all files were copied, even rsync using sudo was not able to make a full copy. So I renamed the Metadata dir and rebooted. System created a new Metadata dir for me. I removed the exclude in TimeMachine and my TimeMachine backups are still running successfully so far after a couple automatic passes were made. I’ll update this thread again in a few days after it’s run awhile and report the results. Thanks..
 
  • Like
Reactions: MacinMan
randomgeeza said:
I'm joining the conversation again... Bought myself a new 2TB Samsung SSD. And on trying the initial backup the FindMy fix workaround didn't work. Even though it has worked for me twice before. I haven't tried the other exclusions mentioned previous, I can't be bothered in all honesty.

For now I am sticking with CCC. It seems to work flawlessly every time and it means I am getting my money's worth out of it.
Click to expand...
Yes I agree completely, I have moved my TM drives to CCC on times intervals through out my the day. Example, they back up a 8:00 am, 11:00 am, 3:00 pm, and 6:00 PM. Works like a champ.
 
  • Like
Reactions: randomgeeza
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