Purge Backup Points not considering Parents and Childs
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
The purge of Backup Points is not considering the dependency for Child Backup Points (Differential Backup),
so for if the Full Backup get purged because it's the oldest and then number of Backup Points existing are above define limit for purge, the depending Child Backups getting useless as the parent backup set is lost!!
I think the purge has to be coded more specific, to not break the dependency chain of the backup points.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lib/Service/PointService.php around lines 954-969 and trace how purge candidates and backup-point dependencies are selected. The fix is done when purging an old full backup no longer leaves dependent differential backups unusable because their parent backup set was removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100