#Change Trident Volume Snapshot Policy

1 messages · Page 1 of 1 (latest)

timber hawk
#

Hello,
I have a PVC created by Trident that is using the default ONTAP snapshot policy. This policy is defined in the TridnetBackend (ex: snapshotPolicy: default).

If I create a new ONTAP snapshot policy, is there some way to apply the new snapshot policy to the volume? If this is done inside ONTAP directly on the volume, will Trident overwrite that change?

gilded glen
#

The tridentvolume CR holds the information of what snapshot policy was used when the PVC was created. But editng the snapshot policy in ONTAP doesn't seem to stop the volume from changing nodes when the pod is moved. And changing nodes does not change the snapshot policy on ONTAP or the tridentvolume CR, so there is a mis-match there.
All in all, you should be able to get away with it, but more testing would be needed to know if it is a functional change or if there is a point at which it causes problems.

gilded glen
#

Changing the policy in the backend doesn't change the snapshotPolicy in the tridentvolume CR either. Even after the pvc is moved to a different node.

timber hawk
#

Thanks Scott. I also tried this out this morning and found the same.
I think changing the policy on the volume directly in ONTAP should be fine, but what would you reccomend?

gilded glen
#

It's technically not supported and I work in support, so I was avoiding making any recommendations.