#44 Don't prune non-borgmatic archives

Open
opened 1 year ago by import_bot · 0 comments

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.

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.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.