Carbon Copy Cloner Icon   

Release History

 

v. 3.5.2, December 19, 2012

Note for users backing up to a Remote Macintosh: Starting with this update, the system requirements for the remote Macintosh are now the same as those for the Mac running CCC. Backing up to a PowerPC Macintosh via the "Remote Macintosh" option in CCC's Destination menu will no longer work.

Added support for sending notifications to Mountain Lion's Notification Center. Growl support will continue to be supported for Snow Leopard and Lion, but in Mountain Lion, CCC will only send notifications to the built-in Notification Center. We understand that Growl offers functionality beyond Apple's Notification center, but the time required to maintain support for Growl and protecting CCC from problems specific to Growl has become too much of a burden to continue its support when there is a capable alternative offered by the operating system.

Scheduled tasks configured to run when the source or destination is reattached now have an optional reminder interval. If your source or destination volume hasn't been attached in a given length of time (7 days by default), CCC will run the task and prompt you to attach the volume.

When selecting a folder as the source or destination, CCC now displays a "bread crumb"-style indicator of the path to the folder to make it more clear where exactly the source and destination folders are located.

CCC will now warn you if your USB-attached source or destination volume is "slow", e.g. attached in a manner that results in the interface speed being negotiated to 1.5MB/s or less.

Task names are now sorted in a case insensitive manner in the Scheduled Tasks window.

Improved CCC's handling of MacFUSE filesystems that do not explicitly allow access to the root user.

Made some improvements to how CCC prevents sleep during a backup task.

Improved handling of mounting network volumes with guest privileges.

CCC now offers a simple mechanism for updating the password for the credentials used to mount a network volume in a scheduled task (e.g. if the password was specified incorrectly when the task was created or has subsequently been changed).

There is now only one menu item for creating a Mac OS X Installer in CCC's Source menu. Selecting this item will automatically select the Mountain Lion installer, if present, the Lion installer if present (if the ML installer is not present), or give the user the opportunity to manually select a Mac OS X installer application. The user can also hold down the Option key while choosing this menu item to manually select a Mac OS X Installer application.

When CCC's Cloning Coach reports that the destination's Recovery HD needs to be updated, updating that Recovery HD is now much more automated.

CCC now works around problems cloning a Recovery HD volume that are caused by PGP and Paragon "flavors" of the GUID Partition scheme.

Fixed some issues handling file ownership when the source or destination filesystem is nfs, ppfs, osxfusefs, or fuse4x.

Made a few adjustments that should cause CCC to behave better while logged in as the root user. We don't recommend logging in as the root user, nor do we spend a lot of time testing this configuration, but it should work better now.

Made some improvements to how a logout event is handled. During logout, the WindowServer is torn down. Depending on the timing of that and when a CCC scheduled task manages to exit, it's possible for the scheduled task to make requests to the now-absent WindowServer which can lead to an exception. That exception can place CCC into an indeterminate state for a prolonged period of time. Now if a backup task is running and you log out, CCC will abort the backup task and exit more quickly. If an exception occurs, a secondary termination mechanism will reliably terminate the scheduled task, allowing it to properly reload and reconnect to the new WindowServer process.

Some email servers require SSL but do not support STARTTLS, which is the IANA-approved standard for negotiating SSL-protected connections to SMTP servers (http://tools.ietf.org/html/rfc3207). This update accommodates these servers by pre-negotiating an SSL connection when using port 465.

Made some minor user interface adjustments to accommodate the behavior of encrypting Fusion volumes.

Fixed the errant presentation of a configuration concern when the destination volume's Recovery HD OS version is not a perfect match to the OS version on the source. It is appropriate, for example, for the source volume's OS to be 10.8.2, but the Recovery HD volume's OS to be 10.8 (because Apple does not update the Recovery HD during ordinary OS updates).

Fixed a schedule calculation issue for monthly tasks in which some months could be skipped.

Fixed an issue in which some folders in the list of items to be copied could not be opened.

Addressed a couple issues where CCC would hang while trying to retrieve information from an unresponsive volume.

Filenames that use more than 255 bytes (e.g. less than 255 characters, but with non-ASCII, multibyte characters) are now preserved properly.

Fixed an issue in which applying the Mac OS X 10.8.2 Supplemental update would cause CCC scheduled tasks to report that "Mac OS X is not responding to CCC's request to perform a privileged task".

Fixed an issue in which CCC was unable to copy files to the destination if the root folder of the source was locked.

v. 3.5.1, August 3, 2012

Fixed an issue in which CCC was unable to save scheduled tasks after being updated.

Resolved a permissions issue related to accessing some files on source when the destination was a network volume.

Made some minor UI adjustments in the Documentation window.

Fixed an intermittent exception at the end of a scheduled task that would result in the "Task finished" window disappearing early and failure of email notifications.

Fixed an exception that would cause a hang during the creation of a Recovery HD volume.

Non-admin users will no longer be prompted to authenticate when launching CCC on Lion or Mountain Lion. This authentication was leveraged to collect information about the Recovery HD volumes attached to your Mac, but CCC was unable to give that indication prior to the authentication dialog being presented. To avoid unnecessary concern, we chose to not collect that information when a user is logged in to a non-admin account.

When LateNite Software's "Clusters" software makes changes to .DS_Store files on the source volume, those changes can lead to errors during the backup. These errors are now suppressed.

v. 3.5, July 20, 2012

CCC is no longer donationware

If you have not "donated" to Bombich Software in the past, this version of CCC will impose a 30-day trial. In order to grow our support and development team, we have made the transition to a commercial product. This will allow us to to continue offering frequent updates to our software, including new features. This will also enable our stellar customer support to remain that way. Transitioning from donationware to a commercial offering underscores our commitment to deliver the best Mac OS X cloning and backup utility on the market. More information about this transition is available in the "CCC License, Registration, Trial, Banners, etc." section of the documentation.

This version of CCC requires Mac OS X Snow Leopard, Lion, or Mountain Lion, and is fully qualified on each of those OSes. We will continue to provide user support and bug fixes for Tiger and Leopard users on CCC 3.4.x for a while longer.

Recovery HD support has been overhauled to better support the concept of "one Recovery HD partition per volume", rather than one per disk. If you have multiple backup volumes with different OSes (e.g. Lion and Mountain Lion), CCC can associate a Recovery HD with each one and apply the appropriate OS to each Recovery HD partition.

CCC is now signed with an Apple Developer Certificate for GateKeeper compliance.

Most of the binaries in the CCC bundle are now 32/64-bit Intel-only binaries.

Fixed an issue that appeared in 10.7.4, specific to Macs running Lion with a 64-bit kernel, in which the /Volumes folder on the destination volume would be locked rather than hidden. This resulted in external volumes being unmountable when booted from the backup volume.

Performance of deleting scheduled tasks is much improved.

CCC previously encountered some performance problems when saving very large numbers of scheduled tasks (e.g. 29). These problems should now be resolved. This is most applicable when updating CCC, or when CCC has been moved and all tasks must be re-saved at the same time.

Updated graphics for High Resolution support on the new MacBook Pro (Retina).

v. 3.4.6, July 20, 2012

Scheduled tasks that are configured to run "When the source or destination is reattached" and that have a remote Macintosh as the source/destination will now properly run when the local destination/source volume is reattached.

Fixed a crashing issue that affected scheduled tasks for Tiger users in cases where CCC was unable to derive a proper Time Zone value from the system.

Fixed an issue that would lead to a hang during the "Authenticating" phase at the beginning of a backup task.

.DS_Store files are now excluded when backing up to SMB network shares. Some SMB filesystems will actually refuse files by this name, and this often generates unnecessary error messages during an otherwise uneventful backup task.

Scheduled tasks no longer cancel wakeorpoweron events when exiting. This resolved an issue in which some Macs would effectively clear these canceled events from the PowerManagement queue, and subsequently not start up the Mac when the scheduled task was configured to do so.

Scheduled tasks configured to run manually that are run when the source or destination is unavailable will now proceed to run if a missing volume is reattached.

Fixed an issue in which scheduled tasks would be rescheduled at the wrong time when the time zone abbreviation was ambiguous (e.g. EST is used in the United States and Australia).

If a block-level clone cannot proceed because the source volume is too severely fragmented, CCC now offers proper guidance for proceeding with a file-level copy.

The capacity of new sparseimage or sparsebundle disk images will now be limited to 2X the capacity of the source volume in cases where the underlying destination volume is excessively large. In cases where the destination volume is 16TB, for example, the underlying disk image creation tool would fail to create a disk image with this capacity and would offer a very poor, generic error code.

v. 3.4.5, April 24, 2012

v. 3.4.4, February 7, 2012

v. 3.4.3, September 29, 2011

v. 3.4.2, August 4, 2011

v. 3.4.1, July 21, 2011

v. 3.4, July 20, 2011

New features:

Issues Resolved