HPE Storage Users Group

I suppose , when moving to 3.3.1, one can not use tunesys to move from normal cpg to cpg with compression and Dedupe enabeled. So one must use DO Or vmware vmotion?

Both compression and dedupe is set per VV and not on the CPG level. In 3.2.1 and 3.2.2, dedupe required a convert as the vv type was tdvv, not sure how this is with 3.3.1 as dedupe and compression are now features on a tpvv. Either way, changing these settings on a VV requires DO and a tunevv command per volume, or create all new volumes with the new settings and do vMotion.

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.

Capacity efficiency properties and hence conversion are on a per volume basis, you would need to tune these VV's or migrate to new VV's in a CPG created under 3.3.1 if you want to take advantage of compression. Savings can be estimated upfront with the checkvv command and there's a new ADR whitepaper that explains the process here :- http://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=a00006358enw