Application Migration - Best Practices and Prerequisites

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.