No backup retention policy #19
Labels
No labels
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-fetch
blocked:lint-failed
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:verify-failed
bug
feature-request
in-progress
needs-decompose
needs-triage
ops-task
quickfix
security/high
security/low
security/medium
test-coverage
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/docker_backup#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Old backups accumulate forever. No automatic pruning by age or count.
Impact
Storage fills with obsolete backups.
Suggested Fix
Add retention policy (keep N backups, max age).
Ops Pipeline — No Executable Procedure
Research did not produce any executable commands.
Already implemented. Retention enforcement logic exists at
backend/src/core/scheduler/retention.ts(enforceRetention) and is called from the queue worker after every completed scheduled backup (worker.ts:101). HandleskeepDaysandmaxBackupspolicy settings.