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!
- This update is fully qualified on Snow Leopard, Lion, Mountain Lion, and now Mavericks.
- CCC now offers volume-specific advice about how to enable full disk encryption. Enabling encryption on an OS X backup volume, for example, involves several steps that must be executed in the correct order. If full disk encryption is not supported on a particular volume, CCC indicates exactly why not. We have also added answers to some frequently asked questions about full disk encryption to our documentation.
- There is an odd edge case in OS X in which you can mount a network volume using a short user name, such as "johnny", but the remote host will place the long name in the filesystem URL that is returned, e.g. "Johnny Appleseed". Previously, this difference would cause CCC to believe that the network volume was mounted with other credentials altogether, and CCC would refuse to use the network volume under the assumption that permissions issues would ensue. This update addresses that issue, CCC will now immediately evaluate the filesystem URL of the network volume that is returned in reponse to its mount request and update its own internal reference to the user account as appropriate.
- Fixed an issue in which CCC may refuse to allow the user to schedule a backup task to a disk image that resides on a FUSE volume.
- Fixed an issue in which a scheduled task could load in a hung state if the task configuration file was corrupted.
- Some Drobo devices have a problem storing extended attributes larger than 1KB. Rather than reporting that the Drobo device is unable to accommodate the extended attribute, these devices report that the destination volume is full, even when there is adequate space available. This update catches this edge case and reports it in a more meaningful way.
- CCC will now explicitly refuse to create a Recovery HD partition if it can positively identify the selected volume as a Drobo device. Drobo's proprietary data moving techniques do not play well with dynamic partition changes, and Drobo specifically does not support the modification of partitioning outside of the Drobo Dashboard.
- Fixed a Mavericks-specific display anomaly in the list of items to be copied.
- Addressed an issue in which the OS rarely, but occasionally, does not send an "application finished launching" notification to the scheduled task helper tool, causing task initialization to fail.
- Addressed an issue in which the OS rarely, but occasionally, does not send a distributed notification that a task has finished, resulting in the task appearing to hang at the end despite the fact that it had actually finished.
- If you have employed the option to "Silently skip if the source or destination is missing", CCC will no longer proceed with that backup task if the missing volume reappears before the next scheduled run time. The task will instead run on its normal schedule.
- The "LOGIN" SMTP authentication mechanism for Apple's iCloud SMTP service recently started to return invalid challenge responses to SMTP clients, causing some CCC email notifications to fail (for users that use iCloud SMTP accounts with CCC). This version of CCC works around this problem by preferring the "PLAIN" authentication mechanism instead.
- Google recently made a change to its Gmail SMTP service that introduced a problem with sending email notifications to multiple recipients. This update resolves that problem.
Intel, OS X 10.6 or later