Well consider this, Carbon Copy will give you a bootable backup while TM won't so might be some incentive to use while waiting for TM issues to be resolved on Apple's end. At least you'll have a reliable backup in case of emergency as well. Your issues seem to be more complex than mine were to resolve, and I was myself going to switch to CCC, if I hadn't gotten TM working again.
I use a CCC competitor called SuperDuper from ShirtPocket. The have a new native M1 version of the software and also creates a backup bootable copy. I have read good reviews of both CCC and Superduper. Typically I have 3 drives connected for backups - two time machines and a drive for Super Duper that dues constant updates. I also have to SSD drives I take when travelling one for TM and one for SuperSuper which I update before the trip and during so additional files are backed up. Excessive, maybe. All it takes I plugging the drives - all are encrypted.
UPDATE - Just spend time with Sr. Advisor - they requested a screen recording of starting a time machine backup until the non completion message and then a running diagnostic tool they sent me that took a while. I uploaded the two files to Apple and will wait for a follow up from engineering.
I own a license to both SuperDuper, and CCC. I stuck with CCC while Shirt pocket worked out the bootable backup issues. Also, I chose CCC over SuperDuper for a while because it was able to clone the recovery partion, while SuperDuper was not. I like both programs, and have three solutions for backup.
Hi there, welcome to the thread! As far as encryption goes, I recommended against it strictly for speed with mechanical drives. It worked OK under Big Sur, but with Monterey, it was taking forever to make the first backup. If you're using an SSD for the backup, you probably wouldn't notice much difference. It seems like Time machine is also hit, or miss here as it seems to work for some, but not others. I was the one who started the thread, on this topic, and thought the issue had been resolved. Turns out, that the more people who show up are having more complex issues than my own.
According to senior tech at apple, they are now starting to say this is THEIR problem and specifically associated with something in Monterey. Though, i'm sure apple will not cop to this anytime soon.Hi there, welcome to the thread! As far as encryption goes, I recommended against it strictly for speed with mechanical drives. It worked OK under Big Sur, but with Monterey, it was taking forever to make the first backup. If you're using an SSD for the backup, you probably wouldn't notice much difference. It seems like Time machine is also hit, or miss here as it seems to work for some, but not others. I was the one who started the thread, on this topic, and thought the issue had been resolved. Turns out, that the more people who show up are having more complex issues than my own.
Hopefully, everyone here besides myself, will be able to resolve their issues soon
Well, I'm glad Apple has acknowledged they have an issue, or at least beginning to. Maybe it's related to the memory issue people started reporting today.
I wonder if I should have done that after creating the thread. I just found out about the option though, just now reading your post.
I was starting to think, it maybe the type of install done matters. For example, my iMac has not been wiped clean since the clean install of Catalina done a couple years ago. So, my system has gone from Catalina to Big Sur, and now to Monterey. Yes, I had some issues when doing the first backup after the upgrade until I started over without an encrypted disk. Meanwhile, others here who either have a new Apple Silicon based mac, or an existing mac, but did a clean install seem to be having more complicated issues. The platform may come into play as well.
Hi Bernard,
TM has never really been a thing to expect to have issues in the past. Even with all the bugs Apple has had with their new releases, TM has always been something that's worked. I wonder if it has to do with the new Apple Silicon macs. Before, they just had to focus on Intel. Now they have both platforms to deal with.
agreed. i've now troubleshot this in every single way. this is apple's issue and particularly something in monterey that is causing the issue. it needs a fix.
i'm stuck, too, because my previous TM machine drives got nuked in trying to fix this. I've now migrated everything manually over to an external ssd in case an upgrade on monterey cascades into any more severe issues regarding my internal ssd.
my apologies. i'm a newbie here and I don't know the rules about threads. if we can somehow keep a thread going with the TM issues in Monterey, that would be great. I think it is going to be a growing list of people, but since the amount of users who religiously use TM is small, it's going to take some time for Apple to take real notice.
It's OK, it's not so much about violating any rules as that hasn't been done. I'm more asking how can we update the status of this thread because the types of issues (though the same theme) have increased beyond my own speed issue.