Carbon Copy Cloner 7 - Users Thread

[Realityck]

CCC 7.0.2 (8045) is now available — This is a update of CCC 7.0.1 (8016)

Spoiler: CCC 7.0.2 Fixes and Changes

• Changed
  Addressed a scrolling performance issue in the "Verify files copied by this task" window that could occur when selecting multiple files.
• Changed
  Corrected the appearance of the Notes text in Dark Mode.
• Changed
  The Task Filter, Advanced Settings, and Notes icons at the bottom of the CCC window now use a badge to indicate that customizations are applied rather than relying on color alone.
• Changed
  UUID resetting is now disabled for ExFAT volumes because the exfat.util resets the UUID to all zeroes (bug filed with Apple: FB13813658).
• Changed
  When a postflight power management setting is selected that involves presenting the system's 60 second countdown dialog, CCC now wakes the screen before making the request so that this dialog is presented more consistently.
• Changed
  Fix a "missing character" font issue for a message in the Task Plan for tasks that are configured to run "When files are modified on the source".
• Fixed
  Fixed an issue where the "Delete snapshots that are older than {}" and "Limit snapshot disk usage to {}" values were getting swapped in the Snapshot Retention Policy table.
• Fixed
  "At rest" encrypted volumes (i.e. the internal storage in an Apple Silicon Mac, or an Intel Mac with a T2 chip) are no longer presented as "Encrypted" in the Disk Center unless FileVault is explicitly enabled with a password.
• Changed
  When you select a volume in CCC's sidebar and enable encryption on that volume, CCC no longer saves the user-specified password in the System keychain. The prompt for password retention is deliberately limited to cases where an encrypted volume is selected as a source or destination to a CCC task.

Works fine with MacOS 15.1 beta

 

[Realityck]

CCC 7.0.2 (8048) released now. Replaces yesterday's CCC 7.0.2 (8045) release.

Fixed
Build 8048 addresses a crashing issue that was introduced in 7.0.2 that could occur on Macs that lack a WiFi interface.

Spoiler: CCC 7.0.2 Fixes and Changes

• Fixed
  Build 8048 addresses a crashing issue that was introduced in 7.0.2 that could occur on Macs that lack a WiFi interface.
• Changed
  Addressed a scrolling performance issue in the "Verify files copied by this task" window that could occur when selecting multiple files.
• Changed
  Corrected the appearance of the Notes text in Dark Mode.
• Changed
  The Task Filter, Advanced Settings, and Notes icons at the bottom of the CCC window now use a badge to indicate that customizations are applied rather than relying on color alone.
• Changed
  UUID resetting is now disabled for ExFAT volumes because the exfat.util resets the UUID to all zeroes (bug filed with Apple: FB13813658).
• Changed
  When a postflight power management setting is selected that involves presenting the system's 60 second countdown dialog, CCC now wakes the screen before making the request so that this dialog is presented more consistently.
• Changed
  Fix a "missing character" font issue for a message in the Task Plan for tasks that are configured to run "When files are modified on the source".
• Fixed
  Fixed an issue where the "Delete snapshots that are older than {}" and "Limit snapshot disk usage to {}" values were getting swapped in the Snapshot Retention Policy table.
• Fixed
  "At rest" encrypted volumes (i.e. the internal storage in an Apple Silicon Mac, or an Intel Mac with a T2 chip) are no longer presented as "Encrypted" in the Disk Center unless FileVault is explicitly enabled with a password.
• Changed
  When you select a volume in CCC's sidebar and enable encryption on that volume, CCC no longer saves the user-specified password in the System keychain. The prompt for password retention is deliberately limited to cases where an encrypted volume is selected as a source or destination to a CCC task.

Thats an interesting bug caught. You see this update when checking. Didn't occur with Wifi just turned off for me.

 

[RK78]

(Already asked here https://forums.macrumors.com/threads/macos-13-ventura-on-unsupported-macs-thread.2346881/page-331, but thinking now that this forum is likely to be more appropriate)


Some help needed: still running HDDs on Late '09 21.5" iMac and Mini Mid-2010 4,1. Thinking that it's about time to replace these ancient platter drives with SSDs.

Current setup/configuration is High Sierra with Ventura OCLP on separate partition. For ease of use and various other reasons, would like to keeps things as is. HS (HFS+) is backed up with CCC5 bootable clone, while the Ventura (APFS) has CCC6 clone, but not currently configured as bootable. Hoping it won't be necessary, but if needed still have original OCLP installers for both Macs.

Bottom line question: what would be the best way to reinstall both the HS and the Ventura on separate partitions in order to duplicate current setup with new SSD drives?

Also would welcome recommendations for SSDs for Mini and iMac.

Appreciate any suggestions/help.

 

[Sciuriware]

(Already asked here https://forums.macrumors.com/threads/macos-13-ventura-on-unsupported-macs-thread.2346881/page-331, but thinking now that this forum is likely to be more appropriate)


Some help needed: still running HDDs on Late '09 21.5" iMac and Mini Mid-2010 4,1. Thinking that it's about time to replace these ancient platter drives with SSDs.

Current setup/configuration is High Sierra with Ventura OCLP on separate partition. For ease of use and various other reasons, would like to keeps things as is. HS (HFS+) is backed up with CCC5 bootable clone, while the Ventura (APFS) has CCC6 clone, but not currently configured as bootable. Hoping it won't be necessary, but if needed still have original OCLP installers for both Macs.

Bottom line question: what would be the best way to reinstall both the HS and the Ventura on separate partitions in order to duplicate current setup with new SSD drives?

Also would welcome recommendations for SSDs for Mini and iMac.

Appreciate any suggestions/help.

As I do not create bootable volumes (I'm content with OS restore and backup restore) I stick to my cheaper
HDD's for backup. For non-professional users a (slow?) backup is never a problem: it may run during dinner.
Then again, replacing HDD's by SSD's is never going to speed up by a factor 2, although a bare SSD is 2x faster:
too many components in the copying process will be bottlenecks.
I think that the fact that you are making regular backups to rotating sets of disks is the most important factor.
;JOOP!

 

[Realityck]

Then again, replacing HDD's by SSD's is never going to speed up by a factor 2, although a bare SSD is 2x faster:
too many components in the copying process will be bottlenecks.

SDD's (Samsung T7) normally backup over USB-C 3.1 ~5 Gb port at about 550 Mb/s, where as a HDD is usually 120 Mb/s. Thats better then x4 faster. If Macs used USB-C 3.2 ports ~ 10 gb it would be approx 1 Gb/s. Using more expensive external Thunderbolt 3/4 NVMe enclosure For M.2 NVMe SSD Drive could go easily 3 Gb/s.

 

[RK78]

SDD's (Samsung T7) normally backup over USB-C 3.1 ~5 Gb port at about 550 Mb/s, where as a HDD is usually 120 Mb/s. Thats better then x4 faster. If Macs used USB-C 3.2 ports ~ 10 gb it would be approx 1 Gb/s. Using more expensive external Thunderbolt 3/4 NVMe enclosure For M.2 NVMe SSD Drive could go easily 3 Gb/s.

That's certainly my understanding. Besides the increased speed in general with SSDs, APFS (employed for the Ventura OCLP) presents difficulties for platter drives, which further reduces speed and may increase wear. And, no small matter, the HDD in the 21.5" Late '09 iMac is 14 years old, and can't last forever.

But back to square one, given the info in my first post, can you, or anyone else, suggest a way to move everything, the High Sierra and the Ventura OCLP, over to a new SSD, keeping things as is.

Thanks in advance for any forthcoming help.

 

[0134168]

But back to square one, given the info in my first post, can you, or anyone else, suggest a way to move everything, the High Sierra and the Ventura OCLP, over to a new SSD, keeping things as is.

Clonezilla.

 

[RK78]

Clonezilla.

Looks interesting. Have taken a cursory look at the Wiki https://www.wikihow.com/Use-Clonezilla. But unsure how or if it can deal with things on two different external drives, the High Sierra internal HFS+, and the Ventura OCLP APFS, not in bootable form (or do I have to put that in CCC Legacy Bootable format?) if it's even possible for Clonezilla to work with two different external volumes as source?

Do you have direct, personal experience with CloneZilla for such purpose, including with an OCLP volume?

 

[0134168]

Looks interesting. Have taken a cursory look at the Wiki https://www.wikihow.com/Use-Clonezilla. But unsure how or if it can deal with things on two different external drives, the High Sierra internal HFS+, and the Ventura OCLP APFS, not in bootable form (or do I have to put that in CCC Legacy Bootable format?) if it's even possible for Clonezilla to work with two different external volumes as source?

Do you have direct, personal experience with CloneZilla for such purpose, including with an OCLP volume?

Using it since day one, in the late 2000´s , I think. Simply, make perfect clones, cluster by cluster, not copying software. Specially appreciated when a hard drive contains various partitions, OS, etc. For instance, if you have Bootcamp installed together macos.

Just only one advice.

Although it´s possible to make a clone to an smaller drive, I don´t recommend you to. Use always a drive at least the size on the original.

I even use it in a Parallels virtual machine, connecting both drives by USB. Works like a charm.

 

[RK78]

My tentative plan, wondering what you think:

Instead of trying to use the High Sierra clone, HFS+ (from CCC5) on an external, and the Ventura OCLP Legacy Bootable clone APFS (CCC6) on a different external volume as source (don't even know if Clonezilla can deal with 2 different external volumes as source), once the original drive is out of the Mac, and the new SSD is in place, I would mount that original drive in an enclosure to use as the single source (everything there in one place) - connected by USB.

Would place the Clonezilla on USB flash drive, and then follow the procedure as outlined in https://www.wikihow.com/Use-Clonezilla in beginner mode.

The new SSD will be at least twice as large as the original 500GB HDD.

 

[0134168]

My tentative plan, wondering what you think:

Instead of trying to use the High Sierra clone, HFS+ (from CCC5) on an external, and the Ventura OCLP Legacy Bootable clone APFS (CCC6) on a different external volume as source (don't even know if Clonezilla can deal with 2 different external volumes as source), once the original drive is out of the Mac, and the new SSD is in place, I would mount that original drive in an enclosure to use as the single source (everything there in one place) - connected by USB.

Would place the Clonezilla on USB flash drive, and then follow the procedure as outlined in https://www.wikihow.com/Use-Clonezilla in beginner mode.

The new SSD will be at least twice as large as the original 500GB HDD.

Clonezilla just make clones.

 

[RK78]

Clonezilla just make clones.

EDITED:

Right, looks like I was missing the restore from clone step. From the wiki linked above Part 3 Restoring a Drive.

 

[RK78]

Clonezilla just make clones.

Appears to be a rather complicated procedure, more so since my source involves 3 different OSs with different file systems each on its own partition. Not something to attempt without help from someone with experience with Clonezilla. Without further help, which at this point doesn't look likely think I will probably have to give up on this approach.

 

[0134168]

I gav

Appears to be a rather complicated procedure, more so since my source involves 3 different OSs with different file systems each on its own partition. Not something to attempt without help from someone with experience with Clonezilla. Without further help, which at this point doesn't look likely think I will probably have to give up on this approach.

I gave you al the help needed. And I say it again. Clonezilla just make clones. A perfect clone of a drive. That´s all. If more that one drive is involved as source, it´s not a clone. That simple.

 

[RK78]

I gav

I gave you al the help needed. And I say it again. Clonezilla just make clones. A perfect clone of a drive. That´s all. If more that one drive is involved as source, it´s not a clone. That simple.

Definitely NOT all the help needed.

-Only drive involved to clone is the current internal - just one drive. Can Clonezilla make a perfect clone of the internal, which contains 3 different OSs on 3 partitions: High Sierra HFS+, Catalina 10.15.7 APFS (dosdude1) and Ventura OCLP APFS. NOT 3 different drives.

EDIT:
Can the clone destination be an empty volume on an external, well large enough for the contents of the full drive? But will doing so erase everything else on that external, other volumes, which I absolutely must keep?

-Also once the clone is made is this the proper way to use that clone to install to the new, empty SSD?

Please see

Part 3
Restoring a Drive

How to Use Clonezilla: Complete Guide

Make an exact copy of your hard drive with free open source softwareClonezilla is a cross-platform, open source hard drive cloning software program. It's used to make exact an exact copy of a bootable hard drive. In order to use this...

www.wikihow.com

 

[0134168]

My god, really can´t believe this. It´s a CLONE. The same exactly as the source drive, cluster by cluster. I told you in the first aswer. I also told you you can use USB, that is, external drives. Why do you ask that again??
Its a CLONE. Just boot from it. Why restoring????
NEVER use the Device-Image. That´s NOT a clone. Always Device-Device - work directly from a disk or partition to a disk or partition.

Why simply don´t you try? The destination is a blank drive, you are not gonna lose anything.

 

[RK78]

I appreciate the help, but you are very fast with your replies, and I want to be sure we are talking about the same thing.

Then according to what you say zero problem making a clone of the entire drive which contains three different partitions/volumes with different file systems.

One more thing needing clarification: I want to make the initial clone to an external with an empty 415GB volume, but that external also contains 3 CCC backups/clones on different volumes, which I would not want to risk losing.

Do you know if I can make the initial clone to that empty 415GB volume without fear of losing everything else on that external? Just need to be certain that the entire drive will not be erased when I choose the 414GB empty as the destination.

 

[Realityck]

I appreciate the help, but you are very fast with your replies, and I want to be sure we are talking about the same thing.

Then according to what you say zero problem making a clone of the entire drive which contains three different partitions/volumes with different file systems.

One more thing needing clarification: I want to make the initial clone to an external with an empty 415GB volume, but that external also contains 3 CCC backups/clones on different volumes, which I would not want to risk losing.

Do you know if I can make the initial clone to that empty 415GB volume without fear of losing everything else on that external? Just need to be certain that the entire drive will not be erased when I choose the 414GB empty as the destination.

Please stop this unrelated to topic conversation now as I wanted it to have some closure and it has by *******’s advice, so now return to the topic of CCC 6/7 usage and news.

So far the current CCC 7.0.2 seems to be working with the latest betas of 15.0 and 15.1.

 

[RK78]

Please stop this unrelated to topic conversation now as I wanted it to have some closure and it has by *******’s advice, so now return to the topic of CCC 6/7 usage and news.

Can you please let ******* reply to my final question.

 

[Realityck]

Can you please let ******* reply to my final question.

It's his option, for closure.

 

[0134168]

Please stop this unrelated to topic conversation now as I wanted it to have some closure and it has by *******’s advice, so now return to the topic of CCC 6/7 usage and news.

So far the current CCC 7.0.2 seems to be working with the latest betas of 15.0 and 15.1.

Apologize, dear sir. 😶

 

[Sciuriware]

Apologize, dear sir. 😶

Why not start a new thread; the complex cloning seems a very interesting subject by its own.
;JOOP!

 

[Realityck]

Aug 27th article from CCC's developer Mike Bombich, fairly lengthy read with illustrations.

File Copying Olympics: How File Size Impacts the Race for Performance Gold - Bombich Software

bombich.com

I had the opportunity to evaluate the new U34 Bolt from Oyen, and I was only disappointed that this device doesn't literally scream or burn a hole through the desk. While delivering a stunning 3.1GB/s of sustained throughput, it was completely silent and no warmer than a cup of coffee (120°F/49°C). As exciting as that was, though, I thought this would be a good opportunity to explore why we don't always see peak performance from a storage device.

Interface performance vs. device performance vs. filesystem performance vs. software performance​

Perhaps once a month we'll get a comment, "Black Magic Speed Test shows XX MB/s, but the backup only gets YY MB/s. What gives?". Less frequently people will wonder how to find that 40Gb/s performance that Thunderbolt boasts. First, let's address the math that may not be obvious. "Gb/s" is not the same as "GB/s"; Gb/s is "Gigabits per second", GB/s is "Gigabytes per second". There are 8 bits in a byte, so 40Gb/s is comparable to 5GB/s. But, interface performance isn't...

That linked USB4 device is a 4TB USB4 (40Gbps) NVMe Thunderbolt 4 (USB-C) Portable SSD for only $459 USD.

It address's that old question of "Should I spend the extra money to have a really fast backup disk?"

 

[RK78]

Why not start a new thread; the complex cloning seems a very interesting subject by its own.
;JOOP!

Would be a fantastic idea to have a thread dedicated just to Clonezilla, except if it would be authored and mostly supported by the poster in question, who is not the most generous with his help. Good at offering initial suggestions, but with little patience, and often balking at offering needed followup, especially with a complex topic such as Clonezilla with a quite complicated user interface. I was very tempted to use Clonezilla, but now probably won't.

Or to be more forgiving, maybe not a question of generosity, perhaps ******* has trouble articulating what he knows so well from years of experience, coupled with difficulty understanding the perspective of someone with no experience.

I'm done here with this.

 

[Fishrrman]

RK78 --
Check your "conversations".