VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
dears,we have an env where there 2 CSI drivers, ebs-aws that support volumesnapshot, and efs that does not.all pods and data are stored on ebs-aws, the pods on ebs generates a continuous logs and all are stored on EFS and saved as files. the question is, when we run the backup for the applications on ebs, the logs stored on EFS will be backed up and all are protected? or there is additional tasks to do?
Hello!I am testing Kasten 6.5.12 in my EKS v1.29.1-eks-b9c9ed7 environment and I need some help:My app has 2 PVCs: ebs-claim (ebs-sc provisioner ebs.csi.aws.com) and efs-claim (efs-sc provisioner efs.csi.aws.com)When I exclude EFS efs-claim from the policy it runs, and it exports the backup to my S3 Bucket.So EBS snapshot is working fine, but when it tries to backup EFS I get the following error: Error details: - cause: cause: cause: cause: cause: fields: - name: storageClassName value: efs-sc file: kasten.io/k10/kio/kube/volume.go:659 function: kasten.io/k10/kio/kube.CreatePVandPVCClone linenumber: 659 message: Unsupported storageclass for pv/pvc clone file: kasten.io/k10/kio/exec/phases/phase/data_manager.go:176 function: kasten.io/k10/kio/exec/phases/phase.(*SharedVolumeSnapshotManager).SnapshotCreate linenumber: 176 message: Failed to clone
good day, I’m working with some people in implementing K10 on OSCP clusters.They have and use DataDomain as backup storage: with Veeam we naturally use DDboost, and we are trying to use it for K10 exports too.We created the PVC and configured as Location in K10, the validation succeeded, but it does not work, it seems the pod cannot mount the nfs export and the export operation timeouts.We have found this errorI tried opening the export to all the internal IPs, but it did not solve the issue.It seems a network issue anyway … has anyone experience on this task? Thanks a lot in advance
we got Volume Snapshots are not supported for this storage when try backup vault in Openshift 4.14 using Kasten k10 operator. Just wonder: how to enable injectKanisterSidecar in k10 operator?
Hi,I testing Kasten K10 in a new installed AWS EKS cluster using k8s 1.29, so I follow the latest documentation and installing using helm and the extra set parameters secrets.awsAccessKeyId and secrets.awsSecretAccessKey.Almost all Pods comes up and PVC accept one pod and PVC that is catalog-svc. When I do a kubectl logs -n kasten-io <PODNAME> --all-containers=true it give me nothing, but if I do a describe on the pod it doesn’t give me a lot of information. Containers: catalog-svc: Image: gcr.io/kasten-images/catalog:6.5.10 Port: 8000/TCP Host Port: 0/TCP Requests: cpu: 200m memory: 780Mi Liveness: http-get http://:8000/v0/healthz delay=300s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:8000/v0/healthz delay=3s timeout=1s period=10s #success=1 #failure=3 Environment: AWS_ACCESS_KEY_ID: <set to the key 'aws_access_key_id' in secret 'aws-creds'> Optional:
Hi there,We have an Elasticsearch application consisting of 3 nodes; each node is placed on a different host and has a separate PV bound. We’re using the following:Helm Chart to deploy the ES cluster: https://artifacthub.io/packages/helm/elastic/elasticsearch/7.16.3, K10 version is 6.5.1 the storageclass for PV provisioning is local-path-provisioner: https://github.com/rancher/local-path-provisioner (we’re not using CSI) Kubernetes 1.24 (RKE2 Distro)The Kanister Blueprint has been written to deal with the backup & restore of the ES app. The backup runs successfully, but when we want to perform a restore, the following problem occurs - executing a data-only or full restore - neither of them seems to work. The statefulset is scaled to 0, and the PVCs are deleted and recreated, but they are placed on the same host, which prevents the pod from being scheduled, since the pod anti-affinity rules cannot be fulfilled - pods would have to be scheduled on the same host.Is it possible to alte
The Kasten K10 documentation suggests that the K10 operator is available to install directly from the Red Hat OperatorHub on OpenShift, but we can’t seem to find it in our OpenShift installation, nor could we find it in the Kubernetes OperatorHub.io community operators. Is the latest Kasten K10 6.5 supposed to be available on OperatorHub, or has it been unpublished as of late?
Hi! I’m using a NFS share for K10 DR. The retention policy in the DR policy was changed to only keep 1 hourly version. Therfore only one version should be kept. It looks liket the old version get retired. But the space on the nfs volume isn’t freed up. Also the usage report shows that the storage is in use by kasten-io. What can I do to free up the space? Is there any manual disk space reaclaim job which needs to be run?
Hi Team,We faced issue when enable export backup to S3 compatible, the snapshot is completed and success but export phase failed.phases: - attempt: 3 endTime: 2023-11-27T04:03:08Z errors: - cause: '{"cause":{"cause":{"cause":{"cause":{"message":"Failed to exec command in pod: command terminated with exit code 1"},"message":"Access Denied"},"file":"kasten.io/k10/kio/kopia/repository.go:650","function":"kasten.io/k10/kio/kopia.ConnectToKopiaRepository","linenumber":650,"message":"Failed to connect to the backup repository"},"fields":[{"name":"appNamespace","value":"frontpage-ops"}],"file":"kasten.io/k10/kio/exec/phases/phase/export.go:266","function":"kasten.io/k10/kio/exec/phases/phase.prepareKopiaRepoIfExportingData","linenumber":266,"message":"Failed to create Kopia repository for data export"},"file":"kasten.io/k10/kio/exec/phases/phase/export.go:168","function":"kasten.io/k10/kio/exec/phases/phase.(*exportRestorePoint
Hello,I have installed Kasten v6.0.7 with Helm Chart.I use the air gap installation for pull images in local repository with this config :global: image: registry: <private_repository>:<port> repository: kasten-images pullPolicy: IfNotPresent airgapped: repository: <private_repository>:<port>/kasten-images pullPolicy: IfNotPresentandkanisterToolsImage: registry: <private_repository>:<port> repository: kanisterio image: kanister-tools pullPolicy: IfNotPresent It works for all images exept one : ghcr.io/kanisterio/kanister-kubectl-1.18I have this error events :55s (x4 over 2m23s) Normal Pulling Pod/kanister-job-bzts6 Pulling image "ghcr.io/kanisterio/kanister-kubectl-1.18:0.96.0"46s (x4 over 2m15s) Normal Pulling Pod/kanister-job-fwwp7 Pulling image "ghcr.io/kanisterio/kanister-kubectl-1.18:0.96.0"4
Hello Everybody, I am new to Kasten K10 and trying to understand the snapshot retention. Below is one of the policies I’ve created.It takes daily backup of a K8s application.I need help understanding what exactly does 31 daily, 10 weekly, 12 monthly and 7 yearly snapshots retention mean.And this is what I see when I get into the restore points:And what should the settings be to retain backups/snapshots of last 1 month (30 or 31 days), and one snapshot per month for the last one year. So, for example today’s date is Oct 2nd, so daily snapshots from Sep 2nd till today and 1 monthly snapshot from Sep 2022 till Sep 2023. This is just an example, I know it depends on the snapshots Kasten has already taken. But, I want to achieve this.
We have hundreds of kanister-job-* pods in our kasten namespace that are in state phase “Succeeded” but are never deleted.$ kubectl get pod --namespace kasten-io --field-selector status.phase=Succeeded|wc -l355 Here is the status of one of the jobs:status: phase: Succeeded conditions: - type: Initialized status: 'True' lastProbeTime: null lastTransitionTime: '2023-06-04T15:11:22Z' reason: PodCompleted - type: Ready status: 'False' lastProbeTime: null lastTransitionTime: '2023-06-04T15:11:22Z' reason: PodCompleted - type: ContainersReady status: 'False' lastProbeTime: null lastTransitionTime: '2023-06-04T15:11:22Z' reason: PodCompleted - type: PodScheduled status: 'True' lastProbeTime: null lastTransitionTime: '2023-06-04T15:11:22Z'The Log of the Kanister-SVC-Pod shows the following messages for this pod:Failed to delete pod - an empty namespace may not be set when a resource name is provided{ "Act
im seeing alot of these errors on my kube-system api servers ive tried delete api-resouce/crd remove helm install re-installalso tried run the shell script from k10 to verify all is good also aggreation layer and comes out with all OKbeen having this issue past 2 years now, would like to get it away :) im using 1.26 which also passes but been having this issue since foreever 1.19/20/21/22/23/24/25 → 1.26 (current) ive been trying to find similar issues on this board and on redit google facebook, tried every single “solution” but nothing seems to help, what am i missing out =?
I have installed k10 in a vCluster environment which has k3s as k8s distribution.k8s version: 1.23.5+k3s1kasten version: 6.0.1When I run the policy for backing up the namespace. My backup policy creates volumesnapshots suceessfully but it is failing at the Export restoringpoint phase with the folllowing error.I have run the k10 primer tool it has all checks ok. Below is the output.@WDX5VBJHW32 MINGW64 ~$ curl -s https://docs.kasten.io/tools/k10_primer.sh | bashNamespace option not provided, using default namespaceChecking for tools --> Found kubectl --> Found helm --> Found jqChecking if the Kasten Helm repo is present --> The Kasten Helm repo was foundChecking for required Helm version (>= v3.0.0) --> No Tiller needed with Helm v3.12.0K10Primer image --> Using Image (gcr.io/kasten-images/k10tools:6.0.1) to run testChecking access to the Kubernetes context --> Able to access the default Kubernetes namespaceK10 Kanister tools image --> Using Kanister tools
hi My client is a member of tkgm's guest cluster.want to do backup and recovery. I want to migrate from Cluster A to Cluster B. When performing a backupThe VMware CSI driver does not support Volumesnapshot because the current host version is 7.0.3. Therefore, the VMware infra profile is registered, and snapshots and exports are performed through the VADP api. When recovering exported data to another cluster like the picture belowWhen the message occurs, the pvc recovery fails. I understand that the generic volume shown in the capture means the general volume. Why does this message occur? Is it because it is restored like a sidecar method rather than using VADP.api when performing restoration? I would like to know the exact backup recovery logic for VMware tanzu.
Hi, We have just upgraded our Kasten K10 multi-cluster environment to 5.5.8, and now some clusters say they don’t have license.For upgrading we used this guide:Upgrading — K10 5.5.8 documentation (kasten.io)New License Management feature:License Management — K10 5.5.8 documentation (kasten.io)All our clusters have less then 5 nodes individually, and previously all were counted individually from their 5 free local license pool. So everything was fine up until now. But after upgrading, now all the secondary clusters display the “default” 5 node starter-license (starter-4f1842c0-0745-41a5-aaa7-a01d748b1c30) as Duplicate, so they don’t contribute to the global mc pool, and also don’t have valid local license either (probably because of the “Duplicate” status).Does this mean that the licensing terms have also changed by this version? And now we have to count licenses globally (in a multi-cluster scenario), and not Per Cluster?(These clusters are for different small tenants actually, so they
Hello Team, We notice a lot of stale pods (created on a random date in previous months of Jan, Feb and March) with the name ‘backup-data-stats-*’ and stale secrets (again created in previous months) ‘k10-content-store-passphrase-*’ in kasten namespace. Is this a normal behaviour? Do we have to do some regular clean up for kasten namespaces? Thanks.Arun PrasadKasten version 4.5.3 Kubernetes Version v1.21.6+c180a7c Kubernetes Release Type OpenShift
Hey all!I have a k10 setup and have successfully created and restored from snapshot backups in the same cluster. I have also successfully exported the restore points to the bucket, but pulling them from the new cluster I am getting this error about the kopia manifests. The s3 bucket back-end is a ceph cluster, and both clusters are connected to the same buckets. The decryption key lets me proceed with the import policy and runs it, so it seems like it can see it. I have verified that the data is being pushed to the bucket. I have also verified the backup works on the same cluster, as I “exported from restore point outside the cluster with success” Anything to look for in specific? I have looked through the logging pod and don’t see anything obvious.
Hi everyone, I am struggling with a “simple” request. How can I “clone” a Persistent Volume, so I can manually re-attach it to a POD?The Transforms just apply to PersistentVolumeClaims, not to PersistentVolumes.Thank you!Mattia
Hi All, How we can change Kasten dashboard access from Http to Https in an redhat hopenshift environment. BR, Ali
Hi, Using Kasten K10 with amazon s3 location, my aws s3 bucket keeps increasing quite a lot. Even if I removed hundreds of resotrepointcontent, I dont see any drops in the S3 bucket usage. I also decreased the retension in my backup policies. Hoeverer I dont see any improvements. Anybody experienced this behavior?
Hi Team,We installed longhorn for our storage. We want to take CSI snapshots using kasten k10, i have already installed snapshot CRDs . But when i run K10 primer check it fails , Starting CSI Checker. Could take up to 5 minutesCSI Snapshot Walkthrough:Not a supported CSI driver (driver.longhorn.io) - Error But i can take volumesnapshots and those are created in longhorn and saved to our s3 storage. This works fine.kubectl get volumesnapshotcontentNAME READYTOUSE RESTORESIZE DELETIONPOLICY DRIVER VOLUMESNAPSHOTCLASS VOLUMESNAPSHOT AGEsnapcontent-c25957d7-01a5-4bbc-8d7d-bea22f9a28e4 true 2147483648 Delete driver.longhorn.io longhorn test-snapshot-pvc 18msnapcontent-d9e9d0f4-61fd-487f-8f41-f5b30c3d4dd8 true 2147483648 Delete driver.longhorn.io longhorn test-snapshot-pvc2 9skubectl get volumesnapshotNAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGEtest-snapshot-pvc true nginx-readwrite-many 2Gi longhorn snapcontent-c25957d7-01a5-4bb
Saving a policy that (1) selects applications By Labels (2) has Snapshot Cluster-Scoped Resources doesn’t behave as expected.Expected:Labels remain unchanged. Snapshot Cluster-Scoped Resources remains checked. Applications page recognizes that Cluster-Scoped Resources policy exists.Actual:K10 adds a label k10.kasten.io/appNamespace=kasten-io-cluster to the label list. Snapshot Cluster-Scoped Resources is changed to unchecked. Applications page does not recognize that a Cluster-Scoped Resources policy exists. Policy fails even though all listed actions complete successfully.
Hi.Have a problem with Multicluster. I forgot to disconnect a cluster from multicluster before I destroyed it.I then did the disconnect, but it stays in “Removal pending” on the console. Is there a way to force the removal to pass? Regards,-Ulf
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
