Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Red Hat > Guides > Red Hat Open Shift Container Platform Guides > Deployment Guide: Red Hat OpenShift Container Platform Reference Architecture for Telecom > Protecting your cluster with PowerProtect Data Manager
PowerProtect Data Manager offers efficient data protection capabilities using the latest evolution of Dell EMC trusted protection storage architecture.
With operational simplicity, agility, and flexibility at its core, PowerProtect Data Manager enables the protection, management, and recovery of data in on-premises, virtualized, and cloud deployments, including protection of in-cloud workloads. You can also protect cloud-native workloads across multiple public clouds using our integrated SaaS-based PowerProtect Cloud Snapshot Manager.
The following steps show the process to integrate OpenShift cluster with PowerProtect, protect applications, and volumes created using Dell CSI drivers.
Note: Log in to your RHOCP environment as an admin user to run the following commands.
[core@csah-pri ~]$ oc project default
[core@csah-pri ~]$ oc create serviceaccount ppdmsa -n default
serviceaccount/ppdmsa created
[core@csah-pri ~]$ oc create clusterrolebinding ppdmcrb -n default --clusterrole=cluster-admin --serviceaccount=default:ppdmsa
clusterrolebinding.rbac.authorization.k8s.io/ppdmcrb created
[core@csah-pri ~]$ oc describe secrets ppdmsa-token-4l7dk
Name: ppdmsa-token-4l7dk
Namespace: default
Labels: <none>
Annotations: kubernetes.io/created-by: openshift.io/create-dockercfg-secrets
kubernetes.io/service-account.name: ppdmsa
kubernetes.io/service-account.uid: c21086ba-7411-4bf6-9b60-8cb4899d19d8
Type kubernetes.io/service-account-token and note the value that is highlighted below:
Data
====
namespace: 7 bytes
service-ca.crt: 8435 bytes
token: eyJhbGciOiJSUzI1NiIsImtpZCI6IlhSMFQ2YVB4Mm1KUmRUY3FxQWlPMHFHcjBkQ29NazNqeWlsdUhnYXMyY1EifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJkZWZhdWx0Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZWNyZXQubmFtZSI6InBwZG1zYS10b2tlbi00bDdkayIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJwcGRtc2EiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJjMjEwODZiYS03NDExLTRiZjYtOWI2MC04Y2I0ODk5ZDE5ZDgiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6ZGVmYXVsdDpwcGRtc2EifQ.uTdp5OxkEbqZDXQmAMIGOBcGxr4b0Ntac2Xnaf0FJy1jLU-ChVLPuEstHvbnOvYHySDw8fnbMi5Np__rgKqDrx-w3iAoA6LUTpfZ22WzPqG7Blwppi8Rd5NvNHyZlUSaZIMtFXEzjDV7s5-FklWCEFbW7930Im-D70xV3hZ4-aBct47fG84f6aHJAGMfbO9cSJI6qQyk9YxNZcFWPtY_UMoXXUP4kwEBPu5RTU0MWvVXttXjHI_-DgmMonoanv3athx6bkYaSMLlX9pmPEuzp2gUjkrwOZ9E57zL2luEBqr6OhwPEw5MsdDeqwoMBijn9DVk3Jg2w6OEYU1rcQkD-A
ca.crt: 7222 bytes
Do not modify this value.
When your cluster is fully discovered, your cluster Discover Status is marked as OK.
Note: If your namespace owns PVCs, volumes are added to the backup automatically. You can exclude them when necessary.
Note: Choose a recurrence and configure retention parameters. In this example, we define a daily backup schedule that we want to keep for seven days.
Note: Unless you trigger a manual backup, the protection policy starts based on the schedule that you have configured.
Note: Unless you want to trigger a manual backup, the process of backing up an asset is run automatically based on the schedule that you have defined during the protection policy creation wizard.
core@csah-pri ~]$ oc get all
NAME READY STATUS RESTARTS AGE
pod/mysql 1/1 Running 0 46h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/mysql ClusterIP None <none> 3306/TCP 46h
Volumes:
mysql-persistent-storage:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: dynamic-iscsi-unity-pvc
ReadOnly: false
The backup runs in the background. You can monitor the progress by selecting Jobs in the left panel.
Depending on the amount of data to back up, the operation may take a while to complete.
Note: Before beginning a restore, a change to the contents in the MySQL DB tables was made. This change was performed to ensure that the correct contents are restored and modified contents do not exist when the restore is performed.
Note: By default, the latest copy is available to restore.
Note: Select the storage system first to be able to see the different copies.
Note: Restoring to another cluster is also possible as described in step 4.
Click Next.
Warning: Proceed with caution; the restore operation will replace the original data.
Similarly, to backup, restore runs in the background. You can monitor the progress by selecting Jobs in the left panel.
Depending on the amount of data to restore, the operation might take some time to complete.