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.
Carbon Copy Cloner - Users Thread - Yosemite to Mojave to Big Sur - and after
- Thread starter mikzn
- Start date
- Sort by reaction score
Carbon Copy Cloner 6.0.5-b1 available if you have beta downloads enabled.
- New
We added a new "macOS Downgrade Assistant" feature, accessible via CCC's Utilities menu. The Downgrade Assistant can assess a backup volume's compatibility with Migration Assistant, and will create macOS Installer media using a specified volume and installer application. - New
We added another small new feature in the source and destination selectors. If the selected source or destination is a network volume, or a folder on a network volume, you can hold down the Option key to reveal a "Switch to AFP" or "Switch to SMB" menu item. We frequently see slow performance and errors from SMB-mounted volumes, and we often recommend that people try "the other" protocol when the current protocol isn't working out. Now we've made it really simple to switch between the two to see if using a different protocol will yield better results. - Changed
Tasks in the sidebar can once again be arranged when the sidebar sorting is configured as "Manual". - Changed
Made some adjustments that should improve performance when a task is writing large files to a rotational destination. Made a separate adjustment that should improve performance when writing to ExFAT-formatted volumes.
Just checked now, that update is not showing up.
Edit: Reinstalled version 6.04, did the "Check for updates" and that popped up the latest beta as you reported.
beta 6.0.5 b1 didn't show the b2 update at all.
Last edited:
beta 6.0.5-b1 had a bug that broke checking for updates - that was fixed in -b2
You did exactly what you needed to workaround that bug.
Since this has more to do with Monterey I discuss it in the other thread.
Last edited:
Many thanks to the moderators for moving this thread from the "Big Sur" forum to a more generic and app specific location - no longer in the "Big Sur Only" section
Thanks ?
Thanks ?
FWIW - rMBP 2015 Model replace SSD - in case anyone is interested or looking to do the same - just used CCC 6 "clone" to replace a 500g blade with a 1TB blade (Samsung 970 Pro)
Worked like a charm and clone is working perfectly after installed - rMBP 2015 15" i7 - took about 30 min including the incremental CCC back up / update just before the SSD swap
Worked like a charm and clone is working perfectly after installed - rMBP 2015 15" i7 - took about 30 min including the incremental CCC back up / update just before the SSD swap
Last edited:
Of course I'll read the instructions...but, is it as simple as connecting a new; empty and formatted SSD drive? I've been using a 500GB but have a 1TB available . MBPro 2017 with 500GB internal storage.
You cannot replace the SSD on the MBP 2017 (my post above was for a 2015 rMBP - sorry for any confusion) - the ability to change the SSD pretty much ended with the 2015 models
But you can certainly easily make a 'Bootable Clone" as long as the external drive (destination drive) is "bootable" - again depends on the macOS ? Mojave? Catalina? Big Sur? Monterey? then choose the correct version of CCC ?
If using CCC 6 for Catalina / Big Sur / Monterey use the "Legacy Bootable Back Up Assistant" for the first clone - see screen shot below
Last edited:
Carbon Copy Cloner 6.0.5-b3 available if you have beta downloads enabled. This version is for Catalina or newer only.
- New
We added a new "macOS Downgrade Assistant" feature, accessible via CCC's Utilities menu. The Downgrade Assistant can assess a backup volume's compatibility with Migration Assistant, and will create macOS Installer media using a specified volume and installer application. - New
We added another small new feature in the source and destination selectors. If the selected source or destination is a network volume, or a folder on a network volume, you can hold down the Option key to reveal a "Switch to AFP" or "Switch to SMB" menu item. We frequently see slow performance and errors from SMB-mounted volumes, and we often recommend that people try "the other" protocol when the current protocol isn't working out. Now we've made it really simple to switch between the two to see if using a different protocol will yield better results. - Changed
Tasks in the sidebar can once again be arranged when the sidebar sorting is configured as "Manual". - Changed
Made some adjustments that should improve performance when a task is writing large files to a rotational destination. Made a separate adjustment that should improve performance when writing to ExFAT-formatted volumes. - Changed
b3: Fixed a display issue in the Legacy Bootable Backup Assistant that would occur when selecting a SoftRAID destination volume. - Fixed
b3: Fixed an issue that arose recently in macOS Monterey that was causing failures while trying to configure new Remote Macintosh tasks. - Fixed
b3: Fixed an issue affecting tasks configured to run "When the source or destination is remounted" in which the tasks would fail to run on volume appearance if the destination's System volume had been removed.
Sorry just found this useful thread after writing a new post. looks like I should have been here. I just downloaded the trial of CCC...planning to upgrade my Mac HD to SSD. The SSD is currently connected by a USB-SATA cable. I cloned the HD to the SSD overnight. I just did a restart with option held down to boot from the SSD but it doesn’t appear in the bootable list. Would you expect it to appear as bootable? I assumed I could use CCC in this way. Welcome any guidance from the knowledgeable. Cheers
Issue with a new (2021) 16 inch MacBook Pro. It worked fine on Monday (initial use on this machine) and tonight it's a no-go:
A report has been sent to Apple to see what the problem is.
A report has been sent to Apple to see what the problem is.
FWIW - here are a few thoughts - you may have already gone thru?
1) are you sure the USB cable allows the drive to be bootable? - I use an an enclosure for all my back up drives (about 10 or so) and I don't partition them into smaller volumes - every one of the enclosed SSD's boot fine as external as a test before swapping with the internal
2) Since you mention, and "if I understand correctly" you are upgrading HDD to SSD - is it possibly an older mac and macOS? are you using CCC-5 ? and pre calalina macOS ?
3) I have never had to start with the option button held down - if the drive is select-able in the preferences < Startup Disk you should see it and be able to select it?
Here is a screen shot on my Mojave MBP - very similar on Monterey MBP also
Carbon Copy Cloner 6.0.5 is now available. This version is for Catalina or newer only.
- New
We added a new "macOS Downgrade Assistant" feature, accessible via CCC's Utilities menu. The Downgrade Assistant can assess a backup volume's compatibility with Migration Assistant, and will create macOS Installer media using a specified volume and installer application. - New
We added another small new feature in the source and destination selectors. If the selected source or destination is a network volume, or a folder on a network volume, you can hold down the Option key to reveal a "Switch to AFP" or "Switch to SMB" menu item in the Source and Destination selectors. We frequently see slow performance and errors from SMB-mounted volumes, and we often recommend that people try "the other" protocol when the current protocol isn't working out. Now we've made it really simple to switch between the two to see if using a different protocol will yield better results. - Changed
Tasks in the sidebar can once again be arranged when the sidebar sorting is configured as "Manual". - Changed
Made some adjustments that should improve performance when a task is writing large files to a rotational destination. Made a separate adjustment that should improve performance when writing to ExFAT-formatted volumes. - Changed
Fixed a display issue in the Legacy Bootable Backup Assistant that would occur when selecting a SoftRAID destination volume. - Fixed
Fixed an issue that arose recently in macOS Monterey that was causing failures while trying to configure new Remote Macintosh tasks. - Fixed
Fixed an issue affecting tasks configured to run "When the source or destination is remounted" in which the tasks would fail to run on volume appearance if the destination's System volume had been removed.
just curious did you get it sorted out?
I am using CCC 5 on Mojave and CCC 6 on Monterey and CCC 6 seems much quicker than CCC 5 in my case and hardware
I have a few questions on how CCC works currently, as I am a bit confused.
I noticed that people in this thread have different needs and use cases for the software ( incremental vs fullback up versus external bootable). in the methods used to solve each one of these problems appears to be slightly different. I would like to find out what the best method is for something that is close as possible to a full backup.
I also find CCC documentation to be extensive, but a YouTube video With a bit of explanation on the use of the current version of the product (6.x.x) would go a long way.
for me personally, the reason why I’m interested in CCC:
* now that TM function is different than Mojave and before, I am looking for the closest and most stable method of restoring an OS to a previous state ( whether that is one day ago or one week ago ) after unfixable issues in the OS are discovered. I personally don’t need to work off of an external volume
* I found Time Machine unstable in Big Sur ( backing up and during restore).
* TM is now more complicated With the restore version of migration assistant
* in the past, I have always done a full system restore because many times I don’t know what caused the system issues or a particular app to become unstables. a full restore saves me from figuring it out which is a time suck.
* speed is not critical to me, because the data stability takes precedence. I can restore overnight.
* I feel like the OS is more delicate than it used to be.
I’m currently using an Intel Mac on Big Sur
here are my questions.
TL;DR
1. why do people here choose to use snapshots? is it to restore one particular app? if so how is this task performed?
2. which method would you recommend that comes the closest to restoring the OS and its contents?I have used migration assistant (non-CCC) with two unexplained failures. I suppose at the moment I don’t mind using features that will be deprecated in newer OSs in the near future, as long as it works For now.
3. am I better off keeping a migrated HFS plus volume formatted on an old computer ( rather than APFS ) as a backup? I remember reading somebody saying stick with APFS, but I can say I've only had bad luck with it. On the other hand I never had an issue with HFS+. does the backup use the TM old method on that volume? or will this make no difference
4. how is a restore performed?
5. Can Legacy Bootable Backup Assistant" be used to restore?
thanks
I noticed that people in this thread have different needs and use cases for the software ( incremental vs fullback up versus external bootable). in the methods used to solve each one of these problems appears to be slightly different. I would like to find out what the best method is for something that is close as possible to a full backup.
I also find CCC documentation to be extensive, but a YouTube video With a bit of explanation on the use of the current version of the product (6.x.x) would go a long way.
for me personally, the reason why I’m interested in CCC:
* now that TM function is different than Mojave and before, I am looking for the closest and most stable method of restoring an OS to a previous state ( whether that is one day ago or one week ago ) after unfixable issues in the OS are discovered. I personally don’t need to work off of an external volume
* I found Time Machine unstable in Big Sur ( backing up and during restore).
* TM is now more complicated With the restore version of migration assistant
* in the past, I have always done a full system restore because many times I don’t know what caused the system issues or a particular app to become unstables. a full restore saves me from figuring it out which is a time suck.
* speed is not critical to me, because the data stability takes precedence. I can restore overnight.
* I feel like the OS is more delicate than it used to be.
I’m currently using an Intel Mac on Big Sur
here are my questions.
TL;DR
1. why do people here choose to use snapshots? is it to restore one particular app? if so how is this task performed?
2. which method would you recommend that comes the closest to restoring the OS and its contents?I have used migration assistant (non-CCC) with two unexplained failures. I suppose at the moment I don’t mind using features that will be deprecated in newer OSs in the near future, as long as it works For now.
3. am I better off keeping a migrated HFS plus volume formatted on an old computer ( rather than APFS ) as a backup? I remember reading somebody saying stick with APFS, but I can say I've only had bad luck with it. On the other hand I never had an issue with HFS+. does the backup use the TM old method on that volume? or will this make no difference
4. how is a restore performed?
5. Can Legacy Bootable Backup Assistant" be used to restore?
thanks
Last edited:
Not sure if this will cover your needs, but I've been using CCC rather than TM for many years (also due to stability issues) with the following backup scheme:
1. My main user directory is backed up nightly to one of seven sparsebundles on a separate server, one for each day of the week. This provides me with a week to realize that I've broken something and recover the most recent non-broken version.
2. The entire system is backed up to a bootable clone (I'm running El Capitan until I move to an Mx machine) once a week to one of two rotating partitions on a backup drive.
3. I make manual full-system backups to two external drives on an aperiodic basis, one of which lives in an off-site location (a safe deposit box). I always (!!!!) do one of these prior to a system update. Fifty-plus years of working with computers makes one paranoid about backups.
Last edited:
I use CCC for incremental backups and superduper for bootable backups on different backup drives.
Why superduper for bootable? is it superior for that specific task, and if so for what reason? if that's the case I might mirror your method in purchasing both programs
It makes bootable drives really well. ccc not so much. I use multiple drives for backups. ccc does incrementals just fine but I have had problems with ccc making boot drives. both are still good for intel. I don't have any m1/2 machines yet but superduper works on my sons m1 air. I don't use tm except for last ditch sort of things on my wifes computers. Never have trusted it
is the purpose of you wanting a bootable drive to keep working with no downtime? or is it a method you use for backup? I asked because I thought this is not possible anymore with the changes in apple's programming. In the past this made sense to me that a disk image can be mapped onto an drive in dire circumstances.
were your CCC drive issues before or after Big Sur,In was the issue during a restore task or a backup task?
sorry for these questions, but the reason why I ask has to do with I'm still trying to figure out the best game plan for the future now that the situation is a bit more complicated under Big Sur and beyond
Last edited:
ccc can do a bootable drive but it's not stable no matter what they say. superduper took a while before he got the bootable working. apple doesn't much care about backups in general otherwise they would have fixed TM a long time ago. it's why I use 2 programs. I have had a copy of superduper since 10.4, ccc has been around almost as long, 10.5
after big sur everything got mucked up.
after big sur everything got mucked up.
I use CCC for a bootable external SSD.
Seems fine. I have been updating the macaoS on that SSD.
Seems fine. I have been updating the macaoS on that SSD.