Skip to main content
NetApp Stage KB

How to setup regular CSI snapshots on Trident provided PV ONTAP volumes

Last Updated:

Applies to

Astra Trident for Kubernetes and Openshift


Since Trident itself only has the option to choose an ONTAP-defines Snapshot schedule, CSI supported snapshots can only be done through additional software:
  • Astra Control Center (ACC) and the "in the cloud" version called Astra Control Service (ACS) provide the possibility to create scheduled CSI-Snapshot backups on the provided PVs, including the option to transfer to a mirror or vault destination, and create a PVC of a Snapshot, or even a pod clone.
  • Third party backup software can also run scheduled backups of Trident PVs, usually by creating a CSI-Snapshot, creating a PVC from that Snapshot, mounting it, and backing up the content to elsewhere (disk or tape based). These usually clean up the mounted PVC and the CSI-snapshot afterwards, not blocking PVC deletion when no longer used.

Additional Information

Using CSI Snapshots has a number of restrictions to be kept in mind:
  • CSI Snapshots do not work on the ONTAP SAN or NAS economy drivers, since the snapshots are volume-wide, not restricted to qtrees
  • the existance of CSI Snapshots block the removal of the PVC until the CSI Snapshots are removed
  • creation of PVCs from the CSI Snapshot (implemented as flexvol clones) will block the removal of CSI based Snapshot as well
In comparison ONTAP scheduled Snapshots do not block PVC deletion, which means they can provide protection when using NFS (ontap-nas[-economy]) drivers in the backend. However, the same restriction exists when creating flexc lones: they will block the snapshot deletion from the scheduler.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.