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 7 - Users Thread
- Thread starter Realityck
- Start date
- Sort by reaction score
see also
CCC 6.1.8 (7612) is now available
Fixed
Fixed
- Build 7612: This build removes a preflight check added to 6.1.8 that was causing more trouble than anticipated. If you had a task with an empty folder as the source, or the source folder only contained files and no additional folders, apply this new build of CCC 6.1.8 to resolve any failures of those tasks.
I'm willing to update anything, but I do not fully understand your explanation.
How can the source of my backup be an empty directory,
how can I NOT have a directory with only files?
And what did any error message look like?
;JOOP!
How can the source of my backup be an empty directory,
how can I NOT have a directory with only files?
And what did any error message look like?
;JOOP!
CCC 6.1.9-b1 (7616) is now available — This is a pre-release update of CCC 6.1.8 (7612)
- New
We're kicking the tires on a new feature that deals with renamed folders by renaming them on the destination rather than recopying them. This behavior is only applied when the source and destination are APFS formatted. - Changed
When a task is configured to temporarily download cloud-only files to make a local backup, we now make a more effective attempt at populating any "dataless" folders on the source before enumerating them. - Changed
Fixed a couple minor Voiceover issues relating to the volume attribute buttons that appear when a volume is selected in CCC's sidebar. These buttons reveal a popover, but Voiceover was failing to consistently read the content of those popovers. We also added a transparent dismissal button to that popover to make it more easily-dismissible via the Voiceover Control+Option+Space keystroke.
Is there a suggested guide for using CCC or TM backups with Sonoma when OCLP is in play?
I'm specifically wanting to migrate my apps and data from a 2011 iMac to a 2013 MacPro. Both are running OCLP 1.2.1 and Sonoma v14.1.1. Can Migration Assistant be used after a fresh Sonoma install, or must I setup the user and then manually drag items from the backup to the newly setup machine?
Incase it matters I used a trial version of CCC (v6.1.8) on the iMac to backup to an external SSD's APFS partition, then moved that over to the MacPro to restore.
I'm specifically wanting to migrate my apps and data from a 2011 iMac to a 2013 MacPro. Both are running OCLP 1.2.1 and Sonoma v14.1.1. Can Migration Assistant be used after a fresh Sonoma install, or must I setup the user and then manually drag items from the backup to the newly setup machine?
Incase it matters I used a trial version of CCC (v6.1.8) on the iMac to backup to an external SSD's APFS partition, then moved that over to the MacPro to restore.
Last edited:
I found these instructions/Spoiler at:
https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/
Perhaps I did not fully understand it, and will try again. Does the same apply for CCC (i.e. step 1; unpatch before creating the backup)?
https://forums.macrumors.com/threads/macos-14-sonoma-on-unsupported-macs-thread.2391630/
Bad news:
TM (time machine) restoring and MA (migration assistant) is broken on root patched systems. Do not try, system will only arrive in an unbootable and uncorrectable state after hours of restoring or transferring data.
There are two ways around this:
1. Use the OCLP USB installer and install Sonoma on top of your current (supported or unsupported) macOS. This will retain your current user data. But create a final TM backup before leaving your supported macOS installation, it will be the only return ticket.
2. Simply use MA or TM before system has been root patched by the OCLP app. This is sometimes difficult to achieve when auto-patching ran before you even reached the login page. You can prevent auto-patching by creating an USB installer manually (createinstallmedia and install OpenCore manually). You can revert patches, too.
TM (time machine) restoring and MA (migration assistant) is broken on root patched systems. Do not try, system will only arrive in an unbootable and uncorrectable state after hours of restoring or transferring data.
There are two ways around this:
1. Use the OCLP USB installer and install Sonoma on top of your current (supported or unsupported) macOS. This will retain your current user data. But create a final TM backup before leaving your supported macOS installation, it will be the only return ticket.
2. Simply use MA or TM before system has been root patched by the OCLP app. This is sometimes difficult to achieve when auto-patching ran before you even reached the login page. You can prevent auto-patching by creating an USB installer manually (createinstallmedia and install OpenCore manually). You can revert patches, too.
Perhaps I did not fully understand it, and will try again. Does the same apply for CCC (i.e. step 1; unpatch before creating the backup)?
Don't overthink it. CCC will copy everything that is necessary (with or without it being a disk that has OCLP running.
After the backup is complete, disconnect that drive and proceed with the new OS install. At the end of the install, there is a place where you will be promptd to use another Mac to import your data. At that time connect the CCC backup disk and specify it as the source for the data transfer. After a few minutes you will have a completed back up!
Last edited:
Agreed. It seems less an issue with CCC, for that does indeed backup everything quite quickly. The trick seems to be to backup and restore the backup before OCLP does the post patching. What I had missed was that that appears to be done automatically after the OS installs and prior to Migration Assistant running during setup.
Had I understood what the OCLP site's warning was stating I could have avoided considerable frustration. It looks like you have to complete the install on the target, then unpatch it and restart before running Migration Assistance. I assumed (incorrectly) that it was not auto-patching until setup was complete. Seems that is NOT the case, which upon re-reading their warning that is what it seems to state:
https://dortania.github.io/OpenCore-Legacy-Patcher/POST-INSTALL.html#enabling-sip
Dear sir: you are absolutely right. The same happens with Migration Assistant. I have reverted the root patches, and now CCC is making a boot legacy clone of Sonoma OCLP. When made, i will try to boot from that clone and reapply the root patches. Will report later.
Attachments
Why can't you boot from the internal disk and apply the root patches? I don't think your present plan will work as intended. If I understand it correctly, the root patches should be applied to the boot disk, and booting from a CCC legacy clone would likely prevent the application of the root patches to the disk intended.
I have had success several times using CCC to make a regular backup task copy to a target disk (for example an external SSD) and then boot from a USB OS installer disk. and run the OS install to that same target disk. In that case, if the root patches are run automatically it doesn't matter as the use of the Migration Assistance utility is not involved in the install.
I think you don´t understand the proccess. Made it several time to use Migration Assistant. You don´t need root patches to boot, although OCLP now install them for you in a clean installation. Of course, I´m talking about my model, Mac Pro 5,1, I don´t know in other models if it´s possible. Root patches for 5,1 just install patches for wifi, Polaris graphics ans USB 1.1
It doesn't work for me either. Even with I carefully unpatched before backing up, and then restored that with Migration Assistant. There must be something I'm missing. I guess I will try a Time Machine backup next to see if I have any better luck. With the amount of time I've wasted on this, I could have reinstalled the apps, and copied over the data manually.
Clone made succesfully. Then I restarted from original drive to apply root patches again. An then I restarted from the clone. Succesfully, I suspected. Reapply root patches to clone. Everything worked like a charm.
well, I have done it with Migration Assistant the way i explained a lot of times. And in a few munutes I will told the results of boot cloning. Meanwhile...
Attachments
Last edited:
All worked perfect. I have a bootable clone of OCLP Sonoma, root patched. Thanks, @BadBiscuit , for recalling me about the problems with root patched systems.
Attachments
Last edited:
Considering the numerous times I have used CCC along with OCLP, and the fact that it has always worked, I agree there must be something you are doing different.
Sure you are selecting a "New Backup Task" in the Task menu in CCC?
Have you carefully looked at the "Task Filter" options? (See the attached screen shot as an example)
I have never reverted or unpatched the source disk before making a backup, and never seen a related bad result either.
Of course, the hardware we are using is widely different, and that may well be involved here. In all, your situation is a mystery to me. I hope you manage to get everything sorted!
Attachments
I'm fairly sure it is the auto-patching feature of OCLP's newer versions that is my issue, not anything to do with CCC. It is my understanding that if any OCLP patches are in place, then even though Migration Assistant will see and appear to use the backup, it will fail to transfer the data in a usable manner (i.e. no error, just missing upon migration completion and reboot). Perhaps a future version of OCLP will have a clear way to disable auto-patching, for when I attempt it using the current version's GUI I'm not convinced it is staying unpatched. I believe auto-patching was added for some systems would crash during install before the user had a chance to patch manually, resulting in a boot loop. I never had that issue, so it would be nice to disable (and perhaps there is a way I just didn't find).
Perhaps, @******* 's success, is because an older version of OCLP is in use. The screenshots indicate the latest is not being run, and it is notifying for the need to manually patch (as it use too). Latest version no longer prompts for it just does the patching. Unfortunately I believe the newest version of OCLP is required on my system in order for Sonoma 14.1+ to boot and function correctly. Otherwise I would try an older version before the auto-patching "feature" was added.
Regardless, thanks for your advice. I think I will just load apps and data over manually at this point, for I suspect that may be for the best anyway. I'll keep an eye on future OCLP versions to see if improvements for migration are added, and retry then.
NO, sir. I use 1.2.1., the last one. I have asked several times to the OCLP an option to not auto install root patches.
It´s simple. You make a clean OCLP install. When done, revert the root patches. Boot without the root patches and then use Migration Assistant from the Utilities folder.
That easy.
I have done this a lot of times, with a lot of versions of OCLP, including the last one.
The screenshot you mention is just to recall you to install again the root patches. It´s an automatic prompt since last versions of OCLP.
Anyway, I prefere a bootable clone made with CCC. In case of any problem, I can simply boot from it and clone again to main drive. Migration Assistan is so much slower.
Last edited:
Thanks for writing up your workflow to create a bootable CCC clone.
CCC 6.1.9-b2 (7626) is now available — This is a pre-release update of CCC 6.1.8 (7612)
Specifically this update is fixing a errant trial expiration issue that eventually affects Pro License users that are using a license sidecar file
- Changed
Fixed an errant trial expiration issue that eventually affects Pro License users that are using a license sidecar file. - New
We're kicking the tires on a new feature that deals with renamed folders by renaming them on the destination rather than recopying them. This behavior is only applied when the source and destination are APFS formatted. - Changed
Implemented a more effective solution for retrieving folder lists for cloud-synced folders that were added via the web or via another Mac. - Changed
Fixed a couple minor Voiceover issues relating to the volume attribute buttons that appear when a volume is selected in CCC's sidebar. These buttons reveal a popover, but Voiceover was failing to consistently read the content of those popovers. We also added a transparent dismissal button to that popover to make it more easily-dismissible via the Voiceover Control+Option+Space keystroke.
Specifically this update is fixing a errant trial expiration issue that eventually affects Pro License users that are using a license sidecar file
From my understanding of CCC, OCLP (not OLCP) and the boot process (I have not tested this):
In the sense of backing up the file system (Time Machine equivalent): Yes. Though you should test your disaster recovery procedures which will involve reinstating OCLP on the system/boot disk before running Migration Assistant (or however you choose to restore the file system).
In the sense of a bootable clone: No - not out of the box. You would need to take further steps to install all of OCLP on the clone drive. In particular, the EFI partition would need to be recreated or copied onto the NVMe drive. You might want to ask about this on OCLP threads.