Deduplication and Provisioning Recommendation

[RYVN]

Hello,

I am looking for some direction regarding provisioning at the VMware level with a De-duplicated LUN on the array level. Currently, we have a de-duplicated thin provisioned LUN on our VNX5200. We will be adding this LUN to VMware as a data store which in turn will be added as additional hard disks to one of our existing VM's to house file shares. I am fairly green in this arena, so my question is: is it recommended to also thin provision on the VMware level and over provision the datastore in order to best realize de-duplicated space at the array level?

Thanks for any direction you can provide!

[bl0ckh3ad]

What you explaining is thin-on-thin and dedupe! So fairly risky to be honest.

https://urldefense.proofpoint.com/v1/url?u=http://www.journeytothecloud.com/virtualization/thin-on-t...

I would think of it link the recession banking crisis. All the banks think provisioned out their loans, and so did their lenders. Then all the money was required back at the same time = boom.

So if you had over provisioned a bunch of vm’s and for some reason they all did a massive amount write IO’s, you potentially could be in a very bad palace, and throwing dedupe in there as well would make me feel uncomfortable.

However, features are there so can be used - And also ensure you have a rock solid backup strategy just in case it all goes pear shaped.