Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Thanks! I do monitor the threads periodically but since I clearly don't have an unbiased opinion I tend to keep quiet. :) Anyway, with v6 we made so many changes to the interface, as well as under the hood, that we really want to keep on top of things. Please continue bringing issues to our attention!

Not sure if you know, but there are only six of us in the company, so thank you for being patient as we support v6. Our responses may be slower and a little bit less in-depth than usual, but we're trying to spend our time on fixing the underlying issues versus individually troubleshooting.
Thrilled to see active responses from CCC. :D For a company of 6 people, you guys rock, Sarah. A lot of us here hold CCC close to our tech hearts. Thanks for jumping in and interacting with us shy people. :p
 
Hi, Sarah from Bombich Software here. We've documented and reported a macOS bug that prevents retention of some custom icons, but I'm trying to figure out if this is different. The link discusses Catalina but the issue is also present in Big Sur.
I join some of the others here is this thread and also thank you for posting an letting us know you are watching the thread and discussions 👍

Am a long time CCC user and a big fan - had a Mojave / 2015 MBP battery swell (a while ago) and it stopped working :( - luckily I was able to use my CCC Mojave clone on a external SSD (1 day old) on a different MBP and was back up and running with all my data and software working within a few hours - very cool :cool: and a big relief

Also use CCC to make separate weekly back ups of my Photos libraries and Music folders - great product 👍
 
We think we have a fix for the icon issue. It'll be out in the first .x update, which we're currently testing before pushing it out to everyone.
 
I don't think so. This is the "unfixable" issue from our documentation:

Finder will not show, nor allow you to set custom icons on other Catalina and Big Sur startup disks​

Finder will show and allow you to customize the volume icon for your current startup disk, but not for other Catalina- or Big Sur-bearing startup disks that your Mac is not currently booted from. This problem is not specific to CCC backups, but we see this frequently because CCC can create copies of macOS System volumes. This problem is the result of a design flaw in the implementation of custom icons in an APFS volume group. Up to macOS Catalina, the custom volume icon is stored in a file at the root of the startup disk named ".VolumeIcon.icns". To keep the System volume read-only, yet allow the apparent modification of this icon file, Apple chose to create a symbolic link at the root of the startup disk that points to System/Volumes/Data/.VolumeIcon.icns. For the current startup disk, this path resolves correctly because the Data member of the volume group is mounted at /System/Volumes/Data. That's not the case for external volumes, those Data volumes are mounted at /Volumes/CCC Backup - Data (for example). As a result, the symbolic link to .VolumeIcon.icns is unresolvable for any volume that is not the current startup disk.

We have reported this issue to Apple (FB7697349) and we are currently awaiting a response.
 
On an M1 Silicon computer can CCC now make a backup of the internal startup volume?
Yes. it shows as two different volumes in CCC on the left menu. HD and DATA. I have the new M1 Mini and have used CCC since 2007. always SafetyNet off. I make a bootable clone of the main SSD and a clone of my media drive
 
And, is 6 good for Catalina as well? I hesitate to upgrade to Big Sur now.
;JOOP!

Yes - Good for Catalina and Big Sur.

TinyGrab Screen Shot 5-23-21, 1.29.30 PM.png


Lou
 
  • Like
Reactions: LizKat and Big Ron
6.x. There is one icon issue, mentioned before, which is macOS's issue and we're waiting for a fix. This is a second issue that cropped up in 6.x that will be fixed.
How reliable is using Legacy Mode with the use of the state of ASR?
 
I've been a fan of CCC since the introduction of OSX, I think it was 5$ shareware back then.
Looking forward to upgrading to v6.
We live in a blessed time:
in 1984 my boss had to buy me a C compiler for VMS at $17K.
... this is not an invitation to double all fees! it's just an example of how lucky we are in 2021.
;JOOP!
 
  • Like
Reactions: GrampaJiiji
"how lucky we are in 2021."

Ain't that a fact!
Carbon Copy Cloner is the one app I've kept updating throughout, ease of use and peace of mind are paramount to safe computing at my age.
 
Last edited:
Hello Forum,

I just found this app and I want to give it a try and start my 30-days trial

is CCC 6.0 stable macOS Catalina 10.15.7 (19H1030)?

Any known issue?​


MBP 15" Mid 2014


TIA

Camelia

 
How reliable is using Legacy Mode with the use of the state of ASR?
It's 100% dependent upon Apple's ASR tool. Every time a new version of Big Sur comes out, there is the possibility of changes to ASR's reliability. In short, we can only look to the past. We know it didn't work on 11.0, 11.1 and 11.2, started working on 11.3, and have no idea what the future will bring.

is CCC 6.0 stable macOS Catalina 10.15.7 (19H1030)?​

I've used it successfully for months on Catalina for both my locally-attached and network backups. That said, we have identified a couple of rather uncommon edge cases (a certain kind of minor source corruption, for example) that were causing issues and have a bug release in testing; it should be out this week.
 
It's 100% dependent upon Apple's ASR tool. Every time a new version of Big Sur comes out, there is the possibility of changes to ASR's reliability. In short, we can only look to the past. We know it didn't work on 11.0, 11.1 and 11.2, started working on 11.3, and have no idea what the future will bring.


I've used it successfully for months on Catalina for both my locally-attached and network backups. That said, we have identified a couple of rather uncommon edge cases (a certain kind of minor source corruption, for example) that were causing issues and have a bug release in testing; it should be out this week.
I just ran into a recoverable problem: on 2 different machines CCC refused to backup upgraded installations
of THE SAME applications, to know: { CCC (!), iMazing and Skim.
Help is on the way ...
;JOOP!
 
It's 100% dependent upon Apple's ASR tool. Every time a new version of Big Sur comes out, there is the possibility of changes to ASR's reliability. In short, we can only look to the past. We know it didn't work on 11.0, 11.1 and 11.2, started working on 11.3, and have no idea what the future will bring.


I've used it successfully for months on Catalina for both my locally-attached and network backups. That said, we have identified a couple of rather uncommon edge cases (a certain kind of minor source corruption, for example) that were causing issues and have a bug release in testing; it should be out this week.
Thanks for your reply. Top notch software. Still learning all the new changes.
Great and timely replies from your whole team.
 
6.0.1-b2 is available if you have beta downloads enabled.

  • b2: Addressed an edge case in which CCC would miss some folders when copying from an APFS volume to a non-APFS volume (typically when an iTunes Music folder had a non-ASCII character in its name).
    [*]Fixed
    b2: CCC no longer removes the "has a custom icon" bit from the destination volume's root folder, causing the Finder to not show the icon.
    [*]Changed
    b2: Files that fail postflight verification are now automatically tossed onto CCC's "try it again at the end of the task" queue for a second chance. If the secondary copy and verify fails, then we report the error.
    [*]Fixed
    b2: Resolved some cases where a task would fail, indicating an exception had occurred in the CloneKitService.
    [*]Fixed
    b2: Fixed an issue in which a task that was configured to create a bootable backup would fail, indicating that the destination volume was read-only.
    [*]Changed
    b2: Improved the handling of low-space conditions in cases where SafetyNet or snapshots are enabled on the destination.
    [*]Fixed
    b2: Addressed a memory leak that led to task failure while handling sparse files on APFS volumes (e.g. Dropbox online-only placeholder files were a big driver of this one).
    [*]Fixed
    b2: Addressed a handful of cases where a task would errantly report a "subtask timeout" while working through folders with very large numbers of files (e.g. 150K), despite no actual stall occurring.
    [*]Fixed
    b2: When copying content from a volume that has ownership disabled (especially NAS volumes), the ownership of the items on the destination is now set to the user that created the CCC backup task.
    [*]Fixed
    b2: Improved the performance of the dynamic performance chart when moving the CCC window from a retina to non-retina display.
 
Last edited:
My HD crashed recently. After Apple store replaced HD they loaded it with Big Sur (I was using Mojave before, trying to keep some 32 bit apps alive). After restoring my data thru Time Machine, my Mac is much slower than before. Today I attempted to create a bootable SSD (Samsung 1TB, using thunderbolt connector) using CCC. It will not show up in startup manager or after using option on startup. I've zapped PRAM and that didn't help either. At this point would it be better to install Big Sur directly on it and copy over data from my Time Machine backup? Any other fixes?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.