Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make prune in the repository config file not mandatory #58

Open
Phothiabea opened this issue Mar 9, 2021 · 0 comments
Open

Make prune in the repository config file not mandatory #58

Phothiabea opened this issue Mar 9, 2021 · 0 comments

Comments

@Phothiabea
Copy link

Phothiabea commented Mar 9, 2021

According to the README prune must be defined for all repository config but this goes against the idea of both duplicacy and this tool to manage multiple repositories on the same storage location (aka. different snapshot-ids). The documentation of duplicacy recommends only running prune from one repository with the -all option instead of letting each snapshot on the storage being pruned separately. This is even supported by this tool as all defaults to true but running multiple prune --all one after the other is superfluous.

I currently want to back up 3 different repositories to the same storage location and thought I just define the prune -all for one, but I can't do that because it forces me to define a prune for each of my repository config files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant