Restoration of Backup taken from PX-Security enabled cluster to PX-Security not enabled cluster

Backup of Px-Native volumes taken from Px-Security enabled cluster and Restore to 

1.  Same Px-Security enabled cluster - Supported without any workaround
2. Different Px-Security enabled cluster - Supported without any workaround
3. Different Px-Security not-enabled cluster - Supported with workaround (direct restore will throw missing "px-user-token" issue). 

What are the steps to perform restoration of Px-Native volumes backup taken from Px-Security enabled cluster to Px-Security not-enabled cluster ?

1. Restore the PV, PVC, application manifests etc., to new k8s cluster from backuplocation (S3-Object Storage or NFS Backup location)
2. Since the original source cluster is enabled with px-security and the newly created destination k8s cluster is not enabled with px-security. Because of this, when pod is trying to mount the restore pvc is failed with "failed to find secret px-user-token". To overcome this,
   1. Clone the restore volume at px layer (optional) using the command "pxctl volume clone --name <clone-volume-name> <original-vol-name>"
   2. Consume this Px-Pre-provisioned using the template (Ref: https://docs.portworx.com/portworx-enterprise/platform/provision-storage/create-pvcs/using-preprovisioned-volumes)
   3.  This Pre-Provisioned volume can be consumed by application pod in two ways
      1.  Create new PV, PVC referencing this Px-Pre-provisioned volume and mount in application (Ref: https://docs.portworx.com/portworx-enterprise/platform/provision-storage/create-pvcs/using-preprovisioned-volumes#2-using-the-portworx-volume-by-creating-a-persistentvolume--persistentvolumeclaim)
      2.  Consume the volume directly in application (Ref: https://docs.portworx.com/portworx-enterprise/platform/provision-storage/create-pvcs/using-preprovisioned-volumes#2-using-the-portworx-volume-by-creating-a-persistentvolume--persistentvolumeclaim)

• Category : Software
• Subcategory : PX Backup