This issue tracks the upstream Velero issue regarding scheduled backup queue accumulation during extended blocking scenarios.

Problem Description

Velero scheduled backups can accumulate in a "New" state queue when backup processing is blocked for extended periods. Various conditions can cause blocking, such as:

• Long-running backups
• Velero server downtime
• Kubernetes API server issues
• Infrastructure problems (storage, network, node)
• Resource constraints

Current Issue

The current logic in pkg/controller/schedule_controller.go:165 prevents new backup execution if any backup from that schedule is in New or InProgress state, leading to indefinite queuing and backup accumulation.

Upstream Issue

GitHub Issue: https://github.com/vmware-tanzu/velero/issues/9259

Proposed Solutions (from upstream)

• Age-based cleanup (recommended)
• Queue limits for pending backups