Product: 
ccc6
*****
** DNL: Try the beta**

Let us know if this issue persists in the current beta.

**To get the beta:**

1. Click the **Preferences** button in CCC's toolbar
2. Click the **Software Update** button in the Preferences window toolbar
3. Check the **Inform me of beta releases** box
4. Click on the **Check for updates now** button and follow the instructions provided to apply the update.


*****
** DNL: CCC 3.4.7 no longer available**

I'm sorry, we're no longer distributing or supporting a version of CCC that will work on Mac OS 10.5 or older. In a pinch, you can use Disk Utility to copy your OS and data to another disk.

CCC 4 is required for Mac OS X 10.10 and newer and is recommended for Mac OS X 10.8 - 10.9.

CCC 3.5.7 will work on Mac OS 10.6 - 10.9


*****
** DNL: Try the current release**

Please let us know if the following steps do not resolve this problem:

1. Download this build of CCC: https://bombich.com/software/download_ccc.php?v=latest
2. Replace the copy of CCC that you currently have with the newer build of CCC
3. Open the new build of CCC and run your task again


*****
** DNL: Checksum slow**

You are using the checksumming option, **Find and replace corrupted files**. With this option, CCC will calculate an MD5 checksum of every file on the source and every corresponding file on the destination. CCC then uses these MD5 checksums to determine if a file should be copied.

If you want to use that option, I would recommend that you use two tasks: one without the **Find and replace corrupted files** option that runs daily and another task with that option that runs weekly or monthly. Schedule the second task to run at a time when the computer can run a longer backup task.

The **Find and replace corrupted files** option is documented here if you would like more detail on how that option works:

[Find and replace corrupted files] (https://bombich.com/kb/ccc4/advanced-settings#checksum)


*****
** DNL: PDOX2**

You have two scheduled tasks (**** & ****) that are configured to back up the same source volume to the same destination volume. When these tasks run at the same time, they conflict with each other. These conflicts led to the errors that were reported.

To avoid the errors, delete or reschedule one of the tasks.


*****
** DNL: Submit logs CCC v4**

Can you submit your logs to us for review? Reviewing the task and its settings will help us evaluate the problem. The easiest way to submit your logs is from within CCC: Choose **Submit logs** from the Help menu and follow the instructions provided.

**Don't forget to let us know the submission ID after you submit the logs**


*****
** DNL: Submit logs CCC v3**

Can you submit your logs to us for review? The easiest way to do this is from within CCC.
**Be sure to copy and paste the submission ID in step 4**:

1. Choose **Report a problem** from the Help menu
2. Click on the **Submit Logs** tab and verify that all the checkboxes are selected
3. Click on the **Submit Logs** button
4. Update this discussion to let us know that you've submitted your logs, and please note the submission ID at the bottom of the Submit Logs tab.


*****
** DNL: No content**

You submitted a support request to the Carbon Copy Cloner help desk with no content.

If you have a specific question or need support with Carbon Copy Cloner let us know.

The [Establishing an initial backup](https://bombich.com/kb/ccc5/how-set-up-your-first-backup) section of our [online documentation](https://bombich.com/kb/ccc5) will get you on your way.


*****
** DNL: License resend**

We re-sent your registration code via email. Please open the registration email on the computer with CCC installed, and click the button that says **Apply Settings**.

**Note: Your registration code is tied to the name and email provided when the license was purchased. Your email and name must exactly match the settings in your registration details or the license will show as invalid.**

Please let us know if these articles don't help you get registered:

- [Trouble Applying Your Registration Information?](https://bombich.com/kb/ccc5/trouble-applying-your-registration-information)
- [How to Register CCC in One Click](https://bombich.com/kb/ccc5/how-register-ccc-in-one-click)
- [How to Manually Enter a CCC Registration Code](https://bombich.com/kb/ccc5/how-manually-enter-ccc-registration-code)


*****
** DNL: TWO-WAY SYNC**

Being backup software, CCC has an edict to never modify the source, so bi-directional synchronization isn't functionality that we intend to pursue. There are lots of issues with a two-way sync that we would have to tackle, and that really starts to make the solution more complicated than what most people are looking for. There are several other solutions out there that provide this kind of functionality though.


*****
** DNL: Freeze**

In nearly all cases where a backup task stalls, or "hangs", the underlying cause is a hardware malfunction or an inability to read from or write to the media. While CCC can generally recover from unresponsive hardware, these underlying hardware problems occasionally affect the entire system's responsiveness as well. These problems are often frustrating, time consuming, and difficult to isolate, but we do have some procedures to try to isolate the problematic hardware component.

It's important to understand that individual applications can't stall the whole system -- Mac OS X was specifically designed to prevent that from being possible. A single application can do something that elicits that behavior (e.g. try to copy files to a particular device), but only software that runs in "kernel space" (kernel extensions, filesystem drivers and the kernel itself) can cause the entire system to become unresponsive or the dreaded kernel panic. In nearly all cases where a user reports "the system freezes", we find that there is a faulty piece of hardware at play.


*****
** DNL: Replacement drive will not boot**

We have received numerous reports of hardware compatibility issues when installing a cloned hard drive from an external enclosure into various Macs. Here are two related discussions (for background):

[Some MacBook Pros can boot from a disk in an enclosure, but not when it is installed internally] (https://bombich.com/kb/discussions/clone-boots-fine-externally...-everyt...)

[Some MacBook Pros can boot from a disk in an enclosure, but not when it is installed internally (asks to be reinitialized)] (https://bombich.com/kb/discussions/unable-boot-from-cloned-hitachi-hd-in...)

This workaround seems to work for most users:

1. Shut down your Mac
2. Install the new disk inside your Mac and put the original disk in your external enclosure
3. Boot your Mac from the original startup disk in the external enclosure -- hold down the Option key while booting your Mac to get to the startup disk selector screen
4. Re-initialize the new disk (in the partition tab -- reapply the "1 partition" scheme to the disk)
5. Create a Recovery HD on the new disk in CCC's Disk Center
6. Clone your original source volume to the new disk
7. Set the startup disk to the new disk in the Startup Disk preference pane and restart your Mac

Note: Step 4 is very important -- be sure to apply a new partition scheme to the disk, don't just erase the volume. This video indicates how to repartition the disk: https://youtu.be/PLrerqB-Hls


*****
** DNL: Remote mac older destination**

When using the **Remote Macintosh** option, the system requirements for the remote Mac are the same as for CCC running on the local Mac -- the system must be running Mac OS X 10.6 or later. Apple makes it exceedingly difficult, logistically, for us to build a binary that works on Tiger, Leopard, Snow Leopard, Lion, Mountain Lion, and Mavericks. The crux of the matter is that Apple made a significant filesystem change in Mountain Lion that can only be dealt with if we link CCC against libraries that are not available to Tiger and Leopard systems. If we don't link against these newer libraries, then we aren't making proper backups on Mountain Lion and Mavericks systems.

Rather than using the **Remote Macintosh** option in CCC's destination menu, we recommend instead that you enable File Sharing on your older Mac and back up to a disk image on the shared network volume. This section of CCC's documentation explains how to do this:

[I want to back up my whole Mac to a Time Capsule or other network volume] (https://bombich.com/kb/ccc4/i-want-back-up-my-whole-mac-time-capsule-nas...)


*****
** DNL: Manual update**

You can manually apply the CCC update with these steps:

1. Quit the older version of CCC if it is running
2. Move the older version of CCC to the Trash
3. Download the new version of CCC from here: https://bombich.com/software/download_ccc.php?v=latest
4. Move the new version to wherever you like. You don't have to keep it in the /Applications folder, you can keep it in a writable location, such as an "Applications" folder within your home folder.


*****
** DNL: DMG full**

You're running out of space on the mounted disk image's volume, not the underlying disk. CCC initially sets the capacity of your disk image to the amount of free space on the underlying disk. If you have freed up some space on that disk since you created the disk image, you can manually expand the capacity of a disk image in Disk Utility:

1. Eject the disk image's volume if it is mounted
2. Drag the disk image file into the pane on the left side of the Disk Utility window
3. Click on the disk image
4. Choose **Resize...** from the Images menu and expand as desired.