Are you on an Intel Mac? I'm home now, so I pulled up the developer's webpage. Here's the latest version https://www.charlessoft.com
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 or Time Machine?
- Thread starter 5425642
- Start date
- Sort by reaction score
No, M1 Air 16GB 1TB. I tried the version downloaded from charlessoft.com and received the same error. I found a program called BackupLoupe that seems to do the same things while being more refined and offers more features. You have to pay for it though. I'm giving it a trying right now, but it's taking forever to index my cir. 500GB of Time Machine backups. Granted, they're on an NAS, but you'd think 24 hours would be long enough.
Don't know if this will work (I don't have an Silicon Mac).. but could you see if could run the Intel version with Rosetta 2, and see if that gives you any errors?
Again, I don't know how well it will work (it may not work at all), but why not, n'est-ce pas?
BL.
The M1 is probably the issue. It shouldn't take THAT long. When TM went wonky on me a few weeks ago it did a 5tb backup to each of my 8tb drives. It takes a LONG time for TimeTracker to read those volumes, but we're talking less than an hour.
I backup to three Time Machine drives. When one dies, I buy another and put it in. I've restored complete from Time Machine many times over the years, and, have also restored individual files that were accidentally deleted. So I am a very big fan of Time Machine. I have used SuperDuper and CCC in the past but that was usually to clone a drive for a swap or move an operating system to run as an external drive on another machine.
There is definitely an Apple Silicon restriction as booting has to use an internal part in order to boot. If the internal part fails then nothing external can boot at all. There are difficulties with Big Sur because of the way system and data files are separated but there are work arounds for that - but still a bit tricky. There is no work around for the Apple Silicon restriction.
Time Machine is only about 60% reliable in my experience (but I'm back on Mojave and High Sierra.) CCC is reliable.
+1 TM
Works well with open source NAS SW https://truenas.com Used it to migrate a new M1 MBP from an Intel MBP TM backup.
"Set it and forget it!" - Ron Popeil
Works well with open source NAS SW https://truenas.com Used it to migrate a new M1 MBP from an Intel MBP TM backup.
"Set it and forget it!" - Ron Popeil
An M1 Mac cannot be booted at all if its internal storage completely fails. Full stop. An Intel Mac can, but if you're using Big Sur or later, things get more complicated (or simpler, depending how you look at it) because the OS itself exists in the form of a crytographically "sealed" volume that cannot be changed, which can only be copied by a certain Apple utility called ASR, which doesn't play well with others.
The better approach is to choose the external device you would want to boot from in an emergency, install macOS onto that device, boot from it, and then use Migration Assistant to copy, or "clone", all your non-OS material from your main drive. After that initial set-up of the "clone", you go back to using the main drive as usual, and run CCC to sync changes on the main drive out to the clone, keeping it updated and ready to spring into action when needed.
Note that in this scenario, macOS updates subsequently installed to your main drive will not propagate to the clone. This isn't a problem, though, because if you boot from the clone, you'll be able to install any missed updates at that time in the usual way; your non-OS data will all still be there, ready and waiting for you.
My source for most of the foregoing advice is this CCC support article: Frequently Asked Questions about CCC and macOS 11 (and later OSes)
Once, at a really critical moment, my CCC-bootable back up didn't work, it was just dead and didn't boot. Stopped using it at that moment and have used SuperDuper since then. It has never failed me. (It claims it supports bootable back ups on M1 also, but I haven't used that feature yet?)
M1 and newer Macs using CCC allow the APFS replication utility to work once to capture the current OS and then conduct incremental data backups. But the need for a bootable backup using newer Macs just isn’t vital. You can always reinstall the OS from the recovery tools menu over the network, or use a another recent Mac with USB-C cable to the target and do a DFU revive or restore to get the OS back to operational. Then use your external bootable snapshot with Apple Migration Assistant to fully restore the M1 or newer Mac to what you were before something happened. You of course don’t need to go that far most of the time.
Monterey adds additional security when installing, updating, and making bootable clones now with M1 and newer Macs. You have the enter Administrator password to install OS. So things are different now for SuperDuper compared to CCC now, which CCC has become a lot more advanced in its newest version.
To my knowledge, CCC will not create a bootable clone on Apple Silicon machines. Bombich is pretty clear about that on his site. If above commenters can shed some light on how they created and tested their CCC bootable clone I would appreciate it.
Superduper! bootable clones work fine, I have done several of them during my migration, on 4 different disks, all booted an M1 MBA fine. Initially I had a lot of fails, therefore the following notes: 1), any usb externals you plan to clone to need to be plugged in before booting. Restart if necessary. Its irrelevant if they show up in Finder, can be written to or manipulated in DU, they need to be plugged in prior to booting. 2), use Coca to keep your machine awake during the process. There's gotchas, read the Superduper blog before committing to a purchase.
However, a good part of the reason for having a clone is gone. One can no longer clone to the internal. I'm not sure if the internal is compromised the Mac will even boot off an external (anyone care to donate an Apple Silicon Mac). I find Time Machine has materially improved in its Monterey version. I have one clone to adequately test content creation apps before adopting them. They can be messy installs, at times built on questionable coding with lengthy learning curves.
As a result of Apple Silicon, Monterey and Time Machine improvements, my backup strategy has changed. I no longer use clones for daily backups. I now will have 2 Time Machine disks plus infrequently updated offsite clones. Having had my provider “lose”, and not be able to replicate, 5 GB of data, cloud backups are still a non-starter for me.
Superduper! bootable clones work fine, I have done several of them during my migration, on 4 different disks, all booted an M1 MBA fine. Initially I had a lot of fails, therefore the following notes: 1), any usb externals you plan to clone to need to be plugged in before booting. Restart if necessary. Its irrelevant if they show up in Finder, can be written to or manipulated in DU, they need to be plugged in prior to booting. 2), use Coca to keep your machine awake during the process. There's gotchas, read the Superduper blog before committing to a purchase.
However, a good part of the reason for having a clone is gone. One can no longer clone to the internal. I'm not sure if the internal is compromised the Mac will even boot off an external (anyone care to donate an Apple Silicon Mac). I find Time Machine has materially improved in its Monterey version. I have one clone to adequately test content creation apps before adopting them. They can be messy installs, at times built on questionable coding with lengthy learning curves.
As a result of Apple Silicon, Monterey and Time Machine improvements, my backup strategy has changed. I no longer use clones for daily backups. I now will have 2 Time Machine disks plus infrequently updated offsite clones. Having had my provider “lose”, and not be able to replicate, 5 GB of data, cloud backups are still a non-starter for me.
Afraid this is true and I also have been using differnt means (combine the two actually.)
redundancy is the key. Multiple time machine backups, one time machine and a few CCC clones, a bunch of CCC clones. No matter what, you'll be doing a full install of the OS and then a migration.
Decided to go done the Time Machine path with a NAS. One of the external storage drives I have I just noted is exFAT so isn't being picked up by Time Machine?
Questions - No easy tricks to get an exFAT picked up by Time Machine? Seems not, in which case I might copy the 4TB directly across to the NAS, reformat my external portable drive to MacOSExtended, copy back, and then get Time Machine working across it... (?)
Questions - No easy tricks to get an exFAT picked up by Time Machine? Seems not, in which case I might copy the 4TB directly across to the NAS, reformat my external portable drive to MacOSExtended, copy back, and then get Time Machine working across it... (?)