Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Carbon Copy Cloner 7 - Users Thread

I will not go into technical details here but due to changes introduced in Big Sur, no third party tool can create a valid, sealed System Partition with an Apple signed Snapshot. When CCC or other utilities seem to do this they "wrap" an Apple Utility (asr). There have been several releases where that mysteriously stops working.
You also cannot update the System Partition, only the Data Volume.
I have switched to doing Data only clones. On an M1/M2, if you hit the unusual condition of a corrupted value, there could be deeper issues with the hidden system partitions (reboot etc.) I have NEVER ended up there except when I wanted to revert from Ventura.
The process for that is a complete wipe and restore either from recovery or (better) the Apple Configurator 2 with an IPW. Then use Migration Assistant with the CCC clone. I once brought my Mac Studio with 3TB of data back from the brink in about 2 1/2 hours using an SSD for CCC Data clone.
Time Machine from my NAS would take days, literally.
 
  • Like
Reactions: Realityck and Kenjutsuz
^^^^

As posted above. all my OS SSDs have been cloned at one time or another and so far Unknown.jpegI have not had any issues. Data only clones are quite easy and require no software just drag and drop. Back in the MacOS day, you could clone an entire startup disk by dragging and dropping👍

Lou
 
Last edited:
  • Like
Reactions: 0134168
haralds said:
I will not go into technical details here but due to changes introduced in Big Sur, no third party tool can create a valid, sealed System Partition with an Apple signed Snapshot. When CCC or other utilities seem to do this they "wrap" an Apple Utility (asr). There have been several releases where that mysteriously stops working.
You also cannot update the System Partition, only the Data Volume.
I have switched to doing Data only clones. On an M1/M2, if you hit the unusual condition of a corrupted value, there could be deeper issues with the hidden system partitions (reboot etc.) I have NEVER ended up there except when I wanted to revert from Ventura.
The process for that is a complete wipe and restore either from recovery or (better) the Apple Configurator 2 with an IPW. Then use Migration Assistant with the CCC clone. I once brought my Mac Studio with 3TB of data back from the brink in about 2 1/2 hours using an SSD for CCC Data clone.
Time Machine from my NAS would take days, literally.
Click to expand...
My god, I don´t know how times I have said this. Once more. OF COURSE you can clone System partition. What you can´t do is update it. Just use the "Legacy Bootable Copy Assistant…"

bombich.com

Creating legacy bootable copies of macOS (Big Sur and later) - Bombich Software

bombich.com bombich.com
 
flowrider said:
^^^^Are you saying you can't update the clone❓

Lou
Click to expand...
You can't use CCC to incrementally update the system version after making a legacy bootable clone. Thats why the developer says it like a limited time snap shot. It's also why we do a complete wipe of the volumes before running a legacy bootable clone process. (APFS replication)
 
  • Like
Reactions: 0134168
Realityck said:
You can't use CCC to incrementally update the system version after making a legacy bootable clone. Thats why the developer says it like a limited time snap shot. It's also why we do a complete wipe of the volumes before running a legacy bootable clone process. (APFS replication)
Click to expand...
You men that Legay proccess wipe it for you, right? Not necessary to wipe it manually before.
 
Realityck said:
I actually use disk utility to do a group volume wipe then do the legacy bootable clone procedure like post #3

If the dev fixed it to be able to wipe both volumes, great. But not checked that.
Click to expand...
I have never wiped it by hand. Legacy proccess does it perfect.
 
Not sure I understand what you folks are saying⁉️⁉️❓❓ As posted earlier, all four of start-up SSDs have been cloned at one time or another. The SSD I am on right now was cloned from Monterey 12.4 and updated to Ventura Bata 3h then to Beta 3i and no issues. Downloading Beta 4 now❗

Lou
 
flowrider said:
Not sure I understand what you folks are saying⁉️⁉️❓❓ As posted earlier, all four of start-up SSDs have been cloned at one time or another. The SSD I am on right now was cloned from Monterey 12.4 and updated to Ventura Bata 3h then to Beta 3i and no issues. Downloading Beta 4 now❗
Click to expand...
I´m afraid @Realityck is using Ventura. Which, of course, is not supported by CCC.
 
Realityck said:
6.1.2 CCC works with Ventura, just not advertised. The 6.1.3-b1 is specific to Ventura testing and works with Ventura beta 4.
Click to expand...
Be-ta. All of them. When I say that Legay proccess wipes the drive, I mean 12.5 and before.
 
Now available CCC 6.1.3-b2 (7389) — This is a pre-release update of CCC for Ventura beta testing cycle

  • Changed
    The clonefile replacement procedure will no longer be used if snapshots are disabled on the destination. The primary purpose of using that procedure is to use storage more efficiently so that we can retain more snapshots, and that's moot if we're not retaining snapshots.
  • Fixed
    When you auto-fill a password in CCC's Email Settings (i.e. from the system's "Passwords..." menu option that appears when the password text field is given focus), that password is now correctly stored in CCC's keychain.

Earlier 6.1.3-b1 notes
 
Last edited:
  • Like
Reactions: flowrider, Weaselboy and 0134168
Now available CCC 6.1.3-b3 (7393) — This is a pre-release update of CCC for Ventura beta testing cycle

  • Fixed
    b3: Addressed an exception that was occasionally occurring during task history database migration.
  • Changed
    b3: Addressed an issue in which new tasks created by 6.3.1-b2 would not run on schedule if ethernet was unavailable. If you're seeing this, apply this update, then click on the Automation selector, then save the task. The task will then resume its normal schedule.
 
  • Like
Reactions: 0134168
The current CCC (6.1.3-b3) backup process, has a new issue with the way APFS utility is working in beta 5.

You'll see the scripted volume APFS replication conclude prematurely not backing up data volume for legacy bootable volume copy.

Temp work around is just run a standard backup instead.

Using a M1 Max MBP.
 
Last edited:
  • Like
Reactions: 0134168
Realityck said:
The current CCC (6.1.3-b3) backup process, has a new issue with the way APFS utility is working in beta 5.

You'll see the scripted volume APFS replication conclude prematurely not backing up data volume for legacy bootable volume copy.
Click to expand...
The Data Volume failure observed above in legacy bootable copy was caused by either of two processes that go into a high CPU state at times under beta 5. Spotlight seems to prevent the data volume from unmounting with its process goes high %CPU, that or the new mail running powerd with high %CPU. So after a few days of using your system it now works.

The 4 step process is System volume is copied, then the Preboot, then Recovery, then the Data volume.
 
Realityck said:
The Data Volume failure observed above in legacy bootable copy was caused by either of two processes that go into a high CPU state at times under beta 5. Spotlight seems to prevent the data volume from unmounting with its process goes high %CPU, that or the new mail running powerd with high %CPU. So after a few days of using your system it now works.
Click to expand...
Good news, MacOS 13 beta 6 doesn't appear to have the issues that beta 5 added. So not seeing powerd and mds_stores (spotlight) hogging CPU that caused the creation of data volume backup to fail during legacy bootable copy.

Still using CCCC 6.1.3-b3
 
  • Like
Reactions: gank41 and 0134168
Now available CCC 6.1.3-b4 (7401) — This is a pre-release update of CCC for Ventura beta testing cycle
  • Fixed
    b4: The "System exclusion" is no longer applied in cases where the destination is a subfolder on the startup disk.
  • Changed
    b4: The Compare window now shows files discovered on the source and destination separately. Especially for really slow destinations like NAS volumes, this will give a clearer indication of ongoing progress.
 
  • Like
Reactions: gank41, flowrider and 0134168
Realityck said:
You need to prepare the volume for APFS replication to work. 11.x and the new 12.0 creates both a system and data volumes. Erase both in the disk utility -> unmount backup target storage, erase system volume not the data volume, select erase volume group as preparation. In CCC you need to target that one volume as a destination in CCC with a new task. Then you will need to use the CCC choices in under your destination.
View attachment 1800812

click on the destination disk you will see this.

View attachment 1800814
Enter the legacy bootable backup assistant. I don't use SafetyNet for incremental backups, so that is off. Allow CCC to erase the volume.

View attachment 1800815
Now when you start CCC backup task it should tell you that you are Replicating the APFS filesystem data. After it gets done this in disk utility should show both a system volume and a data volume. Now see if it will allow you boot off of it.
Click to expand...
Outstanding. Lastest Ventura beta + CCC 6.1.3-b4. I don't remember how many major releases I have been without a bootable clone. Worked like a charm. Gracias........
 
  • Like
Reactions: gank41, 0134168 and Realityck
Is this game over for CCC?

"The APFS replication procedure failed."

Followed the directions. That led to the "Legacy bootable copy assistant" choice. And it fails.
Just to make sure there wasn't a USB drive controller issue or what have you, I have the very same type of SSD installed internally. It's the exact same Crucial SSD and even the exact same size. Follow the CCC troubleshooting to manually erase it, delete that ASRDataVolume (that appears after the 2nd failed attempt), and try again. Fails.

So this is cryptic and maybe I'm missing a step? I get that they're struggling.

Not sure what to try next... I mean besides googling different cloning apps!

I need a cloning app that makes a fully 1:1 bootable clone like CCC used to. Their 'temporary Time Machine mode' isn't acceptable.
 
serr said:
Is this game over for CCC?

"The APFS replication procedure failed."

Followed the directions. That led to the "Legacy bootable copy assistant" choice. And it fails.
Just to make sure there wasn't a USB drive controller issue or what have you, I have the very same type of SSD installed internally. It's the exact same Crucial SSD and even the exact same size. Follow the CCC troubleshooting to manually erase it, delete that ASRDataVolume (that appears after the 2nd failed attempt), and try again. Fails.

So this is cryptic and maybe I'm missing a step? I get that they're struggling.

Not sure what to try next... I mean besides googling different cloning apps!

I need a cloning app that makes a fully 1:1 bootable clone like CCC used to. Their 'temporary Time Machine mode' isn't acceptable.
Click to expand...
Did you follow the procedure in post #3? If something doesn't work with the CCC 6.1.3-B4 just go under help and submit a problem with your logs. For me its is working as a onetime legacy bootable copy, but you have to fully erase the APFS volume group ahead of executing the legacy bootable copy of ratios to work. You cannot make incremental clones of APFS volume sets like in the past. You can of course make standard backups using just that data volume that will suffice as a ASR source for migration assistant recovery after you wipe/reinstall the MacOS from DFU restore.
 
Last edited:
  • Like
Reactions: 0134168
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