shankarsingh
Enthusiast
Enthusiast

Hello,

 

Finally we logged case with Vmware Support and they said that

 

- We have confirmed that this is a normal behavior when using cluster prior to 7.0 Update 2.

- This is a new data service policy only supported with 7.0 U2 clusters and we have explicit check to prevent it to be used in 7.0 U1 clusters by returning incompatible status for 7.0 U1 cluster backed vSAN datastore.

- You should not use any policy containing encryption or space efficiency settings for cluster prior to 7.0 Update 2.

- In case of using ESXi 7.0 U1, we recommend to leave the encryption and space efficiency setting in storage rules tab as 'No Preference' and the deduplication/compression option will be normally working as expected.

 

Hope it helps you .