Periodical non-incremental backups for "raw" targets
- Dominant language
- Perl
- Stars
- 2.1k
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
As the man page states, incremental "raw" backups may be unreliable and can break when restoring. Implement some kind of: "hey, it's past first day of month, and last full backup is older than xy days, trigger full backup!".
As a workaround, you can run `btrbk --override=incremental=no run` periodically.
refs: #132
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the man page section on raw backups and issue #132 first, then trace the btrbk command path used by `btrbk --override=incremental=no run`. Define how the monthly age check and full-backup trigger should work, including the missing threshold policy, and verify that raw targets periodically receive a non-incremental backup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, perl
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100