No action was taken because the import artifacts already existed

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

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.

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.