While rebuilding my Windows 10 install, I decided to switch from CS6/Legacy plug-ins to the Topaz suite of software. As part of the rebuild process, each time I do a major install or change, I perform an incremental backup (using Macrium Reflect 8) and then tag the incremental with what was changed.
Once I had the incremental for all the Topaz software installs, I then started each tool, activated it, and then exited. I then performed another incremental backup to catpure the activations, and the incremental file size was 19GB! I was stunned.
Thinking I had done the incremental incorrectly, I simply started Topaz Studio 2 again, exited, and then ran another incremental. 18.5GB!
What is Topaz Studio 2 changing on the disk that is causing such a massive differential in my backup software? That’s almost a full third of the full backup of the entire system. Is there any way to avoid this?
As it turns out, I think the reason I saw this occur was because I was doing a new Windows 10 install. I think the Windows 10 update system had downloaded more updates in the background while I was installing and running Topaz, and I associated the disk-usage increase with Topaz.
My next boot of the new operating system presented me with an update to install. I think that update was being placed on the disk at the same time as Topaz. I think this also explains why I had trouble reproducing it afterward.