Hello It-Prooffice,

This could be due to possible a cleanup process when the policies are running. I recommend deleting all the backup pods and verifying that no PV are also left over attached to these pods. Lastly, I recommend updating your K10 instance to the latest version and rerun the policy and verify if any backup pods are being left behind.

Thanks

Emmanuel

@It-Prooffice , Backup-data-stats pods get created when a backup/export completes or the dashboardbff restarts to calculate the storage consumed in the object store that is shown in the Usage & Reports card in the UI.

It should be a quick action and shouldn’t be stuck running unless there is an issue. These pods that are there in your K10 namespace are stale and can be deleted without any issues as of now.

However, We should probably try to dig in more if this continues for each backup-data-stats pod.