A customer enables Storage Efficiency on a volume, intending to use compression only as data is written. The customer observes that compression is working, but deduplication processes are still…

Post compression applies compression after data is written to disk rather than inline, which does not meet the requirement of compressing data as it is written.

Creating a custom efficiency policy attached to the SVM does not directly resolve the issue - the policy must be attached to the specific volume, and the SVM-level attachment does not prevent scheduled deduplication on existing volumes.

The default efficiency policy includes scheduled deduplication jobs, which is exactly the behavior the customer wants to eliminate.

The inline-only efficiency policy limits efficiency operations strictly to inline processing - data is compressed as it lands on disk without scheduling any background deduplication jobs. This is the only built-in policy that prevents the deduplication scheduler from activating while still allowing inline compression to function.