VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hello @SBEAfter looking over the described above, this looks to be related to a lack of resources available on all of your nodes to start the new copy-vol pod during exporting. You may need to increase resources of the nodes or add a node (or two) based on the node's resources. This may help with understanding K10 requirements. “https://docs.kasten.io/latest/operating/footprint.html#requirement-guidelines” ThanksEmmanuel
Hello SBE, Could you please provide the results of the command below when you are running the snapshot with export.kubectl describe po copy-vol-data-xxxxx -n kasten-ioThere should be a pod that is failing during the exporting. ThanksEmmanuel
Hello Aaron, Could you please provide us your debug logs so that we may further look into your logs. You can find this by going to Settings>Support>Download Logs If you could please attach the executor-svc(all three), and logging-svc log file and lastly the k10_debug we will have a good bases to further troubleshoot. Thanks Emmanuel
Hello SMT-Almato, Could you please rerun the policy and within the first ten minutes provide the events for kasten-io namespace. kubectl get events -n kasten-io ThanksEmmanuel
Hello, Lemassacre, That's great to hear. With the context deadline error, this would have been an issue within events, possibly an issue with PVC or pods. It's great to hear you have resolved your problem. ThanksEmmanuel
Hello TobiAss, Have you tried NodePort? ThanksEmmanuel
Hello TobiASS, Have you tried other means to access K10 dashboard other than Port Forward? ThanksEmmanuel
Hello ebsglobal,Is this PVC bound to any pods?ThanksEmmanuel
Hello, Could you please provide the results of the commands below. kubectl get sckubectl get volumesnapshotclasskubectl get csidrivers ThanksEmmanuel
HelloI just want to respond back to the message above, but at this time, K10 does not support Managed Identity in Azure. At this time, we only support Service Principle. This is likely to explain the error above. ThanksEmmanuel
Hello Anthony, That's great to hear. Doesn't sound like you would need the logs at this point. ThanksEmmanuel
Hello Anthony, Could you please gather your debug logs, and please look through the logging-svc to narrow down the cause? This could be related to multiple things, and looking for the “cause” in the logs should help narrow down the issue’s.You can now simply access the debug logs from within the support page in K10 UI. ThanksEmmanuel
Hello Maximn,Thanks for contacting Kasten Support. Could you please provide the debug logs so that we may have a better understanding of your environment. The command is below.curl -s https://docs.kasten.io/tools/k10_debug.sh | bash;ThanksEmmanuel
Hello Thanks for contacting Kasten Support. Could you please provide the results for the command below. kubectl get volumesnapshotclass -A ThanksEmmanuel
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.