Dépannage

Occasionally a backup task can stall if the source or destination stops responding. To avoid waiting indefinitely for a filesystem to start responding again, CCC has a "watchdog" mechanism that it uses to determine if its file copying utility has encountered such a stall. By default, CCC imposes a ten minute timeout on this utility. If ten minutes pass without hearing from the file copying utility, CCC will collect some diagnostics information, then stop the backup task. Our support team can analyze this diagnostic information to determine what led to the stall.

Occasionally we receive reports of odd system behavior, such as:

Occasionally a circumstance arises in which CCC presents the following error message before creating or running a backup task:

Some antivirus applications may prevent CCC from reading certain files, mounting or unmounting disk image files, or, in general, degrade the performance of your backup. In some cases, antivirus applications can even affect the modification date of files that CCC has copied, which will cause CCC to recopy those files every time as if they have substantively changed. In another case, we have seen such software create massive cache files on the startup disk during a backup, so much so that the startup disk became full.

We regularly see cases of APFS filesystem corruption that lead to errors during a backup task. This corruption is typically presented in an error like one of these:

readlink_stat("/Photos/Foo/2020_Dumpster_fire.jpg") failed: Illegal byte sequence (92)
rename("/Photos/Foo/.2020_Dumpster_fire_out_of_control.jpg.asdfgh" -> "/Photos/Foo/2020_Dumpster_fire_out_of_control.jpg") failed: No such file or directory (2)

When CCC encounters these errors, the affected items are listed in CCC's Task History window, often with this overly-optimistic advice:

Some Big Sur startup volumes don't appear in the Startup Disk Preference Pane

In the past, the Startup Disk Preference Pane would list all available startup volumes, including volumes cloned by CCC (whether CCC used ASR or its own file copier). Some Big Sur cloned volumes do not appear in the Startup Disk Preference Pane, despite being perfectly bootable.

We have reported this issue to Apple (FB8889774) and we are currently awaiting a response.

L'utilitaire de réplication APFS d'Apple fonctionne généralement rapidement et sans souci, mais il gère mal (voire pas du tout) certaines situations spécifiques. CCC s'efforce d'éviter le plus possible ces résultats problématiques. Néanmoins, voici quelques conseils en cas d'échec avec l'utilitaire de réplication APFS d'Apple.

We occasionally receive reports of strange behavior from USB devices, e.g. slow performance, disks dropping offline in the middle of the backup task. In some of those cases we've discovered that third-party storage drivers are causing the problem. In particular, the SAT-SMART drivers and some ancient BlackBerry USB drivers can lead to problems. If you're troubleshooting a USB device behavior or performance problem, we recommend that you consider uninstalling these drivers.

Apple introduced a bug in 10.15.5 that prevents the creation of firmlinks

The chflags system call no longer works correctly on 10.15.5 with regard to setting the special "firmlink" flag that establishes links between the System and Data volume group members. If you're establishing a new backup of macOS 10.15.5 or later, CCC 5.1.17 (and earlier) will be unable to create a correctly-functioning APFS volume group. Many folders on the destination volume will appear empty, and the volume will not be bootable.

Update November 2020: Apple has resolved this Finder bug in macOS Big Sur.