No action was taken because the import artifacts already existed
| KB ID: | 4607 |
| Product: | Veeam Kasten for Kubernetes |
| Published: | 2024-06-13 |
| Last Modified: | 2024-06-13 |
Get weekly article updates
Oops! Something went wrong.
Please, try again later.
Challenge
Veeam Kasten for Kubernetes has smart logic built-in to perform intelligent actions. Assuming an Import job on the target cluster was successfully completed, unless there's a new restorepoint from the source cluster, the job won't run. This can happen if:
- there are no new restorepoints
or - the import job is scheduled to run more frequently than an export job (via policies)
No action was taken because the import artifacts already existed
Cause
Veeam Kasten for Kubernetes leverages an Object Storage bucket to perform Disaster Recovery of Kubernetes applications. Import job is a critical first step in the DR process, because it downloads metadata of the source cluster's restorepoint and stages the target cluster's K10 catalog appropriately. This is subsequently followed by a Restore job, which downloads the data and restores the application to a fully working state.
Solution
To overcome such a non-action on the source cluster, initiate a manual export job or an export policy to create a new restorepoint for the target cluster to fetch.
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.
