You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
ISSUE
System information. For client/server mode post info for both machines.
Your borg version (borg -V)
borg 1.2.8
Operating system (distribution) and version
Linux Mint 20
How much data is handled by borg?
389G
Describe the problem you're observing.
My drive is now full, and I need to remove (prune) old backups.
However, I do not want to only keep the last 14 days, but two backups per week, no matter, how many that would be.
As far, as I understand the documentation, this is currently not possible.
Would it be possible to implement that?
The text was updated successfully, but these errors were encountered:
Don't forget compact, only that will free space (for borg >= 1.2.0).
borg has all sorts of pruning, from secondly to yearly, but there is no "keep 2 per week".
E.g. you could:
keep everything within 3 days
keep 60 daily backups
keep 26 weekly backups
keep 36 monthly backups
keep 10 yearly backups
Note that keeping backups that are "close" to each other (on the time scale) does not need much space. The more far apart they are, the bigger the differences / the deduplicated size.
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
ISSUE
System information. For client/server mode post info for both machines.
Your borg version (borg -V)
borg 1.2.8
Operating system (distribution) and version
Linux Mint 20
How much data is handled by borg?
389G
Describe the problem you're observing.
My drive is now full, and I need to remove (prune) old backups.
However, I do not want to only keep the last 14 days, but two backups per week, no matter, how many that would be.
As far, as I understand the documentation, this is currently not possible.
Would it be possible to implement that?
The text was updated successfully, but these errors were encountered: