Restoring/Migrating Kubernetes Applications Out of Place

You can restore an application out of place to any Kubernetes cluster that is added to Commvault, for application migration or disaster recovery. You can migrate Kubernetes applications between different Kubernetes distributions, clusters, and StorageClasses. Commvault requires the source and destination cluster to use the same major release of Kubernetes. For example, you can restore Kubernetes 1.23 to Kubernetes 1.23.

You can use out-of-place restores to migrate applications as follows:

• From on-premises clusters to cloud-managed clusters (for example, Azure Kubernetes Service, Google Kubernetes Engine, and Amazon Elastic Kubernetes Service)

• From one cloud-managed cluster to another cloud provider (for example, between Amazon Web Services, Azure, and Google Cloud Platform)

• From a cloud-managed cluster to a cloud IaaS cluster (for example, from Google Kubernetes Engine, Amazon Elastic Kubernetes Service, or Azure Kubernetes Service to Amazon EC2, Azure, or Google Cloud Platform VM instances)

Procedure

1. From the navigation pane, go to Protect > Kubernetes.

   The Applications tab appears.

2. On the Application groups tab, in the row for the application group that you want to restore, click the action button , and then click Restore.

   The Select restore type page appears.

3. Click Full application.

   The Restore page appears.

4. Select the applications to restore.

5. To select a specific backup copy to restore from, do the following:

   By default, Commvault restores content from the first available, valid backup copy that it finds.

   1. In the upper-right corner of the page, click Settings.

      The Settings dialog box appears.

   2. From the MediaAgent list, select the access node that contains the backup copy.

   3. From the Source list, select the backup copy.

   4. Click Save.

6. Click Restore.

   The Restore options dialog box appears.

7. For Type, select Out of place.

8. For Destination cluster, select the cluster to restore the content to.

   You can select any Kubernetes cluster that is added to Commvault.

9. From the Access node list, select the access node to perform the restore.

   For optimal performance, select an access node that has low latency to the Kubernetes cluster and the backup copy.

10. In the Application name box, enter a name for the restored application.

11. Specify the namespace to restore the application to:

    • To select an existing namespace, from the Namespace list, select the namespace.

    • To create a namespace, move the Enter namespace manually toggle key to the right, and then enter a name for the namespace.

12. From the Storage class list, select the StorageClass to provision PersistentVolumes from.

    If you intend to back up the restored application with Commvault, select a StorageClass that has a CSI provisioner, an attacher, and a snapshotter.

13. To delete and overwrite existing data, move the Unconditionally overwrite if it already exists toggle key to the right, and then click Yes in the confirmation dialog box.

    If any data matching the restore data exists in the destination, Commvault deletes the existing data before starting the restore process.

14. To use resource modifiers to add, delete, and modify fields in the Kubernetes resource YAMLs that you restore, under Advanced options, do the following:

    • To use an existing resource modifier from either the source or destination cluster, select the resource modifier.

    • To specify a new resource modifier or to change an existing modifier, click Edit Modifiers.

    For more information about resource modifiers, see Modifying Fields in Restored Kubernetes Resource YAMLs.

15. Click Submit.