Another day another problem, K10 (latest version) up against vsphere 8 cannot remove snapshots and therefore not comply with polices, so it will fill up your storage fast - in our case 3tb+ per day snapshots, despite having a limit of one. We had our fill of this garbage software - ciao, not sure if veeam/kasten or vmware fcd is worse, but pure garbage - never count on it in production… even deleting restore points in k10 never deletes snapshots in vmware (those that should never have been there in the first place). What a waste of time.
+22I understand you might be frustrated but you have not said whether Veeam Kasten support tried to help or what steps were taken. Can you describe you Storage Class for us. Also what type of cluster are you running Tanzu? or something else just leveraging the vsphere csi.
Either way if you could post some details I am sure people will try to help out.
VMCA2024, VMCE2023, VMCE2024-SP,CKA, LFCS, PCA,TARS
1 person likes this
Geoff Burke wrote:
I understand you might be frustrated but you have not said whether Veeam Kasten support tried to help or what steps were taken. Can you describe you Storage Class for us. Also what type of cluster are you running Tanzu? or something else just leveraging the vsphere csi.
Either way if you could post some details I am sure people will try to help out.
Sure, vanilla k8s - 1.28-1.29 multiple clusters, vcenter 8x underlying esxi 8x as well. Storage class vsphere csi (latest).. etc. I wish I had a week or two to spare, but I don’t, I have to find FCD’s with orphaned snapshots instead… this is not the first time k10 didn’t perform as configured, but it’s the last time for sure. It was deleted today.
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.