It is our aim to have the Task History window provide the user with enough information to find and troubleshoot any problems they're having with their backup tasks. For debugging and support purposes, however, CCC logs its activity in the following files:
Zuletzt aktualisiert von 27 April 2021
Network performance is usually the bottleneck of a backup task that copies files to or from a network volume, but there are several other factors that can affect performance as well. Here are some suggestions for improving the performance of your NAS-based backups.
Zuletzt aktualisiert von 23 January 2023
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.
Zuletzt aktualisiert von 20 January 2023
Occasionally we receive reports of odd system behavior, such as:
Zuletzt aktualisiert von 12 July 2022
Occasionally a circumstance arises in which CCC presents the following error message before creating or running a backup task:
Zuletzt aktualisiert von 27 April 2021
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.
Zuletzt aktualisiert von 27 April 2021
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:
Zuletzt aktualisiert von 4 January 2021
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.
Zuletzt aktualisiert von 13 May 2021
Der APFS Replikator von Apple ist in der Regel schnell und fehlerlos, doch mit bestimmten Bedingungen kommt er nur schwer oder gar nicht klar. CCC versucht, diese Szenarien zu vermeiden, doch sollte der APFS Replikator fehlschlagen, haben wir die folgenden Empfehlungen für Sie zusammengestellt.
CCC meldet, dass die APFS Replikation fehlgeschlagen ist
Wenn Ihr erstes Backup fehlschlägt, probieren Sie folgende Schritte aus. Bleibt das Problem trotzdem bestehen, finden Sie im nächsten Abschnitt weitere Hilfestellung.
Zuletzt aktualisiert von 7 May 2021
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.
Zuletzt aktualisiert von 5 June 2020