"Back off man, I'm a scientist" (Bill Murray, Ghostbusters). Sorry, couldn't resist. I have sufficient evidence to convince me that CCC was part of the problem.
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
I've installed the latest beta and auto run when attached still doesn't work for me.
Great idea, except....
Already done that by recreating the backup task. In fact, I tried reselecting the drives before I recreated the task.
Can you clarify? So...can only be cloned once...can't use same drive ...so..clone and hold drive in storage for an emergency or to re-clone have to make an 'original' clone each time? Hence, use a non-bootable for 'daily' back up to CCC and for bootable have to 'erase...clone' on perviously stored backup? Sorry if not too clear!Even though we all ran into what Big Sur introduced, that still didn't completely stymie us from make partial clones for restoration of the ID, settings/data for doing a reinstall the the MacOS 11 using Migration Assistant. Eventually Apple got its APFS replication utility to work well enough that you could make bootable backstops, although only on the first cloning attempt, you could not perform incremental cloning of the system anymore.
When Monterey first came out we were back to the signed system volumes and the APFS replication utility not working for creating bootable clones. But Apple did fix it a bit later to it being usable again after a few betas. Later in Monterey beta cycle they added security that requires a admin level user to use their passcode to allow a external clone of that cryptographically sealed "Signed System Volume to be able to boot and see other volumes. You still are stuck with the first cloning attempt working limitation.
Hopefully Apple has taken this as far as it needs to go now.
Otherwise you would have to go out into 'the real world' where they demand 'Results'.........😉!
Thanks for the tip. Unfortunately the command doesn't appear to work under Monterey. I get:Maybe you need to run the terminal command to make the hidden volume show under finder? See the last part of this article
How to hide specific mounted volumes from your Mac's desktop
Learn how to leave specific volumes mounted but still hide them from your Mac's desktop for a cleaner look.www.idownloadblog.com
Note the lower-case “v” in this command as opposed to the upper-case in the hiding command. This is the attribute controlled by “-a”; “V” means “invisible”, and “v” means “visible”.
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
I notice if I toggle the option to show external drives on the desktop the CCC - Data volume does appear on the desktop, but once again not in the left column of Finder. It shows under /Volumes
EDIT: After some reading here: https://bombich.com/kb/ccc5/working-apfs-volume-groups and looking at Disk Utility I can see that the CCC - Data volume is marked as an APFS Data Volume and is therefore hidden. I don't know whether Monterey made this change, or an update to CCC made the change. What is peculiar is that nobody else has noticed this behaviour.
EDIT 2: I dropped a note through to Mike Bombich. This new behaviour, marking the CCC - Data volume as hidden is from Monterey and not something CCC has done. Unless there is a way to change the marking I guess we’ll just have to live with it.
Last edited:
Smiling is nicer. Perhaps you're unfamiliar with this quote:
Sorry Blowback. I misinterpreted your response, which perplexed me. Murray's line is popular amongst scientists.
No prob....Scientist/Engineer myself for many years. The Universe is the size of your understanding of it....And, you are aware that my 'quote' is from the same movie? Its my favorite from the movie.
Space is big, really big.
I mean, you may thing it's a long way down the road to the chemist but that's just peanuts to space.
Listen....
No, I missed that, which is probably why I was perplexed. I got Feek's though. Another favourite.
Carbon Copy Cloner 6.0.5-b3 available if you have beta downloads enabled.
- New
We added a new "macOS Downgrade Assistant" feature, accessible via CCC's Utilities menu. The Downgrade Assistant can assess a backup volume's compatibility with Migration Assistant, and will create macOS Installer media using a specified volume and installer application. - New
We added another small new feature in the source and destination selectors. If the selected source or destination is a network volume, or a folder on a network volume, you can hold down the Option key to reveal a "Switch to AFP" or "Switch to SMB" menu item. We frequently see slow performance and errors from SMB-mounted volumes, and we often recommend that people try "the other" protocol when the current protocol isn't working out. Now we've made it really simple to switch between the two to see if using a different protocol will yield better results. - Changed
Tasks in the sidebar can once again be arranged when the sidebar sorting is configured as "Manual". - Changed
Made some adjustments that should improve performance when a task is writing large files to a rotational destination. Made a separate adjustment that should improve performance when writing to ExFAT-formatted volumes. - Changed
b3: Fixed a display issue in the Legacy Bootable Backup Assistant that would occur when selecting a SoftRAID destination volume. - Fixed
b3: Fixed an issue that arose recently in macOS Monterey that was causing failures while trying to configure new Remote Macintosh tasks. - Fixed
b3: Fixed an issue affecting tasks configured to run "When the source or destination is remounted" in which the tasks would fail to run on volume appearance if the destination's System volume had been removed.
Carbon Copy Cloner 6.0.5 is now available.
- New
We added a new "macOS Downgrade Assistant" feature, accessible via CCC's Utilities menu. The Downgrade Assistant can assess a backup volume's compatibility with Migration Assistant, and will create macOS Installer media using a specified volume and installer application. - New
We added another small new feature in the source and destination selectors. If the selected source or destination is a network volume, or a folder on a network volume, you can hold down the Option key to reveal a "Switch to AFP" or "Switch to SMB" menu item in the Source and Destination selectors. We frequently see slow performance and errors from SMB-mounted volumes, and we often recommend that people try "the other" protocol when the current protocol isn't working out. Now we've made it really simple to switch between the two to see if using a different protocol will yield better results. - Changed
Tasks in the sidebar can once again be arranged when the sidebar sorting is configured as "Manual". - Changed
Made some adjustments that should improve performance when a task is writing large files to a rotational destination. Made a separate adjustment that should improve performance when writing to ExFAT-formatted volumes. - Changed
Fixed a display issue in the Legacy Bootable Backup Assistant that would occur when selecting a SoftRAID destination volume. - Fixed
Fixed an issue that arose recently in macOS Monterey that was causing failures while trying to configure new Remote Macintosh tasks. - Fixed
Fixed an issue affecting tasks configured to run "When the source or destination is remounted" in which the tasks would fail to run on volume appearance if the destination's System volume had been removed.
I am evaluating CCC for use on my MBP. I have downloaded the trial version and have setup up several tasks. Although there is a message that they are monitoring change, I have removed some files from the source folder and a synch task has not been triggered. My setup:
MBP > Folder A
Ext Hard Drive> Folder A Copy
Automation:
Then as a second test, I set it up with a Data Threshold Limit of 0GB thinking that maybe this would trigger any change in files on the source folder. It did not.
What am I missing?
Thanks!
MBP > Folder A
Ext Hard Drive> Folder A Copy
Automation:
- Schedule Basis: When files are changed on the source.
- Frequency Limit: 1 minute= does this mean checks every minute for a change?
- Data Threshold Limit: Default is 1 GB- Does this mean that it does not trigger until 1GB of change or is 1GB the max that it will transfer? I realize under Schedule Basis I have set the trigger as when files are changed on source.I would assume this overrides the Data Threshold limit, but maybe not. But I have tested it both ways setting it to both 1GB and 0GB and a Task Synch effect has not triggered.
Then as a second test, I set it up with a Data Threshold Limit of 0GB thinking that maybe this would trigger any change in files on the source folder. It did not.
What am I missing?
Thanks!
I am evaluating CCC for use on my MBP. I have downloaded the trial version and have setup up several tasks. Although there is a message that they are monitoring change, I have removed some files from the source folder and a synch task has not been triggered. My setup:
MBP > Folder A
Ext Hard Drive> Folder A Copy
Automation:
So to review, I setup up several tasks, at first with the above settings. Manually it would sink, but then to test it I removed 1 file off the source folder placing it in the trash to see if this would trigger a synch task. It did not.
- Schedule Basis: When files are changed on the source.
- Frequency Limit: 1 minute= does this mean checks every minute for a change?
- Data Threshold Limit: Default is 1 GB- Does this mean that it does not trigger until 1GB of change or is 1GB the max that it will transfer? I realize under Schedule Basis I have set the trigger as when files are changed on source.I would assume this overrides the Data Threshold limit, but maybe not. But I have tested it both ways setting it to both 1GB and 0GB and a Task Synch effect has not triggered.
Then as a second test, I set it up with a Data Threshold Limit of 0GB thinking that maybe this would trigger any change in files on the source folder. It did not.
What am I missing?
Thanks!
The frequency limit is the minimum amount of time that CCC will allow to pass before it attempts a backup. The data threshold means it doesn’t trigger until it detects at least that size of altered data before it attempts a backup (your first guess).
For example, mine is set to 60 minutes and 1GB. That means CCC will wait for at least 60 minutes and at least 1GB of change before backup. If it reaches the 1GB before the 60 minutes is up, it will wait. If it reaches the 60 before 1GB, it will wait.
Thanks for responding. 1Gb is a huge amount of data imo to wait for a sync, I want the equivalent of any change on the source to update say within a minute. I tried setting the data threshold to 0 and that did not seem to work. With the data I am saving, mostly documents of various types, bills, notes, records, guides, manuals, it could be anywhere from days to weeks, to trigger a sync, and for somone who is trying to keep the equivalent of an electronic office, where everything exists on a hard drive, and many scanned documents are shredded after scanned, if it is a 1GB limit, that just does not work for my purposes.
Why have a setting: when files changed on source if 1Gb is the lowest threshold that can be set? There is one heck of a lot of file changing going on before the 1Gb threshold is reached, if 0 is not accepted.
Maybe it exists, but on their web site, I see no tech/customer support or community forum to discuss such things.
The forum and support seem to be right here.
Unless you mail them directly ...
;JOOP!
P.S.: hey! another squirrel!