On a 2012 Standard server, I have deduplication turned on for a data volume. Several directories are set up as exclusions in dedup settings, so there are only 2 directories which should be getting deduplicated. (And one of those is a running VM which should have been excluded, but looks like it got missed.)
The other directory targeted for dedup contains Veeam backup files of several Hyper-V VM's. When I look at the properties of this volume (Drive D:), I see 0.98TB used, 1.28TB Free, with a capacity of 2.27TB.
If I select all of the folders on the drive except the 2 that are being deduplicated and pull up the properties window, it shows size: 24.4GB, and size on disk: 24.4GB. Even the folder with the running VM shows both the size and size on disk as 45.0GB.
So far, those numbers make sense to me. But when I pull up the properties of the "D:\Backups" folder, it shows Size: 1.38TB, and Size on disk: 36.7GB. While I know server 2012 deduplication is good, those numbers don't seem right. Then, going a step further, I pulled up properties of some individual files inside the D:\Backups directory. The files in that directory vary in size, anywhere from 5GB to 600GB, but all show a size on disk of 4.00kb. (Except the newest backup, which hasn't been through a dedup cycle yet, so it still shows the full size and size on disk as the same.)
Is it expected that all files which have been deduplicated would show a size on disk of just 4k?
What numbers should I believe when it comes to file sizes and disk utilization? The file size numbers just don't add up, but are the used/free space numbers correct as shown in the volume properties?
Thanks!