Q1:
Q2: Yes, those steps use the latest snapshot. To use a different snapshot, select it and click on the "restore..." button which appears next to the snapshot.
Last edited:
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
Q2: Yes, those steps use the latest snapshot. To use a different snapshot, select it and click on the "restore..." button which appears next to the snapshot.
A standard backup to a external SSD qualifies as a ASR volume for restoring system prefs/Applications/files using Migration Assistant to get you back fully after reinstalling the MacOS or doing a factory complete wipe/reinstall MacOS & system FW (DFU restore).
CCC said, before a backup, it first takes a snapshot. A Snapshot will not be deleted, however, the backup will be updated by the next backup. So there is always ONE and only one latest backup and many snapshots on the CCC backup drive. Yes?
This backup is what you called a standard backup, yes?
Yes, there can only be one latest backup. All, including the latest, are snapshots.
The CCC documentation uses the term "standard backup" to distinguish the current supported backup method from a "legacy bootable backup". So it refers to a backup method, not a particular snapshot.
Use the CCC Knowledge Base (from Help Menu) and search for "standard backup".
Last edited:
gilby posted in reply 698 above:
"On the CCC destination volume, all backups are snapshots. All snapshots are equally complete backups. They are only distinguished by date and time. None of them are more "standard" than any other."
Is that still the case if the user TURNS OFF "snapshots" in CCC's preferences?
(I do)
"On the CCC destination volume, all backups are snapshots. All snapshots are equally complete backups. They are only distinguished by date and time. None of them are more "standard" than any other."
Is that still the case if the user TURNS OFF "snapshots" in CCC's preferences?
(I do)
Just wondering what the reason is you don’t like snapshots. CCC snapshots saved me many times.
"Just wondering what the reason is you don’t like snapshot"
The ONLY stuff I want on my CCC backup, is "a clone" of what was on the source drive at the moment I last backed up. Nothing else. Like "it used to be".
I guess that's ... just me.
The ONLY stuff I want on my CCC backup, is "a clone" of what was on the source drive at the moment I last backed up. Nothing else. Like "it used to be".
I guess that's ... just me.
We still have that hardware error during finalization of legacy snapshot backup with AS Macs to an external SSD to contend with 15.2 beta cycle, beta4 still exhibit that problem with APFS replication utility. The dev is well aware of it and waiting for Apple to remediate in the RC or we see it happen with 15.3 beta when it shows up. Workaround is still just do a standard backup.
Its simply the process of using the APFS replicator utility to copy all 4 volumes related to a bootable snapshot. This however with Apple changes to macOS security to lock things down against external bootable SSD has been less successful endeavor in recent years.
Standard backups
Thank you so much for taking the time to explain issues that are common knowledge for many ! I sincerely appreciate your time and effort! Now I could follow the discussions.
Its simply the process of using the APFS replicator utility to copy all 4 volumes related to a bootable snapshot. This however with Apple changes to macOS security to lock things down against external bootable SSD has been less successful endeavor in recent years.
Standard backups
Question on sanpshot: going forward and backward
On my mac, I have CCC snapshots (SS) for the past 12 months, one SS for each month.
If I restore my mac using the June (2024) SS, then find out it is not what I want, can I
(A) use the SS on Dec (2024) to restore? or
(B) use the SS on Jan (2024) to restore?
(C) Next, my mac is corrupted and I re-install the same OS, can I use the SS created before corruption?
(Edit: Questions answered.)
On my mac, I have CCC snapshots (SS) for the past 12 months, one SS for each month.
If I restore my mac using the June (2024) SS, then find out it is not what I want, can I
(A) use the SS on Dec (2024) to restore? or
(B) use the SS on Jan (2024) to restore?
(C) Next, my mac is corrupted and I re-install the same OS, can I use the SS created before corruption?
(Edit: Questions answered.)
Last edited:
Conflicting statements on Snapshots by two gurus
I have 10 snapshots made on 10 consecutive days and one snapshot per day.
CCC told me that on day 10, I could restore the Mac using SS(day 1) and if I like, restore it again using SS(day 9), that is I could restore using any SS, no matter what order I chose to use. I can understand this reasoning as all the 10 SSs are still on the CCC backup drive; they have not been deleted. Thus, forward or backward and as many times as I like, solely decided by me.
However, from Howard Hoakley, “If you prefer, you can roll back that whole volume to its state as recorded in the snapshot, but once you’ve done that, you can’t roll forward again, as all newer data is destroyed in that process.”
(Explainer: Snapshots, https://eclecticlight.co/2021/07/31/explainer-snapshots/). I can also understand this line of reasoning which is in clonflict with what CCC told me.
I hope someone could help explain which view is correct.
I have 10 snapshots made on 10 consecutive days and one snapshot per day.
CCC told me that on day 10, I could restore the Mac using SS(day 1) and if I like, restore it again using SS(day 9), that is I could restore using any SS, no matter what order I chose to use. I can understand this reasoning as all the 10 SSs are still on the CCC backup drive; they have not been deleted. Thus, forward or backward and as many times as I like, solely decided by me.
However, from Howard Hoakley, “If you prefer, you can roll back that whole volume to its state as recorded in the snapshot, but once you’ve done that, you can’t roll forward again, as all newer data is destroyed in that process.”
(Explainer: Snapshots, https://eclecticlight.co/2021/07/31/explainer-snapshots/). I can also understand this line of reasoning which is in clonflict with what CCC told me.
I hope someone could help explain which view is correct.
Woah - Used CCC (V7.0.4) for the first time in a while to clone the final OS15.2 release to my backup bootable SSD. The interface is completely different and easier to understand. And it worked without a flaw, as usual.👍🏻
Lou
Lou
Last edited:
I have CCC7. Just wondering if it is a different version than yours?
Just wondering your Sequoia backup is bootable?
^^^^Oh Geez - Is my face RED🤬 Don't know where I got that from❓ Corrected to V7.0.4👍🏻
As stated - Yes, the clone is bootable👍🏻
Lou
As stated - Yes, the clone is bootable👍🏻
Lou
^^^^Well, I just cloned the same disk again and it appears that the interface has reverted to the past interface❓❓❓ As posted above I liked the other interface better👍🏻
To make a clone:
1. Click on the destion disk that will pull up this window:
2. Click on Legacy Bootable Copy Assistant - Brings up this:
3. Click on Allow CCC to Erease.
4. That'll do it😊
Note - I always erase the destination disk first with Disk Utility
Lou
To make a clone:
1. Click on the destion disk that will pull up this window:
2. Click on Legacy Bootable Copy Assistant - Brings up this:
3. Click on Allow CCC to Erease.
4. That'll do it😊
Note - I always erase the destination disk first with Disk Utility
Lou
Sincere thanks for sharing your recipe! It seems simple, but without your showing how to do it, it would have been impossibly difficult for me.
It seems so. I followed Lou's method. I saw the system and data volumes created by CCC. When pressed "option" during start up, I saw CCC appeared as one of the startup disk.
Unfortunately I have OCLP and got stuck and once I clicked OCLP EFI, CCC did not showed up as startup disk anymore.
I think that without OCLP, it seems like Lou's method should work.
