Thanks Adai. Would it be feasible to use a Provisioning Script to turn on compression when volumes are created? By "Provisioning Script" I mean create a script that could turn on compression of a volume then set the Provision Policy to call the script. I assume enough information is passed to those scripts so it would be possible to figure out what volume was just created.
Yes, you can do this in case of primary provisioning policy which has ability to run post provisioning script. But unfortunately secondary provisioning policy does not have the capability to invoke post provisioning script. I will add you to an internal email regarding the same.
There are post provisioning scripts you can assign to a storage service, but I have not used them. If a program provisions storage via APIs, it should be able to get the volume information and invoke ONTAP APIs to set compression.
Is enough information passed to the post provisioning script to ascertain the volume that was just created? I ask, because like you I haven't used the post provisioning scripts (yet). I seem to recall that information is passed via environment variables to the script. I just forget what all is passed. I guess I just need to start with a small script that simply does a 'set > \temp\env_var.txt' to see what is passed.
Will it confuse DFM if compression is turned on. I assume not, but I thought I'd ask.