Delete Backups

Portworx Backup provides efficient options to delete both individual and multiple backups, enabling better storage management. Standard backups can be deleted in parallel using configurable thread settings (BACKUP_DELETE_WORKER and VOL_DELETE_WORKER) that allow up to five backups and five threads per backup to be processed concurrently. This setup ensures proper dependency checks, especially for incremental backups, preventing data loss by moving dependent backups to a Delete Pending state.

For NFS backups, each PVC spawns a separate delete job, and new concurrency control parameters (like NFS_DELETE_JOB_LIMIT and KDMP_DELETE_JOB_LIMIT) help limit simultaneous job pods to avoid overloading clusters with job quotas. These parameters are set in ConfigMaps and must be manually added and tuned based on cluster pod quota limit. Together, these deletion workflows provide flexibility, reliability, and resource-efficient cleanup for both traditional and NFS-based backup environments. Refer the following topics to effectively manage backup deletion in Portworx Backup:

📄️ Delete Backups

This topic explains how to handle the deletion of backups and their associated volumes content efficiently and concurrently. This functionality allows users to delete backups while ensuring dependencies, such as incremental backups, are managed correctly. - >- portworx backup concurrent deletion, parallel deletion backups portworx, backup deletion efficiency portworx, portworx early access concurrent deletion, stork installation portworx, portworx volume thread configuration, backup dependency management portworx, concurrent backup deletion portworx, px-backup configuration parameters

📄️ Delete NFS Backups with Job Limit

Learn how to delete NFS backups in Portworx Backup using configurable backup job pod limits for delete jobs to avoid cluster resource exhaustion in job-constrained environments.