Hi Again Hendersond,
I'm not sure if my math is 100% correct here, but its not far from it.
Total volume usage - Snapshot Usage = Live Data
Dedupe Savings / (Live Data + Dedupe Savings) = Dedupe ratio excluding snapshots
For you:
1068 - 773 = 295
244 / (295 + 244) = 45.2% saved
The 19% you're seeing is based off of the 244GB of savings on 539GB of live data with an overhead of the snapshots 773GB (and for some reason it treats the snapshots as undeduped, when in reality they probably *are* deduped). If we factor snapshots into the above equation: 244 / (295+244+773) we get 19% after rounding.
We actually just noticed this with our DFM provisioning manager, whereas the CLI shows the dedupe saving including snapshots as just used storage, DFM seems to exclude snapshots from its computations. Our VSphere volume is ~42% saved in the CLI in DFM its abou 52% ( we have a very short backup schedule)
If you really want to tell, delete your snapshots(prolly not a good idea though). Alternatively, just try deleting a number of snapshots off the tail end (such as all of november if you don't need them). This might give you an idea of how the dedupe % will fluctuate.
Long story short, its a bit of bad math in df -s in combination with your snapshots.
I hope we've answered the conundrum at this point. If you still have problems our questions, let us know.
Best Regards,
Adam S.