FAQs & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: TreeSize | Show all categories

TreeSize is basically designed to visualize the current state of your storage, but it can also compare these results with previously exported ones to calculate the changes inbetween.

If you want to automatize this in TreeSize, you would need to write a batch file that does:

  1. Perform the scan of the path and export the scan to an XML file using the /XML command line parameter.
  2. Perform a compare of the scan from the step before with a previous one, using the command line parameter /COMPARE and export the results in an appropriate format
  3. Replace the XML file that represents an older scan with the current one, so that it can be used for the next run.

A batch file for drive D:\ could look like this:

START /WAIT "TreeSize" Treesize.EXE /XML "C:\New_D.XML" D:\
START /WAIT "TreeSize" Treesize.EXE /OPEN "C:\New_D.XML" /COMPARE "C:\Old_D.XML" /HTML "C:\Compared_D.html"
DEL "C:\Old_D.XML"
MOVE "C:\New_D.XML" "C:\Old_D.XML"

Our disk space manager SpaceObServer offers features like this out-of-the box, as it stores historic disk space data in a SQL database.

This problem is unfortunately caused by SharePoint itself.

SharePoint throttles the number of user actions for very large requests. This leads to the fact that TreeSize has to pause the scan after a certain number of calls for a short time (40 to 300 seconds) until new user requests are released.
If SharePoint interrupts the active scan due to too many calls, a message is written in the Windows Event Viewer that refers to the throttling.

To speed up or not unnecessarily slow down a scan, unused statistics (esp. the statistics on file owners and the option to 'Track advanced file system features') should be deactivated.

As an alternative, SpaceObServer may be interesting for you, as it also supports SharePoint scans. Due to the database used to persist the scan results, the data collecting process, and the reporting/analysis can be split up into two independed steps. Let the scan-service wait, instead of waiting yourself.

We discussed this behavior with several NAS vendors, who agreed that this is an issue with the SMB implementation of the specific NAS system.

Please check if their is an update available for your NAS and if it resolves this issue for you. If not, please contact the vendor of your NAS system and ask him to fix this behavior.

As a workaround in TreeSize, you can activate a legacy mode, where TreeSize would estimate the allocated values based on the sizes. To do so, please start TreeSize with parameter /UseLegacyEnumerator True

When deduplicating files, TreeSize replaces duplicate files by hard links, after which the physical data exists only once on the hard disk. There are however X links to this data. Each of these links is shown with the size of the physical data, this is why the Windows Explorer and by default also TreeSize shows the same size for these files and the folders they are included in.

If you take a look at the allocated space of the physical drive (e.g. in the "Drive List" in TreeSize or in the "Properties" of the drive in the Windows Explorer) you will notice the difference.

To get the correct physically allocated size of a folder, you need to look at the column "Allocated Space". In the TreeSize main application make sure that the option "Track NTFS alternate data streams and NTFS hardlinks" is turned on in the Options dialog.

Open the TreeSize File search using the Windows Start menu or the TreeSize Tools menu, add the network paths to the list of paths to Search, activate the Duplicate Search only and start the search. You may change the way TreeSize compares the files on the "Duplicate Files" tab.