
In terms of the image size being different from the "Total selected", it's because Reflect defaults to Medium compression, and that image file size based on that amount of data being backed up seems about right to me.

This routine also occurs for rollback files for monthly Windows updates, which are also getting quite large. For example, if you updated to a newer Windows 10 build somewhat recently, the files needed to roll back to the previous version are kept for a while and eventually purged in the background. Windows is constantly accumulating new data, updating caches, purging stale data, etc., and that background activity can result in a significant net change to data. If the SSD contains an operating system, there's no way that nothing changed between last August and now. If Reflect isn't throwing any errors, nothing is wrong.
