- 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
Increase the number of worker threads in Supervisor cluster backup-driver if Velero timeout occurs
During a Kubernetes protection policy backup, the snapshots of persistent volumes in Tanzu Kubernetes guest clusters are performed sequentially by the backup driver in the Supervisor cluster.
If backups fail because of a Velero timeout, even when the Velero pods are running without issues, and there are 10 or more guest clusters in the environment, Dell Technologies recommends increasing the number of worker threads in the Supervisor cluster backup-driver.
To update the Supervisor cluster backup-driver deployment to increase the number of worker threads, apply the following change to the --backup-workers line in the Supervisor cluster backup-driver:
spec:
containers:
- args:
- server
- --backup-workers=5
command:
- /backup-driver
NOTE Making this change restarts the
backup-driver. After the restart, verify that the
backup-driver pod is available and running in the Supervisor cluster.
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: <>()\