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

******* said:
Hope they fix it soon.
Click to expand...
I expect the MacOS 12.3 beta 2 late next week 10th or 11th of Feb. We'll see if its better then. Looking at discussion of SSL (Signed System Volume) this paragraph kinda describes what CCC is doing to make a one time bootable snapshot.

to turn cryptographic verification off, then mount the System volume and perform its modifications. To make that bootable again, you have to bless a new snapshot of the volume using a command such as
sudo bless --folder /[mountpath]/System/Library/CoreServices --bootefi --create-snapshot
Click to expand...
This bug is not allowing the pre-boot or system volumes to be blessed and show up after snapshot. Everything is in a single data volume.
 
  • Like
Reactions: 0134168
The APFS replication with bless utility used by backup applications stopped working with beta 1 and is the same with beta 2.

This bug was already reported to Apple.

It means that three volume bootable snapshot, only shows as Data Volume with everything in it. Yep no preboot or system volumes shown in Disk Utility.
 
  • Like
Reactions: 0134168
******* said:
Maybe it is of interest to you...


#4,788
Click to expand...
APFS replication has been working with Monterey betas until 12.3 betas. But the bless utility is what allows those volumes to be created properly. It’s not as important to have it boot as it is to have everything residing in the current snap shot volume array. But thanks for the feedback.
 
CCC 6.1-b2 now available, the notes below edit out what was already mentioned in the b1 notes
  • Fixed
    Fixed an issue in which CCC was unable to create files and folders in some OneDrive-related folders on the destination.
  • New
    Added an option to reveal the Advanced Settings persistently in the main window.
  • New
    Added a contextual menu to the CCC menubar icon for "quick access" functions (e.g. open CCC, run a task, quit the Dashboard). Right-click on the CCC menubar icon to access this menu.
  • New
    Added navigation buttons to the CCC toolbar to make it easier to get back to a task after making volume configuration changes (e.g. when adjusting snapshot settings).
 
  • Like
Reactions: Weaselboy and 0134168
CCC 6.1 is now available
  • Fixed
    Fixed an issue in which CCC was unable to create files and folders in some OneDrive-related folders on the destination.
  • New
    Added an option to reveal the Advanced Settings persistently in the main window.
  • New
    Added a contextual menu to the CCC menubar icon for "quick access" functions (e.g. open CCC, run a task, quit the Dashboard). Right-click on the CCC menubar icon to access this menu.
  • New
    Added navigation buttons to the CCC toolbar to make it easier to get back to a task after making volume configuration changes (e.g. when adjusting snapshot settings).
  • New
    Added an option for a light background for the sidebar (i.e. in Light Mode).
  • New
    Added settings to choose a specific appearance (i.e. light or dark, independent of the system setting).
  • Changed
    The Source and Destination selectors are now enabled while a task is running. You can click on these to see details about the source and destination (e.g. disk usage, free space) as the task progresses.
  • Changed
    Task History events now show information about how many files and how much data was removed from the destination (in addition to how many files and how much data was copied to the destination).
  • Changed
    Every Mac that is supported by macOS Catalina has native USB 3.0 support, so now CCC's Copy Coach proactively warns when a source or destination is connected via USB 2.0 (e.g. due to using an old USB hub or non-USB 3.0 compliant cable).
  • Changed
    The Dashboard now shows both "last run time" and "next scheduled run time" for each task. Previously this was an option, but presenting both at the same time seems to be what most people are looking for.
  • Changed
    Enhanced the search feature in the CCC Documentation window to offer an option to search the current page for matching text, or to execute a search of the entire CCC Kbase.
  • New
    Task groups can now be specified via the "Run another task" option in Advanced Settings > Postflight.
  • Fixed
    Fixed a minor apparent discrepancy when using the "Verify files copied by this task" feature on a NAS volume. Previously this would show size-based differences due to the absence of extended attributes despite that those were deliberately not copied.
  • New
    Audit records can now be exported to a CSV file.
  • New
    Added a "Copy Link" option to the Tasks contextual menu. These links will open CCC and select the applicable task. These can be useful alongside other Mac automation.
  • Fixed
    Fixed a couple conditions where CCC would report an error and fail to create a symlink becase a folder with the same name already existed on the destination. Fixed a similar issue where CCC was unable to create new folder on the destination because a file (often a symlink) with the same name already existed.
  • Fixed
    Fixed a mouse tracking issue in the CCC Dashboard "mini progress" window that could make it impossible to click on the pause/stop buttons.
  • Changed
    The CCC Dashboard window size and placement is now retained across launches.
  • Changed
    Made a handful of adjustments to how older versions of files are presented in the Snapshot Comparison Browser. Checksums are now calculated on-the-fly for any files smaller than 2MB.
  • Changed
    The System exclusion limit is no longer applied to a subfolder destination when the source OS is Big Sur or later.
  • Changed
    Made some adjustments that should improve performance when using an ExFAT or NTFS volume as a source or destination.
  • Changed
    Made some modest improvements to the "time remaining" estimate. This estimate will now include componesation for time that that will be required for re-verifying files that were copied (if specified for the task).
Please note that latest MacOS 12.3 betas still break the Bless utility part of APFS replication.
 
  • Like
Reactions: kemo and 0134168
CCC 6.1.1-b1 is now available if you have beta downloads enabled.
  • Fixed
    Fixed an exception that was causing tasks to fail with no clear reason when a task was configured with a remote Mac source or destination, and the specification for that remote Mac was missing a "volume name" attribute.
 
Last edited:
  • Like
Reactions: 0134168
Realityck said:
CCC 6.1.1-b1 is now available if you have beta downloads enabled.
  • Fixed
    Fixed an exception that was causing tasks to fail with no clear reason when a task was configured with a remote Mac source or destination, and the specification for that remote Mac was missing a "volume name" attribute.
Click to expand...
Did you try the RC?
 
Based on reports from others (reporting success when cloning an m-series Mac with CCC), I tried creating a bootable backup on an old drive -- and failed.

My hardware:
2021 MacBook Pro 14" (base model).
OS 12.2

The target drive is an OLD 40-pin platter based drive (P-SATA or IDE?), in a Rosewill 40-pin to USB2 case.

The drive mounts and erases to APFS without problems.
I ran CCC using the "Legacy" option.
The clone takes a while, but completed successfully (as reported by CCC).

I then shut down and re-booted to "startup options", and the backup drive shows as bootable in the choice of startup drives.

However... the boot will begin... and then eventually "stall"...and then... it suddenly "finishes up", but to the INTERNAL drive, and presents a "your computer was restarted because of a problem" alert.

I also tried starting the process from scratch, this time using SuperDuper instead -- and the results are the same.

The "Data" portion of the clone gets done as intended.
But the drive won't successfully boot.

I'm thinking that this might be due to one or more factors:
- old 40-pin parallel ATA type hard drive
- controller on the drive
- controller in the Rosewill enclosure
- a combination of the above, or something else.

Guess I'll have to try either an SSD or a SATA-based drive.
Perhaps the new OS's can't handle older drive technology...
 
Fishrrman said:
Based on reports from others (reporting success when cloning an m-series Mac with CCC), I tried creating a bootable backup on an old drive -- and failed.

My hardware:
2021 MacBook Pro 14" (base model).
OS 12.2

The target drive is an OLD 40-pin platter based drive (P-SATA or IDE?), in a Rosewill 40-pin to USB2 case.

The drive mounts and erases to APFS without problems.
I ran CCC using the "Legacy" option.
The clone takes a while, but completed successfully (as reported by CCC).

I then shut down and re-booted to "startup options", and the backup drive shows as bootable in the choice of startup drives.

However... the boot will begin... and then eventually "stall"...and then... it suddenly "finishes up", but to the INTERNAL drive, and presents a "your computer was restarted because of a problem" alert.

I also tried starting the process from scratch, this time using SuperDuper instead -- and the results are the same.

The "Data" portion of the clone gets done as intended.
But the drive won't successfully boot.

I'm thinking that this might be due to one or more factors:
- old 40-pin parallel ATA type hard drive
- controller on the drive
- controller in the Rosewill enclosure
- a combination of the above, or something else.

Guess I'll have to try either an SSD or a SATA-based drive.
Perhaps the new OS's can't handle older drive technology...
Click to expand...
That was on the Monterey RC?
 
"That was on the Monterey RC?"

It was the version that came with the MacBook Pro 14".
Not a beta version.
 
******* said:
That was on the Monterey RC?
Click to expand...
I didn't see any fix for the Bless Utility portion of APFS replication with MacOS 12.3 RC. For now that is broken since the last OS it worked which is MacOS 12.2.

IF you make a backup snapshot using the Legacy Bootable Backup Assistant you will end up with one volume named "Data" with the system, pre-boot, and data all together.

For now if you have a MacOS 12.2 snapshot that you are incrementally backup on occasion, just use that, don't try the erase, make a new one time bootable snapshot using CCC with MacOS 12.3.
 
  • Like
Reactions: 0134168
Bombich Software has the following statements on their web pages

Creating legacy bootable copies of macOS (Big Sur and later)
Copying Apple's system is now an Apple-proprietary endeavor; we can only offer "best effort" support for making an external bootable device on macOS Big Sur (and later OSes). We present this functionality in support of making ad hoc bootable copies of the system that you will use immediately (e.g. when migrating to a different disk, or for testing purposes), but we do not support nor recommend making bootable copies of the system as part of a backup strategy. Please bear in mind that you can restore all of your documents, applications, and system settings from a standard CCC backup without the extra effort involved in establishing and maintaining a bootable device.
Click to expand...

If I continue to make regular backups to the destination, will it remain bootable?
You should not expect the destination to remain bootable after running additional backup tasks to the destination (i.e. via manual or scheduled backups). The Legacy Bootable Copy Assistant is intended only for creating ad hoc, bootable copies of the system that you intend to use immediately.
Click to expand...

As you can see Apple keeps changing how much of a backup they permit. This might change with future version of the MacOS 12, and then MacOS 13. Its something that is still usable if something happens, but not necessarily bootable like we been able to make up to now.
 
  • Like
Reactions: 0134168
Realityck said:
Bombich Software has the following statements on their web pages

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


If I continue to make regular backups to the destination, will it remain bootable?


As you can see Apple keeps changing how much of a backup they permit. This might change with future version of the MacOS 12, and then MacOS 13. Its something that is still usable if something happens, but not necessarily bootable like we been able to make up to now.
Click to expand...
:-(
 
Realityck said:
I didn't see any fix for the Bless Utility portion of APFS replication with MacOS 12.3 RC. For now that is broken since the last OS it worked which is MacOS 12.2.

IF you make a backup snapshot using the Legacy Bootable Backup Assistant you will end up with one volume named "Data" with the system, pre-boot, and data all together.

For now if you have a MacOS 12.2 snapshot that you are incrementally backup on occasion, just use that, don't try the erase, make a new one time bootable snapshot using CCC with MacOS 12.3.
Click to expand...
Not. Always erased the drive prior to backup.But I can tell you that I will not update to 12.3 till this stuff is clear to me. I use to make experiments and changes, and boot clones for restore are a must for me.
 
why not use SuperDuper? I think v3.6.1 is fully bootable with Big Sur and Monterey according to shirt-pocket.com.
 
drewaz said:
why not use SuperDuper? I think v3.6.1 is fully bootable with Big Sur and Monterey according to shirt-pocket.com.
Click to expand...
Because I have a good history of responses from the developer when reporting any bugs along along with his recent modernization of the CCC software. In the short term I think this will be fixed soon, just as the other dev has announced a workaround. Thanks for pointing that out with the blog 3/13 update.
 
Last edited:
no worries. I'm a casual user and not very tech savvy. I've used SD for years and it sounds like 3.6.1 works for 12.3 and with intel and Apple silicon so ... I was just trying to learn something.
 
drewaz said:
why not use SuperDuper? I think v3.6.1 is fully bootable with Big Sur and Monterey according to shirt-pocket.com.
Click to expand...
I own both. My dealings with Shirt Pocket has been less than stellar. But, if SD now works, I will use it.

Lou
 
drewaz said:
no worries. I'm a casual user and not very tech savvy. I've used SD for years and it sounds like 3.6.1 works for 12.3 and with intel and Apple silicon so ... I was just trying to learn something.
Click to expand...
This is par for the course as Apple changes the way APFS security with Apple Replication utility. Every time they add additional permissions they can break either product. In a day or two I will be seeing MacOS 12.4 beta then off we go again maybe. :D
 
Realityck said:
This is par for the course as Apple changes the way APFS security with Apple Replication utility. Every time they add additional permissions they can break either product. In a day or two I will be seeing MacOS 12.4 beta then off we go again maybe. :D
Click to expand...
:rolleyes:
 
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