7/25/2023 0 Comments Bombich carbon copy cloner![]() This problem is not specific to CCC backups, but we see this frequently because CCC can create copies of macOS System volumes. Finder will not show, nor allow you to set custom icons on other Catalina and Big Sur startup disksįinder will show and allow you to customize the volume icon for your current startup disk, but not for other Catalina- or Big Sur-bearing startup disks that your Mac is not currently booted from. Workaround: If you need to recover your Apple Silicon Mac from a backup, we recommend that you reinstall macOS and then migrate data from your CCC backup using Migration Assistant. Apple resolved the issue in macOS Monterey. We reported this issue to Apple in March 2021 (FB9055615). In the current shipping version of macOS Big Sur (11.3), Apple's ASR utility can copy from the Apple Fabric storage in an Apple Silicon Mac, but it causes a kernel panic when cloning to Apple Fabric storage. Apple Software Restore causes a kernel panic when cloning to the storage in Apple Silicon Macs to configure CCC to re-erase and reclone the entire volume. Workaround: Any time you want to make the OS on the destination identical to the source, simply click on the Destination selector and choose Legacy Bootable Backup Assistant. CCC can then use its own file copier to maintain the backup of your user data, applications, and system settings. Our recommendation: We recommend erasing the destination only for the purpose of establishing the initial bootable backup. To avoid deleting your snapshots and the rest of your backup, CCC will not update the System volume on the destination when System updates are applied to the source. We do not anticipate that Apple will implement our requested functionality. We made a feature request to Apple in September 2019 (FB7328230) to allow ASR to clone just the System volume. As a result, every time an OS update is applied to the source, you would have to erase the whole destination volume (including any existing snapshots on that volume) just to update the system on the destination. Right now, ASR will only copy whole volume groups (System and Data) we can't choose to copy just the System volume. That volume can only be copied using Apple's proprietary APFS replication utility ("ASR"). Starting in macOS Big Sur, the system now resides on a cryptographically sealed "Signed System Volume". CCC will not update the System volume on a Big Sur bootable backup if you want the Mac to always boot from the backup volume). When your Mac has completed booting, you can optionally choose to set the startup disk to the current startup volume (i.e. Workaround: To boot from the backup volume, restart your Mac while holding down the Option key, then select the backup volume in the Startup Manager. We reported this issue to Apple in Nov 2020 (FB8889774). When Apple's APFS replication utility is used to copy a Big Sur System volume (something that is now required on macOS Big Sur), however, the cloned volume will not appear in the Startup Disk Preference Pane, despite being perfectly bootable. In the past, the Startup Disk Preference Pane would list all available startup volumes, including CCC backup volumes. Some Big Sur startup volumes don't appear in the Startup Disk Preference Pane We cite known problems that Apple introduced in the new OS below. CCC 5.1.22 (and all versions of CCC 6), published in October 2020, is fully compatible with macOS Big Sur. I’m not sure why this is not the default, or why the option is not in the Preferences dialog.Apple published macOS Big Sur in November 2020. This is much more useful when getting a sense of how far along it is. With this setting, the progress shows files compared, files copied, and gigabytes copied. diglloyd-iMac:MPG lloyd$ defaults write showDetailedTransferStats -bool YESĭiglloyd-iMac:MPG lloyd$ defaults read showDetailedTransferStats If done correctly, the value should read as "1" with this command:ĭefaults read showDetailedTransferStatsĪs shown, entering those commands looks like this (stuff in blue is what was entered). Quit Carbon Copy Cloner and paste the following into a Terminal window (press the return key when done).ĭefaults write showDetailedTransferStats -bool YESĢ. The issue is this: when backing up (cloning) many small files, the progress is not helpful in terms of gigabytes copied, so it is not apparent how far along things are which means it becomes inscrutable as to how long it will take (the progress indicator is not accurate in such cases).ġ. I wrote to to ask if there were a better progress display when cloning. SEND FEEDBACK Related: backup, Carbon Copy Cloner, cloning
0 Comments
Leave a Reply. |