#1 Global Leader in Data Resilience

Application Migration - Best Practices and Prerequisites

KB ID: 4621
Product: Veeam Kasten for Kubernetes
Published: 2024-06-14
Last Modified: 2024-06-14
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.

Purpose

This article explains the prerequisites and best practices that must be considered for successful import during application migration.

Solution

Veeam Kasten for Kubernetes platform is built to support application migration across clusters, which is an extremely powerful feature that enables a variety of use cases, including Disaster Recovery (DR), Test/Dev with realistic data sets, and performance testing in isolated environments.

The easiest way to migrate an application is to export the application from the source cluster and import it into the destination cluster. Export can be easily configured and run by following this documentation.

The following recommendations should be considered before running an import policy.

Recommendations to Ensure a Successful Import

  • Ensure Veeam Kasten for Kubernetes installation is identical (same version, installation namespace, etc.) in both the source and target clusters.

    While we continuously make improvements in how we generate the encryption keys in each version of Veeam Kasten for Kubernetes, having the same version in the source and destination clusters will reduce the possibility of import failure due to a mismatch between Veeam Kasten for Kubernetes versions in source and target clusters.

    Also, if the Veeam Kasten for Kubernetes installation namespace differs between the source and target cluster, import action will fail with the error `No kopia manifests found in the repository.`  Review KB4620 for more information.
  • Ensure that the external storage target (location profile S3/NFS/VBR), where the backups are exported from the source cluster, is accessible and registered as a location profile in the target cluster.
  • Ensure the correct `Config data for Import` (i.e., migrationToken) is used when creating the import policy. This encoded string has all the metadata that Veeam Kasten for Kubernetes needs to access, decrypt, and restore the data from the repository. So, getting the correct config string for a successful import is essential.

    Example - Manual exports are stored in a different repository than policy-based exports. It is important to validate if the export is manual or policy-based and copy the string accordingly.
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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.