Why did using Carbon Copy Cloner trigger a huge Time Machine backup?

[AllGold]

I got tired of the crapshow that is Apple's Disk Utility beyond Mavericks so I downloaded the latest version of CCC to make a clone of my APFS boot drive. Just a one-time manual clone.

Now Time Machine thinks pretty much everything on my boot drive needs to be backed up. Is CCC to blame for this? How? Why?

I couldn't find anything like this problem in an online search.

[anonymouse1]

Is your new clone excluded from Time Machine? Is it trying to back up your clone?

[AllGold]

anonymouse1 wrote:
Is your new clone excluded from Time Machine? Is it trying to back up your clone?

I've made that mistake before but not this time. I triple checked and everything that is supposed to be excluded is. Besides, the clone was to an external drive that hasn't been connected since (and it was excluded at the time).

You know, that makes me wonder if maybe CCC confused TM to think the clone is my original drive and now the original drive is something new that needs a full backup. Probably not because TM still sees all the previous backups of the original.

[p8712]

All the modified dates changed?

[Filliam H. Muffman]

Maybe CCC set it's own flag for everything that had been cloned (didn't preserve extended attributes?) and it triggered Time Machine to make a new complete backup. I would send Bombich.com a question about making a clone without triggering Time Machine flags.

*edit