Cleanup Tool reports wrong backup size with differential backup:
Hi all,
I found an old forum post with a similar problem, but it sounded to me as if it should be fixed by now - unfortunately that is not the case.
You can see the correct file size here: 106,5 MB.
(Sorry that the output is in German - anyway, only the numbers are relevant)
However the Cleanup Tool reports 32,2 GB instead:
(The time stamp of the 1st full backup is also incorrect btw, the actual file has 10:09 as its modification time)
Regards,
Oliver


- Log in to post comments

Oliver,
I believe your difference in file size is because you are looking at two different file types (methods). The file on 09/04/2020 is a Complete or Full in english type backup file meaning that all data selected was backed up. In this case 194.7GB compressed to 162.5GB.
The file created on 10/04/2020 is a Differential type backup meaning that all data that is different from that of the previous Full backup was backed up. In this case 32.2GB.
This is normal behavior for the application. This is not the same as cleanup of a task.
- Log in to post comments

Thanks!
@Enchantech,
it is not about the difference in size between the Full and Differential Backup, but about the size shown for the same Differential Backup. The actual size of the .tibx file for the Differential Backup is 106,5 MB (there were no changes between the 2 backups, so the difference is very small) and this correctly reflected in the Activity Report. Still, Cleanup Tool shows a file size of more than 32 GB, which simply is not there.
Also the difference in file size is much much larger than what Steve experiences.
- Log in to post comments

Oliver,
Okay, I see what you mean there. I cannot say definitively of course but I would suspect that the 32.2GB reported in the Clean up tool could be the total amount of data changed by cleanup whereas the 106.5MB is the actual size of the most recent differential backup file.
In my experience with the clean up tool, that tool runs against the entire backup and effectively consolidates all data. Given in your example a full months time has passed between the entries you report the 32.2GB number although large may well be in order of a bit over 1GB of change per day.
As Steve says we have no firm understanding of what's being reported.
- Log in to post comments

Hello Everyone,
I've checked our internal sources - looks like the issue with the incorrect size calculation is still present (affects TIBX archives with full and incrementals).
- Log in to post comments