Dépannage

Ouvrir les préférences

Cliquez sur le bouton Préférences dans la barre d'outils de CCC ou sélectionnez Préférences dans le menu de Carbon Copy Cloner.

Sélectionner les mises à jour

Recherchez les mises à jour en cliquant sur Rechercher les mises à jour.

La meilleure façon d'obtenir de l'aide est d'effectuer une demande d'assistance directement dans l'application CCC. Nous ne pouvons assurer notre assistance qu'en anglais et nous nous efforçons de répondre dans les plus brefs délais.

Menu Aide

Nous sommes là pour vous aider si vous avez une question sur CCC ou si vous avez besoin d'aide pour résoudre un problème. Choisissez Poser une question sur CCC… dans le menu Aide de CCC.

Lancement de la désinstallation directement dans CCC

Pour désinstaller CCC, maintenez la touche Option enfoncée et choisissez Désinstaller CCC… dans le menu Carbon Copy Cloner. La désinstallation de CCC entraîne la suppression immédiate de l'utilitaire privilégié de CCC et de toutes les tâches enregistrées. Le fichier de l'application CCC ainsi que les préférences de CCC sont alors placées dans la corbeille.

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. We have also received a handful of reports indicating that the Samsung SSD storage drivers cause problems booting from their devices.

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 CCC backup volumes. 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.

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 advice:

Some SMB volumes can't support macOS sparse disk images

We have received several reports that macOS is unable to create disk images on SMB volumes hosted by various NAS devices. If you attempt to create the disk image in Disk Utility (for example), Disk Utility reports an "RPC Error". After months of investigation, we have concluded that macOS Catalina has more stringent requirements for sparse disk images than previous OSes.

Note: This problem only affects macOS Catalina

Occasionally this annoying message comes up when you're trying to eject your destination volume. If CCC is currently using that volume as a source or destination to a running backup task, then CCC will effectively prevent the volume from being unmounted. If your backup task is not running, though, CCC isn't preventing the volume from being unmounted. But what application is?

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: