Carbon Copy Cloner 7 - Users Thread

[serr]

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.

Thanks for the reply Realityck

Oh boy...
This is a little cryptic to me. Is this instructing to erase the hidden and data volumes separately with Disc Utility and then clone to each separately with CCC?

I'm aware of the dual volumes (hidden system and data). I wasn't expecting to need to work them separately in CCC and didn't really see clear prompts for that.

 

[Realityck]

Thanks for the reply Realityck

Oh boy...
This is a little cryptic to me. Is this instructing to erase the hidden and data volumes separately with Disc Utility and then clone to each separately with CCC?

I connect/mount the Backup HD, then I launch disk Utility and then expand the Backup HD hierarchy to show the two volumes (Backup HD, data) and make sure both are unmounted, then select the Backup HD with erase and it should show group volume erase as a option. Once it has wiped both and it creates a backup HD showing on desktop with the usual Time Machine dialog asking if it can use that which i decline. Then you select that for your CCC target, right click on CCC legacy bootable copy option and then start the process of it doing a 4 stage APFS replication clone. This is a limited time backup, meant to be bootable, but not for incremental backups.

 

[serr]

I connect/mount the Backup HD, then I launch disk Utility and then expand the Backup HD hierarchy to show the two volumes (Backup HD, data) and make sure both are unmounted, then select the Backup HD with erase and it should show group volume erase as a option. Once it has wiped both and it creates a backup HD showing on desktop with the usual Time Machine dialog asking if it can use that which i decline. Then you select that for your CCC target, right click on CCC legacy bootable copy option and then start the process of it doing a 4 stage APFS replication clone. This is a limited time backup, meant to be bootable, but not for incremental backups.

I don't see any extra options by right-clicking on the legacy bootable copy option vs left-clicking. I see no option for a "4 stage APFS replication clone". I went through the motions again anyway and it fails the same.

 

[serr]

Right...

Any recommendations for a different cloning app?

 

[Realityck]

I don't see any extra options by right-clicking on the legacy bootable copy option vs left-clicking. I see no option for a "4 stage APFS replication clone". I went through the motions again anyway and it fails the same.

The 4 step process is System volume is copied, then the Preboot, then Recovery, then the Data volume. That is how the legacy bootable copy works when doing a APFS replication. There is nothing that is describing or named as such.
Right or left click was only meant as recollection, not exact, just find it and use that legacy bootable copy option.

 

[serr]

The 4 step process is System volume is copied, then the Preboot, then Recovery, then the Data volume. That is how the legacy bootable copy works when doing a APFS replication. There is nothing that is describing or names as such.
Right or left click was only meant as recollection, not exact, just find it and use that legacy bootable copy option.

What are the options to try when it fails?

I select the legacy bootable copy option. It lets me. It gives me the bootable system clone option and the allow CCC to erase button. I click that and then hit start. It starts and runs for a few moments and then gives me "The APFS replication procedure failed." error message.

I'm pretty sure I'm following instructions? I see the dialog windows and options mentioned in your post #3. I'm starting with a freshly formatted SSD to use for a destination.

If there's some folder structure to prepare (like the hidden volume for the system) that isn't mentioned by CCC or mentioned in their help page that comes up, can you spell that out for me step by step like I'm a little thick?

 

[Realityck]

Right...

Any recommendations for a different cloning app?

There is TimeMachine, SuperDuper of course available, but the first doesn't make snapshots, the 2nd isn't supported as well as CCC is by the dev. I am using the latest MacOS 13 beta 7 without issues on 2 Apple Silicon Macs.

 

[serr]

I don't believe Time Machine can make a bootable clone yet. Is that still correct?

That's the single thing I need. A bootable clone from a system drive. I don't actually need snapshots or the Time Machine style "roll back to last Tuesday" features. Just the ability to clone an entire system drive with OS and app installations.

I'm poking at MacOS 12 in order to be able to use some HDMI capture cards that require it for their driver. To be fair, I haven't tried Catalina or Big Sur. I kind of stuck to avoiding them because of the brick bug. Their drivers don't work in 10.13 or 10.14. I jumped ahead to MacOS 12 and they just work. So I've got that going for me!

I need to be able to clone this system for backup like I've become accustomed to though. And here we are.

 

[Realityck]

What are the options to try when it fails?

I select the legacy bootable copy option. It lets me. It gives me the bootable system clone option and the allow CCC to erase button. I click that and then hit start. It starts and runs for a few moments and then gives me "The APFS replication procedure failed." error message.

I'm pretty sure I'm following instructions? I see the dialog windows and options mentioned in your post #3. I'm starting with a freshly formatted SSD to use for a destination.

If there's some folder structure to prepare (like the hidden volume for the system) that isn't mentioned by CCC or mentioned in their help page that comes up, can you spell that out for me step by step like I'm a little thick?

So you are running Monterey, is the latest macOS 12.6 (21G115) release? AS/or Intel Mac? Are you using CCC 6.1.2 or the latest 6.1.3-b4?

Like I suggested at the start you could easily communicate this to the CCC developer and he would tell you whats going on with your submitted logs. Seriously he will respond.

Have you have done what CCC requires for system settings permissions such as for files and folders and full disk access there should be Carbon Copy Cleaner and com.bombich showing/enabled. Wondering if you granted CCC necessary permissions.

 

[Weaselboy]

I don't believe Time Machine can make a bootable clone yet. Is that still correct?

It could with older macOS versions, but that feature is now gone.

I think what Apple wants you to do now is use Internet recovery to reinstall the OS, then import your data from a Time Machine backup.

This new sealed OS volume Apple has added for security, with a separate Data volume, really makes things difficult for those cloning apps.

 

[serr]

It could with older macOS versions, but that feature is now gone.

I think what Apple wants you to do now is use Internet recovery to reinstall the OS, then import your data from a Time Machine backup.

This new sealed OS volume Apple has added for security, with a separate Data volume, really makes things difficult for those cloning apps.

Sure. I get the difficulties of chasing Apple's faux pas around this. And I understand their method. (Make USB installer to install OS. Migrate and/or use Time Machine.) This is a system for audio and video work and I need to make old school fully 1:1 clones. So it's going to have to copy that hidden system folder and the whole works!

I have a couple Linux tabs open in Firefox here. I think we're getting closer to the end of the line...

I don't know. It looks like examples of success in this thread so... What detail am I missing here?!
I poked around looking through all the dialog windows and options I could find. I tried screwing around to clone the hidden vs data volumes separately but that looks wrong (miscommunication) and I could find no way to do it. The only way to select the source and target volumes in CCC seems to be the normal/expected way at the outer level.

I still have CCC v5 licensed on my laptop. I downloaded the demo for v6 on the Mac Pro for this. The 30 day demo has always been full feature in the past and states it's full feature now. I have a slightly older OS 12.2 install. (Ya see, those HDMI cards weren't working with anything. Then I tried the 12.2 installer I had made and that worked! I've just been wary to update that in case these flakey cards don't like it. Probably being silly but...) So anyway, it's the latest version of CCC v6 and MacOS 12.2. I guess I'll try updating MacOS and report back. I can always manually install it again. (What I'm trying to find a cloning app for again!) I'll also try it from my laptop. (I have a 12.5 install) I'll also try it to a USB connected drive instead of an internal. (Ya see, CCC scolded me initially when I tried a USB connected drive because it didn't like my SATA to USB cable apparently. That's when I put another SSD inside to try that way.)

Again again, if this is truly a Rube Goldberg level of instruction where only certain paths through the menus work, I'd appreciate a "step by step for dummies"! Otherwise I'm pretty sure I was following the instructions above. I think I've been using CCC since around 2006 and just never looked back.

 

[serr]

My Macbook Pro running Monterey 12.5 with CCC v6.1.2 gets the very same error.

Not sure what I might be missing or screwing up.
The legacy bootable copy option appears to be the choice to make a full clone including the OS installation.
Posts here including pictures seem to agree.
CCC has a note that pops up about this being a proprietary Apple procedure and all the extra CCC features (filters, etc) are disabled. OK, cool. Hit start and it just fails.
USB connected SSD this time.

 

[serr]

Downloaded SuperDuper to try. It allowed to be installed but it fails too. OK so OS 12 is too new for SuperDuper too. Another strike.

...
Replicating system volume
Volume replication failed - error 49197

 

[Realityck]

My Macbook Pro running Monterey 12.5 with CCC v6.1.2 gets the very same error.

Not sure what I might be missing or screwing up.
The legacy bootable copy option appears to be the choice to make a full clone including the OS installation.
Posts here including pictures seem to agree.
CCC has a note that pops up about this being a proprietary Apple procedure and all the extra CCC features (filters, etc) are disabled. OK, cool. Hit start and it just fails.
USB connected SSD this time.

Look at the video, has the SSD been setup to use APFS, never mind setting up a task this video covers? Never seen what in bold. Your 30 day demo s/b feature complete, not extra CCC features are disabled. Something is amiss.

 

[serr]

Look at the video, has the SSD been setup to use APFS, never mind setting up a task this video covers? Never seen what in bold. Your 30 day demo s/b feature complete, not extra CCC features are disabled. Something is amiss.

APFS yes. With SSDs since High Sierra.
The first APFS choice. No encryption, etc.

Take a look at your screen shot in post #3. The note under "Bootable System clone using Apple's proprietary APFS replicator" is what I was talking about.

Something is amiss alright! The system cloning is truly not functioning here. Not with MacOS 12.2 or 12.5 and not on my Mac Pro or Macbook Pro. CCC v6.1.2 These are new nearly clean installs too! Not some crusty migrated repeatedly since 2007 shenanigans or some such. Tried USB connected SSD for the destination and even tried an internally installed SSD on the Mac Pro (in case the USB connection was the issue).

The dude in the video appears to be using the temporary 'time machine mode'. He just went straight to the standard features and never clicked on the Legacy Bootable Backup Assistant. It's the cloning of the OS install that I need.

Are there suddenly restrictions on drive names or something goofy Windows-esque like that in play?
I've used CCC since around 2006 I think. I always format new drives myself and correctly. I've shuffled OS's around many times and booted up machines with abandon. I feel like I'm following the instructions here. Everything follows the screen shots and comments I see.

 

[flowrider]

I used SuperDuper for awhile and it worked until it didn't. The author and I bickered back and forth for awhile and I finally gave up and tried CCC, I've been using it since. I had an issue with it early on in Monterey, but it was something I was doing wrong. I went back and followed all the steps laid out in this thread, and it's been working fine for me ever since.

I use CCC to make bootable clones. I have four SSDs with OS's Two for Monterey and two for Ventrura. All are bootable, but one is the startup disc and the other is a backup in case of issues with the startup disk.

Lou

 

[0134168]

APFS yes. With SSDs since High Sierra.
The first APFS choice. No encryption, etc.

Take a look at your screen shot in post #3. The note under "Bootable System clone using Apple's proprietary APFS replicator" is what I was talking about.

Something is amiss alright! The system cloning is truly not functioning here. Not with MacOS 12.2 or 12.5 and not on my Mac Pro or Macbook Pro. CCC v6.1.2 These are new nearly clean installs too! Not some crusty migrated repeatedly since 2007 shenanigans or some such. Tried USB connected SSD for the destination and even tried an internally installed SSD on the Mac Pro (in case the USB connection was the issue).

The dude in the video appears to be using the temporary 'time machine mode'. He just went straight to the standard features and never clicked on the Legacy Bootable Backup Assistant. It's the cloning of the OS install that I need.

Are there suddenly restrictions on drive names or something goofy Windows-esque like that in play?
I've used CCC since around 2006 I think. I always format new drives myself and correctly. I've shuffled OS's around many times and booted up machines with abandon. I feel like I'm following the instructions here. Everything follows the screen shots and comments I see.

Just erase completely in APFS in Disk Utility the destination drive.

 

[serr]

Just erase completely in APFS in Disk Utility the destination drive.

Did that every time!

 

[serr]

I used SuperDuper for awhile and it worked until it didn't. The author and I bickered back and forth for awhile and I finally gave up and tried CCC, I've been using it since. I had an issue with it early on in Monterey, but it was something I was doing wrong. I went back and followed all the steps laid out in this thread, and it's been working fine for me ever since.

I use CCC to make bootable clones. I have four SSDs with OS's Two for Monterey and two for Ventrura. All are bootable, but one is the startup disc and the other is a backup in case of issues with the startup disk.

Lou

What specific versions of everything are working for you?

 

[flowrider]

^^^^

CCC V6.1.3-b4 (7401). Monterey V12.6 (21G115). Ventura V13.0 (22A5342f).

Lou

 

[serr]

Is that a beta version of CCC? Where can one download that?

 

[davidlv]

Is that a beta version of CCC? Where can one download that?

Open CCC, check the preferences.
Click on the "Update" pane, put a check mark before the beta option item.
Then run the Check for updates function.

 

[Realityck]

Is that a beta version of CCC? Where can one download that?

GO CCC settings -> Updates-> check box "inform me of beta releases"

Also update to 12.5 at least.

 

[mastermamo]

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.

Brilliant. Worked perfectly between a NVMe and backup SSD.
Once there was just one volume instead of 2 the legacy backup in CC worked like a charm.
Massive thanks !!!

 

[Realityck]

CCC 6.1.3 (7408) is now available

Spoiler: CCC 6.1.3 Fixes and Changes

• Fixed
  The "System exclusion" is no longer applied in cases where the destination is a subfolder on the startup disk.
• Changed
  Fixed an issue in which "on reconnect" tasks were not correctly getting throttled according to the task configuration if the task was also configured to prompt the user to proceed when the missing volume was reconnected.
• Changed
  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.
• 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.
• Changed
  Task groups can now be deleted via the Task menu (e.g. Command+Delete) and via the "Additional Actions" menu in the sidebar.
• Fixed
  Resolved an issue in which a task would appear stalled when converting a disk image to a read-only format. Fixed an unrelated progress indication issue in the same scenario.
• Changed
  Automated tasks will now be skipped any time a restore task is running to remove any possible conflict between a restore task and a backup task. Users are welcome to run backup tasks manually while a restore task is running, this change only affects automated tasks.
• Changed
  Fixed the presentation of a snapshot creation failure in cases where the destination is in the midst of encryption conversion.
• Changed
  The minimum time threshold for "When files are modified on the source" tasks is now 1 minute, but the default is now 5 minutes. The minimum data threshold is now 0; when set to 0, CCC will start an event when changes have been made to a file on the source (and the time threshold is met).
• Changed
  The CCC Dashboard will now proactively open CCC if CCC's helper tool lacks Full Disk Access. Likewise, the Dashboard will open CCC if corruption in CCC's task database has been detected.
• Changed
  CCC now applies a two-week sanity limit on the Quick Update feature. We were finding some cases where macOS managed to have retained multiple weeks of FSEvent records, and it was taking longer to slog through all of those records than it would take to simply re-enumerate the source and destination. So if a Quick Update task hasn't run successfully in the last two weeks, it will now proceed with a full audit of the source and destination.
• New
  Added a new "Settings" column to the task events table in the Task History window that will indicate when the "Quick Update" or "Backup Health Check" settings were applied to a given task event. This column is hidden by default; right-click on the table header row to choose which columns should be visible.
• Changed
  Ventura: Modified the steps for granting Full Disk Access. It's now one step! That's right, just one step! Just start dragging the CCC Privacy Fish and CCC will pull some strings in the background to magically make the full disk access table appear for the drop.
• Changed
  Ventura: Fixed the filesystem identity of ExFAT and FAT32 volumes in the disk chart (i.e. when you click on the Source or Destination selector, or select a volume in CCC's sidebar).
• New
  Ventura: Adopted a new macOS procedure for adding the CCC Dashboard login item.
• Changed
  Ventura: Adjusted how connections to a remote Mac are initiated from a Ventura client to accommodate changes to the scp utility that are specific to macOS Ventura.
• Changed
  Mostly Ventura: Fixed a memory access issue that occurs (with more frequency on Ventura) in the SQLite encryption library that CCC has been using to encrypt task audit and task history databases. After applying this update, CCC will temporarily decrypt the task audit and task history databases, then re-encrypt them with a replacement encryption library. In the unlikely event that an exception occurs while decrypting one of these databases, the affected database will simply be recreated. This change has no effect on task configurations, which are stored in a separate, non-encrypted database, and no effect on any of your data on your backup disk.