#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
TRY NOW
book meeting
BACK TO KB LIST

DR Restore - Internal error occurred: Could not retrieve artifacts for prefix

KB ID: 4617
Product: Veeam Kasten for Kubernetes
Published: 2024-06-13
Last Modified: 2024-06-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

A Veeam Kasten for Kubernetes DR Restore fails with the following error:

Internal error occurred: {"message":"Could not retrieve artifacts for prefix search","function":"kasten.io/k10/kio/rest/clients.FetchArtifactsForSearchPrefix","linenumber":52,"fields":[{"name":"key","value":"api-meta-label_restoreactions.actions.kio.kasten.io_k10.kasten.io/policyName"},

Cause

The issue occurs after a Disaster Recovery (DR) Restore is initiated but fails due to some complication. During the DR restore process the catalog service is scaled down, so when the DR Restore is re-initiated, it searches for the catalog which is not available at that time because it has been scaled down. 

Solution

The following steps would help resolve this particular issue:

  1. Check the status of the restore pod in the kasten-io namespace. If DR restore fails, the pod status will be shown as 'failed'.
kubectl get po -n kasten-io
  1. Check the catalog pod status. Make sure the catalog pod is running. If it is not running, scale the catalog deployment using the following command:
kubectl scale deploy/catalog-svc --replicas=1 -n kasten-io
During the DR restore, catalog-svc deployment will be scaled down to recover the catalog. If the DR restore fails for some reason, when re-initiating the restore, you must scale up the catalog to 1.
  1. Uninstall k10-Restore helm chart (previously failed)
helm uninstall k10-restore -n kasten-io

  1. Re-initiate the Veeam Kasten for Kubernetes DR restore process.

  2. Check for the status of the DR Restore Chart, Restore Pod, and Catalog Pod.

helm list -n kasten-io
kubectl get po -n kasten-io
#If its successful - catalog pod should show up as running and restore pod will be terminated upon DR Completion

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.