Don't prune non-borgmatic archives #44
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#44
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Perhaps borgmatic should identify its own backups within your repo. For example, default archive_name_format would be borgmatic-{hostname}-{now:...} and the corresponding default prune prefix would be borgmatic-{hostname}-. I realize this isn't incredibly robust but it would reduce the risk of collisions and pruning things you didn't want to prune.
Additional idea: Add a dry-run flag to the retention section of the yaml file, so the user can confirm with -v2 that their backups are going to be pruned properly. If I were writing borgmatic from scratch I'd default to dry-run=True, but in this case False would be less of a behavior change.
Ideas from Andrew.
Imported from Taiga issue 43 (to do). Created on 2017-10-30T03:24:41+0000 by Dan Helfman.
Closing due to inactivity, but I'd be happy to reopen if there's still user interest.