That is a *very* impressive dedupe savings, from 112GB to 26.3MB, something 
like a 98% savings. While dedupe is a nice feature, I've never seen anything 
close to that kind of savings, especially on photos (I assume .JPG). I'd try to 
copy them to a non deduped volume and see what you get there.

...Tim

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kuhlman, Donald
Sent: Thursday, October 30, 2014 11:28 AM
To: [email protected]
Subject: RE: [NTSysADM] Size on Disk HUGE discrepancy

Could the new server possibly have DeDuplication running causing it to report 
the De-Duped size on the disk?

See below - 
https://social.technet.microsoft.com/Forums/en-US/fa6f6329-f710-4c5e-9538-942045df68a3/windows-server-2012-with-deduplication-show-wrong-size-on-disk?forum=winserver8gen

Running 2012 server with deduplicated volume (performed by windows server).
Volumesize is 5 TB, free space is 2,2 TB, reported Dedupliction rate is 47%. 
This I believe is correct.
However the properties for the only folder on the drive reports:
Size:              5,31 TB (5.848.049.807.909 bytes)
Size on disk:  90,7 GB (97.404.194.816 bytes)
Contains:       1.215.797 Files, 52.169 Folders
There are only one folder in the root of the volume, why it's not just files 
that already resides in other folders on the volume.
Individual folders shows correct values just after they are copied to the 
volume, but after deduplication is run (and the retention period for the files 
has passed), Size on disk shows as very small.


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of J- P
Sent: Thursday, October 30, 2014 1:15 PM
To: NT
Subject: [NTSysADM] Size on Disk HUGE discrepancy

Hi all,

this may seem trivial ,however, this particular situation has me concerned;

We have a photo archive that's been around for about 15 years- it started on a 
2k server, moved to a 2003,2008 and now its on a 2012r2 server.

I know the norm is that the "size on disk" would be a bit bigger than "size" 
due to file system, cluster size etc..
but in this case its the reverse, and by A LOT, and NO, compression is not 
enabled

The directory 112 Gb, and contains 20,029 files and 414 folders, now size on 
disk only reports 26.3 MB (27,607,040 bytes) thats MEGS, NOT GIGS

Is this something to be alarmed with?




Reply via email to