
With that in mind, you will not want to let this application out of your hands and into the hands of your end users. In the hands of the wrong user, WinDirStat could easily help someone delete precious system files that would render the machine unbootable. The other issue isn't really a product of WinDirStat, but of possible user error. The minute you try to create your own user-configured cleanup routines you will quickly experience a complete lack of documentation, which makes the task rather challenging, if not impossible. The biggest issue with WinDirStat is the documentation.

I could have simply dug around the hard drive and checked every file for size and tracked them with a spreadsheet. With that choice in hand, I had an obvious task - find out what types of files were causing the backup to grow so large. The obvious choice (for the client) was to weed out files that were taking up too much space.

The client had two choices, get a larger external drive or reduce the number of files included in the backup. In some instances that may be a fine backup solution, but this particular client wanted to have multiple backups saved.

As you can imagine, Acronis was only allowing us to fit a single backup on their 500GB external drive. Recently I had a client whose file backup had reached over 400GB.
