- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Kubernetes Overview
- About asset sources, assets, and storage
- Prerequisites
- Supported Internet Protocol versions
- Port usage
- Role-based security
- Data-in-flight encryption
- Roadmap for Kubernetes cluster protection
- Roadmap for Tanzu Kubernetes guest cluster protection
- Updating PowerProtect Data Manager from version 19.9 or earlier to the latest version in a Kubernetes environment
- Enabling the Kubernetes Cluster
- Adding a Kubernetes cluster asset source
- Prerequisites to Tanzu Kubernetes guest cluster protection
- Prerequisites to Kubernetes cluster discovery
- Enable an asset source
- Delete an asset source
- Add a VMware vCenter Server
- Add a Kubernetes cluster
- Controller Configurations
- Add a VM Direct Engine
- Protection engine limitations
- Managing Storage, Assets, and Protection for Kubernetes Clusters
- Add protection storage
- Replication triggers
- Add a protection policy for Kubernetes namespace protection
- Add a Cloud Tier objective to a protection policy
- Add a service-level agreement
- Extended retention
- Edit the retention period for backup copies
- Delete backup copies
- Using the PowerFlex volumegroup snapshot extension
- Protecting PVCs in PowerScale access zones
- Restoring Kubernetes Namespaces and PVCs
- Kubernetes Cluster Best Practices and Troubleshooting
- Configuration changes required for use of optimized data path and first class disks
- Recommendations and considerations when using a Kubernetes cluster
- Support Network File System (NFS) root squashing
- Update the Velero or OADP version used by PowerProtect Data Manager
- VM Direct protection engine overview
- Troubleshooting network setup issues
- Troubleshooting Kubernetes cluster issues
- Specify volumesnapshotclass for v1 CSI snapshots
- Enabling protection when the vSphere CSI driver is installed as a process
- Customizing PowerProtect Data Manager pod configuration
- Backups fail or hang on OpenShift after a new PowerProtect Data Manager installation or update from a 19.9 or earlier release
- Data protection operations for high availability Kubernetes cluster might fail when API server not configured to send ROOT certificate
- Kubernetes cluster on Amazon Elastic Kubernetes Service certificate considerations
- Removing PowerProtect Data Manager components from a Kubernetes cluster
- Increase the number of worker threads in Supervisor cluster backup-driver if Velero timeout occurs
- Velero pod backup and restore might fail if namespace being protected contains a large number of resources
- Pull images from Docker Hub as authenticated user if Docker pull limits reached
- Application-Consistent Database Backups in Kubernetes
- About application-consistent database backups in Kubernetes
- Obtain and deploy the CLI package
- About application templates
- Deploy application templates
- Perform application-consistent backups
- Verify application-consistent backups
- Disaster recovery considerations
- Granular-level restore considerations
- Log truncation considerations
PowerProtect Data Manager 19.11 Kubernetes User Guide
Update the Velero or OADP version used by PowerProtect Data Manager
When PowerProtect Data Manager is configured to protect Kubernetes clusters, Velero is used for backing of Kubernetes resources. In an OpenShift environment, PowerProtect Data manager uses OADP to deploy Velero. Each PowerProtect Data Manager release uses a specific version of Velero by default, which is documented in the file /usr/local/brs/lib/cndm/config/k8s-image-versions.info. If you must update the Velero or OADP version that PowerProtect Data Manager uses in order to pick up the latest security fixes, perform the following procedure.
Prerequisites
NOTE The
Velero version should be updated to an incremental patch build only. A minor or major version of Velero or OADP that is later than the default version that
PowerProtect Data Manager uses might not be compatible.
Steps
- Log in to PowerProtect Data Manager as an admin user.
- Open the file /usr/local/brs/lib/cndm/config/k8s-dependency-versions-app.properties.
-
In a non-OpenShift environment, add the following line to this file to update the Velero version, and then save the file:
k8s.velero.version=vx.y.z
Where vx.y.z is the Velero incremental patch version.
-
In an OpenShift environment, add the following line to this file to update the OADP version, and then save the file:
k8s.oadp.version=x.y.z
Where x.y.z is the OADP incremental patch version.
- Restart the CNDM service by running the command cndm restart, and then wait for a few seconds for the service to restart.
-
From the
PowerProtect Data Manager UI, run a manual discovery of the Kubernetes cluster.
When the discovery completes successfully, the configuration that is stored in the configuration map ppdm-controller-config on the Kubernetes cluster powerprotect namespace updates.
-
Run the following commands to delete the
powerprotect-controller pod on the Kubernetes cluster. This action forces a restart, during which the changes take effect. This step should be performed when there are no backup or restore operations in progress.
kubectl get pod -n powerprotectkubectl delete pod powerprotect controller pod name -n powerprotect
- Repeat steps six and seven for each Kubernetes cluster that is protected by PowerProtect Data Manager.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\