Began splitting clone from snapshot | NetApp | Page 1

Hi,
I have ontap NetApp device which is used to serve PersistentVolumes in Kubernetes with help of Trident CSI. We also using Commvault for backing up PersistentVolumes. Comvault makes a snapshot of the volume and then create a new volume out of the snapshot and mounting this new volume to a pod for backup. As per CommVault support no changes are done to the new volume during backup.

We've noticed that during backup of PVs of heavily loaded kubernetes cluster Trident is sending clone split command to Trident with corresponding record in logs: "Began splitting clone from snapshot".
There are no policies in Trident to split on clone creation and there are no such annotation activated.

Does anyone know why Trident splits the clone?
That causes a lot of problems as it is a lengthy procedure and causes a lot of issues.

Thanks 🙂

#Began splitting clone from snapshot