Apple's APFS replicator is typically fast and flawless, but it does not handle some conditions with grace (or at all). CCC works to avoid as many of these ungraceful results as possible, but we have the following recommendations for the cases where Apple's APFS replicator flops.
CCC reported that the APFS replication failed
If your first backup attempt failed, try the following steps.
- Restart your Mac
- Rule out general hardware problems, and verify that your destination device is attached directly to a USB or Thunderbolt port on your Mac (avoid hubs). Consider removing any potentially-conflicting hardware drivers.
- Open Disk Utility
- Choose Show All Devices from the View menu
- Unmount your destination volume – this redundant step is often necessary to avoid failures in step 7.
- Select the parent device of your destination volume in Disk Utility's sidebar †
- Click the Erase button in the toolbar
- If you see a volume named "ASRDataVolume_xxx", select that volume and click the — button in the toolbar to remove it.
- Back in CCC, click on the Destination selector box and choose Choose a different destination. Choose the freshly-erased volume as the destination.
- Click on the Destination selector again and choose Legacy Bootable Backup Assistant. Choose the option to allow CCC to erase the destination.
- Click the Start button
† If you have other volumes or partitions on your destination disk that you do not want to lose, do not erase the whole disk. Instead, select the destination volume in this step. Click the "Erase Volume Group" button if it is presented in the Erase Volume panel.
Apple's APFS replicator will fail if there are problems with your installation of macOS, filesystem corruption on the source, storage driver conflicts, problems with the hardware, or if there are any media read failures. In short, it's just not very tolerable of real-world conditions. CCC's file copier is battle-tested — we've built years of experience into it to handle all sorts of challenging conditions with grace.
In cases where Apple's APFS replicator simply can't get the job done, we recommend that you configure CCC to perform a Standard Backup. A Standard Backup is a complete backup of all of your data, settings, and applications. This backup will be suitable for migrating all of your applications, data, and settings to a fresh installation of macOS should that ever be required. Creation of the backup alone is sufficient to protect your data, however this will not address any problems with the source.
To proceed with a Standard Backup, click the "X" button in the top-left corner of the destination volume icon in the Destination selector box to clear out the current destination selection. Then click on the Destination selector box again and reselect the destination volume.
Apple's APFS replicator does not gracefully handle the cancelling of a replication task. The destination volume is essentially corrupted, but ASR does not erase the volume to place it back into its pre-task condition. Further, the destination device is not only completely unresponsive, but even Disk Utility cannot load devices and volumes. This is scarier than it looks initially, there is fortunately a simple solution.
Solution: Physically detach the destination device from your Mac, then reattach it. If the destination is an internal device or cannot be easily detached, simply restart your computer. Then choose Disk Utility from CCC's Utilities menu and reformat the destination.
We reported this ungraceful result to Apple (FB7324207) in September 2019 and we are still awaiting a response.
Apple's APFS replicator clones the source volume at a very low level. Rather than copying individual files, it copies the filesystem data structures directly. Because this utility is not examining files on an individual basis, it's not able to deal with media failure nor filesystem corruption in a graceful manner (FB7338920). When ASR encounters media failure or filesystem corruption, the cloning task will fail and the destination volume will be in a corrupted state. The presence of media errors makes it very unlikely that ASR will be able to complete the clone, so CCC will not use the ASR utility if the source or destination is reporting read/write errors.
Solution: We recommend that you proceed with a Standard Backup, then address the hardware concern that led to the read/write errors, then restore your data from the backup (if the problem was affecting the source).