- 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
Velero pod backup and restore might fail if namespace being protected contains a large number of resources
Kubernetes namespaces can include a large number of resources, such as secrets, configuration maps, custom resources, and so on. When a namespace being protected by PowerProtect Data Manager contains 1500 or more of these resources, the Velero pod might run out of memory, causing backup and restore operations to fail with an error.
If the namespace being protected has more than 1500 resources and protection jobs are failing with a Velero backup or restore error, increase the memory limits of the Velero pod by performing the following:
- Run the command kubectl edit deployment velero -n velero-ppdm, or an equivalent command.
- Review the output for the section on resource limits, which appears similar to the following:
resources: limits: cpu: "1" memory: 256Mi - Change the memory limit, depending on the number of Kubernetes resources in the namespace. For example:
- If the number of Kubernetes resources in the namespace exceeds 2000, change the memory limit to 512 Mi.
- If the number of Kubernetes resources in the namespace exceeds 3000, change the memory limit to 1024 Mi.
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: <>()\