Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 7579

Deduplication: how to identify which files are "in-policy" (and which are not)?

$
0
0

Dear experts,

in eventlog I find the following information for one of my deduplicated volumes:

Volume: F: (\\?\Volume{9794e270-fb08-487e-979b-8a08fa9ca311}\)
Error code: 0x0
Error message:
Savings rate: 24
Saved space: 853327714684
Volume used space: 2681869406208
Volume free space: 66771247104
Optimized file count: 1199618
In-policy file count: 1188049
Job processed space (bytes): 0
Job elapsed time (seconds): 2
Job throughput (MB/second): 0

Some things look strange to me: 
- The savings rate is only 24% which looks odd because I get about 40% on other file shares with similar characteristics.
- The "Optimized file count" is higher than the "in-policy" file count.
- The volume has about 3.5 million files but only 1.1 million files are "in-policy".

My understanding of "in-policy" files is that all files are in-policy which are older than 3 days (if not configured different, which is not the case) and which are not contained in an excluded folder (nothing configured here) and which have no excluded file extension (nothing configured here apart from the default). Right?

I'm sure that only a small fraction of the files on this volume are younger than three days, so something seems to be wrong there, but I have no idea how to find the cause of the problem.
Is there any way to identify the files (full path) which are considered to be not "in-policy"?
How can I find out if the optimization process really looks at all files - and doesn't skip a million?

Thanks!

Regards
Christoph


Viewing all articles
Browse latest Browse all 7579

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>