Carbon Copy Cloner backups are better than ordinary backups. Suppose the unthinkable happens while you’re under deadline to finish a project: your Mac is unresponsive and all you hear is an ominous, repetitive clicking noise coming from its hard drive. With ordinary backups, you’d spend your day rushing out to a store to buy a new hard drive and then sit in front of your computer reinstalling the operating system and restoring data.
With Carbon Copy Cloner, your data and the operating system’s data are all preserved on a bootable volume, ready for production at a moment’s notice. When disaster strikes, simply boot from your backup and get back to using your Mac. At your convenience, replace the failed hard drive and then let CCC restore the OS, your data and your settings directly from the backup in one easy step.
Any backup application can save your stuff. A CCC bootable backup will save your productivity too!
- When creating a new disk image on a Mojave+ system, CCC will now create APFS-formatted disk images if the source volume is APFS-formatted. All snapshot functionality afforded to APFS-formatted volumes will apply to APFS-formatted disk images as well
- Hard drives from a popular vendor ship with a rogue "is a bundle" flag set on the root folder. When cloning this volume to a folder, the rogue flag is preserved on the destination folder, which causes the Finder to treat it like a file, making it awkward to see the items that were copied. CCC now strips this rogue flag from the root folder of the selected destination to avoid the annoying result
- Adjusted the handling of 0-byte "placeholder" files (e.g. Dropbox, GoogleDrive, OneDrive "online only" files) to avoid lengthy delays. These delays were particularly notable when working through Dropbox folders
- Total snapshot disk usage is presented more prominently in the Disk Center
- When cloning to an ExFAT or FAT32 volume, custom volume icons are now preserved at the destination
- Resolved an error that can occur when creating read-only disk images on SMB network volumes. Due to a bug in macOS Mojave, sparseimage disk images cannot be created on SMB NAS volumes. Rather than creating a sparseimage intermediate disk image, CCC will now create aa sparsebundle intermediate disk image
- CCC's "trust but verify" case-sensitivity check is now applied to "ufsd_ExtFS" volumes as well, after getting confirmation from a user that these volumes incorrectly report themselves as case-insensitive, when in fact they are case-sensitive
- To protect against unauthorized modifications, CCC now requires that pre
- and postflight scripts are owned and writable only by the system administrator, and that all parent folders of the scripts are owned and writable only by the system administrator. A new "Secure CCC's Scripts folder" option is available in the Utilities menu to help meet these new requirements
- Fixed some UI issues around the visibility of the pre/postflight script interface elements
- Fixed an issue in which other tasks within a group would start to run after the following events: a) start task group, b) stop task group before all tasks complete, c) manually run one of the tasks within the group
- Fixed an issue in which CCC would errantly report that a destination lacked support for files larger than 4GB
- Hourly run time limits that have a start or end time at midnight will be applied a little more gracefully, e.g. a task that starts a few seconds prior to midnight will be allowed to run with a midnight start time limit
- Fixed a password decoding issue that could cause problems while configuring a task with the Remote Macintosh option if the administrator's password on the remote Mac contained 3-byte characters (e.g. €)
- Tasks that failed due to the source or destination being missing will no longer get a "failed" badge in the Tasks table if the task is also configured to not send error notifications when the source or destination is missing. Likewise, the Task Plan will now indicate this condition specifically, rather than offering a generic "Errors occurred during the last run" message
OS X 10.10 or later, 64-bit processor