VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hello @ph1l1pp Thank you for using our community and K10.Could you please raise a ticket to K10 support at http://my.veeam.com/, to speed up the troubleshooting, please add to your case the debug logs:https://docs.kasten.io/latest/operating/support.html#gathering-debugging-informationBest RegardsFernando R.
Hello @Pando85Thank you for using our community and K10!In our next release (4.5.7), k8s 1.22 version will be supported, it should be available this weekend, please stay tuned at https://docs.kasten.io/latest/releasenotes.html where the release details will be posted. Best regardsFernando R.
Hello @Aly Idriss , Thank you for contact Kasten by Veeam and using our community!I would recommend to check the setup of your StorageClass, K8s allows PVC to be expanded only when the StorageClass has "allowExpansion" set to true according with K8s documentation:https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claimsIt would be set as true by default on CSI driver, but I am not sure which Storage are you using with K10.RegardsFernando R.Kasten Support
Hello @Aly Idriss ,Looks like there are some issues regarding resize of a created PVC on k3s Local Path Provisioner, so after enabling "allowVolumeExpansion" the command should work as it did for you, but the real size will not show, according to the PR/docs since Local Path Provisioner doesn't take PVC size into consideration, there is no quota/enforcement for the volume size so it can have a bigger size than it showing on PVC being limited by the system disk size, but unfortunately looks like the PR did not address the PVC size status, it will still show the original amount.Please take a look in the links bellow for further details related to this:https://github.com/rancher/local-path-provisioner/issues/190https://github.com/rancher/local-path-provisioner/pull/189https://rancher.com/docs/k3s/latest/en/storage/RegardsFernando R.Kasten by Veeam support.
Hello Ali,Thank you for using our k10 community.Please as I replied in the K10 case you opened with us, I would like to ask you to check and make sure the permissions on S3 side are correctly set and please could you also provide us there (k10 case) the S3 profile's yaml so we can check the parameters, since 2.5.12 there were many changes in the code/workflow, so we need more details to try to find out the issue.RegardsFernando R.
Updates Guys about this case, The issue was from Nutanix not from Kasten, the issue was from the endpoint, they were using the subdomain endpoint, after they used the correct endpoint it worked fine. Thank you for the update Aly.
Hello Claudio,Using MinIO as a profile for kanister action is only applicable for backupAction, Export will still uses the location profile under export (in this case VBR) that is set up in the policy form, so backup pushes the kanister artifact to MinIO however export will fail when it pushes to VBR, that means using VBR as a profile for blueprint based backups is unsupported for now on K10.I am working to update our documentation informing this and also internally we will be working with engineering team to address this for future releases.Please let me know if you have any additional questions.RegardsFernando R.
These were submitted. Backups still failing. Hello @Aaron Oneal .Kasten K10 4.5.15 is out please check the release notes here: https://docs.kasten.io/latest/releasenotes.html There is a fix in this release that was related when policies with selective export and independent export retention schedule fail but all the run actions were succeed, related with automatic retirement failure.I would recommend to try this latest version and maybe if possible recreate your policy or create a new one to test.ThanksFernando
@Hagag, have you reproduced this? I’m unclear why your question above was marked as a solution. Hello @Aaron Oneal .When using the cluster-scoped option the recommended way is selecting your application by "name", if you are filtering already with label your apps , filtering cluster-scoped resources with a different label will not work.We have a documentation regarding this where the app is selected by name:https://docs.kasten.io/latest/usage/clusterscoped.html#snapshot-policies-for-application-and-cluster-scoped-resourcesThis process can be enhanced , but for now it is working as designed. I noted about this and will register a feature request to engineering so they can assess to be added in any future releases.RegardsFernando
While that happens to be how the policy is configured in a screenshot, there is nothing in the text that says filter by name is required. Since configuring otherwise breaks the functionality, it would be better to disable the snapshot toggle in the UI when labels are configured because it leads to this non-functional behavior. I am baffled this is considered as designed and not an obvious bug. Hello Aaron,Thank you for your reply, I will be working to update our docs to include that information regarding the filter by "name", and also it is already reported to our engineering team for future enhancements. Regarding working as designed, in the sense that while using label for both apps and cluster-scoped resources what K10 does it tries to add a single entry of k10.kasten.io/appNamespace: kasten-io-cluster as label that will match and select cluster scoped resources related with the app being backed up, what could help is a better information in the UI and also in our docs related to
While that happens to be how the policy is configured in a screenshot, there is nothing in the text that says filter by name is required. Since configuring otherwise breaks the functionality, it would be better to disable the snapshot toggle in the UI when labels are configured because it leads to this non-functional behavior. I am baffled this is considered as designed and not an obvious bug. Hello Aaron, Thank you for your reply, I will be working to update our docs to include that information regarding the filter by "name", and also it is already reported to our engineering team for future enhancements. Regarding working as designed, in the sense that while using label for both apps and cluster-scoped resources what K10 does it tries to add a single entry of k10.kasten.io/appNamespace: kasten-io-cluster as label that will match and select cluster scoped resources related with the app being backed up, what could help is a better information in the UI and also in our docs r
Hello @Aaron Oneal ,Thank you for the information.Would be great to have your debug logs with the new version (4.5.15), or at least could you please provide the same executor-svc output of the error as you did in this post but with 4.5.15 version, since we had a fix for the same function I would like to see if something changed in the error message from 4.5.14 to the latest version that would help us to investigate.RegardsFernando
Hello @Aaron Oneal , Thank you for the information. Would be great to have your debug logs with the new version (4.5.15), or at least could you please provide the same executor-svc output of the error as you did in this post but with 4.5.15 version, since we had a fix for the same function I would like to see if something changed in the error message from 4.5.14 to the latest version that would help us to investigate. Regards Fernando Hi @Aaron Oneal ,Also if possible can you provide the policy yaml or the screenshot from dashboard of the policy setup , I would like to check the retention/export retention you selected to try to replicate on our side.Thank youRegardsFernando
Hello @KastenJohn.Great to hear you managed to install using k10tools.Could you please provide the error messages you are facing so we can take a look, also maybe if possible the Kanister logs would help us to find the cause.RegardsFernando R.
Hello @JTI , @SBE .Since it needs more investigation I would recommend please if you can open a trial case and upload your debug logs in the case so we can have a better look.Also what you can try is create a PVC using the snapshot created as a source manually and see how much time it takes to be bound and ready.RegardsFernando R.
Hello @Smugness2774,Could you please take a look in your dashboard-svc logs and search for your profile name, it could point us to the cause or help us to investigate.kubectl logs dashboardbff-svc-xxxxxxx | grep VBR_PROFILE_NAMEAlso please take a look in the port/credentials requirements from VBR integration with K10:https://helpcenter.veeam.com/docs/backup/kasten_integration/used_ports.html?ver=110https://helpcenter.veeam.com/docs/backup/kasten_integration/req_permissions.html?ver=110https://docs.kasten.io/latest/usage/configuration.html#vbr-location-profile RegardsFernando
Hello @nantheless Thank you contacting Kasten by Veeam support.Checking on our side regarding the location on Azure profile from 5.0.7, will update as soon as possible.RegardsFernando
Hello @nantheless There is a bug in the UI on 5.0.7 regarding Azure storage location profile and will be fixed in the next release.For now if you are using 5.0.7 you can create your location profile using CLI, but keep in mind that from 5.0.7 the bucket (container on azure storage) must be created before creating the location profile on K10: Create a secret with the credentials: kubectl create secret generic k10-azurestorage-secret \ --namespace kasten-io \ --type secrets.kanister.io/azure \ --from-literal=azure_storage_account_id=AZURE_STORAGE_ACCOUNT_NAME \ --from-literal=azure_storage_key=AZURE_STORAGE_KEY Create an yaml for the profile: (replace PROFILE_NAME,BUCKET_NAME and region) cat <<EOF >>azure-profile.yamlapiVersion: config.kio.kasten.io/v1alpha1kind: Profilemetadata: generation: 2 name: PROFILE_NAME namespace: kasten-iospec: locationSpec: credential: secret: apiVersion: v1 kind: secret name: k10-azurestorage-s
Hello @KastenJohnThank you for using our community and K10!There is a way to cancel a K10 action from CLI (runaction, backupaction, restoreaction..), you must create a cancel action, you can find more details in our documentation.https://docs.kasten.io/latest/api/actions.html?highlight=cancel%20action#cancelaction-api-typeI will describe how to do it and also how to check in more details about your restore action.First check if the restore action is still running: (It can be also done for backup actions)kubectl get restoreactions -A -o custom-columns=ACTION:.kind,NAMESPACE:.metadata.namespace,NAME:.metadata.name,'CREATED AT':.metadata.creationTimestamp,STATUS:.status.state,POLICY:.metadata.labels."k10\.kasten\.io\/policyName"ACTION NAMESPACE NAME CREATED AT STATUS POLICYRestoreAction test22 test22-6nr5v 2022-10-11T14:33:49Z Running <none>Describe the restore action, it can help you identify what is happening:#This case using the re
Hello @voarsh Please let us know if you are still facing this issue.RegardsFernando R.
Hello @Prasanna Keshava ,As @jaiganeshjk , has stated in his reply, the "--name" is a name of your choice that is used to identify your cluster, it was not extracted from your context, this "name" can be anything that helps you to identify your cluster, you can think of it as a label for your cluster.The parameter you have to fill with the information you collected from your context is --context , that according with your context output would be:--context=kasten-io/api-rosa4keshava-vidk-p1-openshiftapps-com:6443/cluster-admin Hope it answer your question.Fernando R.
Hello @abasha1 Thank you for using our community.Could you please provide some more details, in example, have you upgraded K10 to a newer version, I notice that the pods are not older than 9 hours so looks like K10 was redeployed or upgraded.Also please add the controllermanager-svc logs, that might contain some additional information as I can see both dashboard-svc and controllermanager-svc restarted 4 times.If K10 was not upgraded, you could try rolling out K10 deployment and check the events and logs for dashboard and controllermanager.kubectl rollout restart deployment -n kasten-ioRegardsFernando
Hello @abiwot Thank you for using or community.First I would like to point out, since I noticed you are using latest k8s version on target cluster, K10 does not support k8s 1.24 as yet, planned to be supported soon.Regarding transformations, you can apply while importing to your target cluster, when you select "Restore After import" checkbox, and each transform can be applied to a specific resource using group, version, resource type and name, or if you want to apply i.e. all PVCs to have a different storageclass, you can create a transform specifying only the version and resource as "persistenvolumeclaims" and all PVCs will be affected by this transform.That means you can apply transform to multiple resources of the same type without specifying a name, but in the actual version it is not possible to apply a general transform that would affect all type of resources in the namespace in a single operation.More information can be found in our docs: https://docs.kasten.io/latest/usage/rest
Hello @tinto.1970 Hope all is well, there is a document where we provide how to setup alerts/rules on K10 grafana to be sent by email daily. Please take a look, other alerts can be created based in different K10 prometheus metrics.https://kb.kasten.io/knowledge/setting-up-smtp-and-alerting-with-k10-grafanaRegardsFernando R.
Hello @amit ,Thank you for using our K10 community!There is a possibility to use a helm value to accept the EULA form, also add Company and email, during installation or upgrade, it helps when using automation tools (Argo/Gitops) to deploy K10.Reference: https://docs.kasten.io/latest/install/advanced.html?highlight=accept%20eula#complete-list-of-k10-helm-optionsDuring installation just add the helm parameters to your install command:--set eula.accept=true \--set eula.company="COMPANY NAME" \--set eula.email="COMPANY EMAIL"In case of upgrade, there is a configmap that is created when installing K10 named "k10-eula-info", delete this configmap and run the helm upgrade with the values below:#Delete configmap k10-eula-info from kanten-io namespacekubectl delete cm k10-eula-info -n kasten-io#Save K10 helm values to a filehelm get values k10 -n kasten-io > k10_val.yaml#Upgrade K10 using the helm values belowhelm upgrade k10 kasten/k10 --namespace=kasten-io -f k10_val.yaml \--set eula.acce
Already have an account? Login
Enter your username or 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.
