So, 48848 CBT blocks of 524288 bytes size indeed makes up 23.9 GB of data, it appears correct.[26.05.2015 18:02:52] < 9904> dsk| Initializing swap CTK filter for disk 'VDDK:[datastore1] VM/VM01.vmdk'. Std. block size: '524288'.
[26.05.2015 18:12:26] < 17308> dsk| vSphere CTK cursor reached EOF.  blocks were reported as updated.
Since actual modified files at the end of days was about 2 GB, how come CBT detects so many changed blocks?
Realizing this is not a Veeam question but someone in here might have a clue on why this occurs and how to minimize this.
I have two main suspects:
Microsoft Word periodically autosaving, meaning it creates a new file on a new block and deletes the old one.
Group Policies pushing out Internet Explorer favorites with the Replace option. 10 shortcuts and 100 clients updating every 90 minutes in an average of 8 hours workday would alone give 5000 updates.