PowerProtect Data Manager 19.15 Kubernetes User Guide

Restore to an existing namespace

Perform the following steps to restore a Kubernetes protection policy backup to an existing namespace within a Kubernetes cluster:

1. From the PowerProtect Data Manager UI, select Restore > Assets, and then select the Kubernetes tab.
   The Restore window displays all protected and unprotected namespaces.
2. Select the checkbox next to a protected namespace and click Restore.
   You can also use the filter in the Name column to search for a specific namespace, or use the Search field to search on specific criteria.
   The Restore wizard appears.
3. On the Select Copy page:
   1. Select the radio button next to a backup copy.
   2. Click Next.
   NOTE:If you click Next without choosing a copy, the most recent backup copy is used.
4. On the Cluster page, select one of the following options, and then click Next:
   • Restore to Original Cluster—Select this option to restore to an existing namespace on the original cluster.
   • Restore to an Alternate Cluster—Select this option to restore to an existing namespace on a different cluster, and then select the cluster from the list. A restore to an alternate cluster can be useful when migrating namespaces from a cluster on-premises to a cluster in the cloud, when moving namespaces from a lower cluster version to a higher cluster version, or when moving from one environment to another (for example, from a test environment to a production environment).
     NOTE:When restoring to an alternate cluster, ensure that this Kubernetes cluster has been added and discovered in the PowerProtect Data Manager UI Asset Sources window.
5. On the Purpose page, select from one of the following options:
   • Restore Namespace and Select PVCs to restore namespace resources and selected persistent volume claims (PVCs). Optionally, you can also select Include cluster scoped resources to restore the cluster roles, cluster role bindings, and custom resource definitions (CRDs) that were backed up automatically as part of the Kubernetes protection policy.
   • Restore Only PVCs to restore PVCs without namespace resources.
6. Click Next.
   The Restore Type page displays.
7. On the Restore Type page, select Restore to Existing Namespace, and then select a namespace from the Select Namespace list. Click Next.
   The PVCs page appears, displaying the PVCs in the namespace that you plan to restore, along with the PVC configuration in the original target namespace.
8. On the PVCs page, if the configuration of the namespace you want to restore is different from the configuration in the target namespace:
   • Select Overwrite content of existing PVCs to restore selected PVCs and overwrite existing PVCs in the target location if they have the same name.
   • Select Skip restore of existing PVCs to restore selected PVCs without overwriting existing PVCs in the target location if they have the same name.
9. Optionally, if you want to retire the storage class on the original cluster:
   1. Select Change storage class for PVCs to compatible storage class.
      The PVCs that are part of the restore display.
   2. Select the checkbox next to the PVCs for which you want to change the storage class on the target cluster.
      NOTE:The storage class will not be modified for existing PVCs being overwritten.
10. Click Next.
    If you selected Change storage class for PVCs to compatible storage class, the Storage Class page appears with a list of supported storage classes on the target cluster.
    If you did not select this option, the Options page appears. Go to 12.
11. On the Storage Class page:
    1. Select the checkbox next to a PVC for which you want to change the storage class on the target cluster, or select multiple PVCs to change all selections to the same storage class.
       NOTE:When changing the PVC storage class on the target Kubernetes cluster, if you select more than one PVC at a time on this page, only the storage classes that apply to all selected PVCs display. To view and select from all available storage classes, select one PVC at a time.
    2. Click Target Storage Class to select from the available storage classes.
       The Select Storage Class dialog appears.
    3. Select from one of the available storage classes, and then click Save to save your changes and return to the Storage Class page.
       NOTE:PVCs that were backed up using first class disk (FCD) data path can only be restored to FCD storage classes. CSI-based PVCs, however, can be restored to FCD or CSI storage classes.
    4. If changing the storage class for one PVC at a time, repeat steps a through c.
    5. Click Next.
    PowerProtect Data Manager creates a mapping between the original storage class and the new storage class.
12. On the Options page, you can select Troubleshooting mode to enable debug logging, and then select the level of logging to use:
    • Info—Includes information such as status changes. This is the default log level for scheduled backups and restores.
    • Debug—Additional information that helps with problem diagnosis.
    • Trace—The most detailed amount of information for complex problem diagnosis.
13. Click Next.
14. On the Summary page, click Restore.
    NOTE: A confirmation message indicates that namespace resources, including pods, services, secrets, and deployments, are not overwritten during the restore, and that all resources that do not exist in the namespace will be restored.
    An informational dialog box appears indicating that the restore has started.
15. Go to the Jobs window to monitor the restore.
    A restore job appears with a progress bar and start time.