If you've ever used CCC's default option to archive items on the
destination, then there should be a _CCC Archives folder at the
root level of the destination. CCC specifically protects that
folder and manages it a bit differently. You can drag it to the
Trash, then empty the Trash to verify whether that is the culprit.
CCC also does not delete items that are excluded by default, so if
anything is excluded from the backup task, those items will be
protected from deletion on the destination. You can modify this
behavior, but if you're not excluding anything, the only items of
note would be the Trash and any Time Machine backups on the
If you've emptied the Trash and there is no TM backup on the
destination volume, and the discrepancy still exists, we can get to
the bottom of it using a tool available at the bottom of this
section of CCC's documentation:
3 Posted by Elliot Fisher on 05 Sep, 2012 05:18 AM
I can't articulate my awe of your speed and thoroughness in
dealing with user support; cheers.
I have never used CCC's archive default: the _CCC Archives
folder is not present on the destination.
Nothing is excluded from the backup, that I can tell, and I have
no Time Machine backups on the destination.
I ran the script and found that the largest discrepancy was that
the destination's user folder is 243Gb larger than the source's.
There were other minor (in terms of size) differences, but nothing
to sneeze at. The implication here is that CCC is copying new or
altered files and deleting nothing - thus creating a backup of
everything that is currently on my iMac, and of everything that has
ever been on my iMac. The question is why...
6 Posted by Elliot Fisher on 05 Sep, 2012 06:11 PM
Done and done. I just submitted the log, CCC Report ID: 11578.
The last couple backups I ran were experimental - me playing with
settings to see if I could resolve the issue - all to no avail.
Also: I've been getting an error message (see attachment) at the
end of every backup. Could this be causing/contributing to the
7 Posted by Elliot Fisher on 05 Sep, 2012 09:01 PM
It also may not be completely obvious from the logs, but my
holistic backup scheme is as follows:
I have a 2Tb external volume that I have partitioned into two
1Tb destinations; the first is for backing up my iMac, the second
is for backing up another 1Tb external. Backups have been running
daily for a long while.
The problem I have described above exists on both
When CCC detects media problems on the source or destination, it
makes the very conservative decision to cease making any deletions
on the destination. It may seem trivial in this case, but imagine
if unreadable files were discovered on the source, but CCC decided
to proceed with deletions on the destination anyway. At the end of
the backup, you could end up with unreadable files on the source
and no backup at all of those files on the destination. One might
argue, "Why not just avoid deleting the files that had media
errors?", but filesystem problems are rarely that cut-and-dry.
Fortunately, this is super easy to fix. Delete this file from
the source volume and re-run the backup task: