- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Kubernetes Overview
- Enabling the Kubernetes Cluster
- Managing Storage, Assets, and Protection for Kubernetes Clusters
- 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.10 Kubernetes User Guide
Updating PowerProtect Data Manager to version 19.10 or later in a Kubernetes environment
When updating PowerProtect Data Manager to version 19.10 or later in a Kubernetes environment, certain considerations must be taken into account.
CAUTION If you are not using the
cluster-admin role and you do not follow a Kubernetes-specific update procedure,
PowerProtect Data Manager will fail to function properly.
PowerProtect Data Manager uses structural custom resource definitions (CRDs) to extend the Kubernetes API and increase system security. But versions of PowerProtect Data Manager earlier than 19.9 used non-structural schemas that did not validate the consistent format of custom resources (CRs). When updating from a version of PowerProtect Data Manager that supports Kubernetes asset sources to version 19.10 or later, certain considerations must be taken into account. For information about updating PowerProtect Data Manager in general, see the PowerProtect Data Manager Administration and User Guide or the PowerProtect Data Manager Deployment Guide.
Self-service recovery
During the update, all CRs are deleted, including the backupjobs CR. After the update, the self-service recovery of the last backup copy taken before the update is not possible. That backup can only be restored from the PowerProtect Data Manager user interface. Self-service recoveries can be performed on backups taken after the update.
Minimum cluster-role privileges
The following cluster roles must have certain privileges:
- The cluster role bound to the service account provided to PowerProtect Data Manager must have Delete for customresourcedefinitions resources.
- The cluster role bound to ppdm-serviceaccount must have Patch for deployments resources.
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: <>()\