

After the deduplication has been applied, the original files are replaced by a pointer to the corresponding chunk in the SVI directory.

The NTFS deduplication segments files with fractionally equal content into so-called "chunks" which are moved into a the subfolder "System Volume Informaton\Dedup\ChunkStore\" (SVI) located on the corresponding NTFS partition. What is the reason for this? Answer / Solution A lot of files have a size of "0 Byte" while a folder called "System Volume Information" requires a huge amount of disk space. If the NTFS deduplication (available for Windows Server 2012 and higher) is enabled, TreeSize displays some strange values for the size of files and folders. NTFS Deduplication Sizes Question / Problem
