Trident with Commvault backups triggers unexpected clone splits in ONTAP
Applies to
- NetApp ONTAP
- NetApp Trident 24.10 or higher
- OpenShift
- Commvault backup integration
Issue
- Snapshots are automatically being split despite the annotation of
splitOnClone=falseset in the StorageClass or the Backend. - Clone splits are being aborted
- Clones are being left in an offline state in ONTAP
- PVC's are left in a
TerminatingorDeleted Releasedstate - Trident controller restarts during the period of scheduled backups
