Multiple repositories with dedicated source_directories in one config #118
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#118
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?
If we put source_directories with multiple repositories, each repository will have the same directories backed up, right?
So if I want to have a repository for one thing and another for something else, I must create two config files?
That's a bit annoying if so
WHy not a:
Note: I don't exactly understand why there is a list actually for "repositories", is it to make a backup in different sites?
If you have multiple
repositories
listed in a single config file then, yes, each repository will have the same source directories backed up. Here's the comment/documentation on borgmaticrepositories
:The rationale is that the user may want to create multiple identical backups with different providers for increased redundancy. For instance, one local repository for quick access to files and one remote repository in case the local repository is destroyed. Or just two different remote repositories in different physical locations.
If you mean one repository with one set of source directories, and another repository with a different set of source directories, then yes, you'll need two different config files right now.
As for your nested
repositories
/source_directories
suggestion, you may want to check out some of the prior discussion on this ticket: witten/borgmatic#73Could you say a little more about the issue with multiple configuration files? Is it just that you'd find yourself having to duplicate configuration among them?
"Is it just that you’d find yourself having to duplicate configuration among them?"
Exactly :P
And thank you for all answers, very clear.
Thanks.. I think I understand the need now. I'll have to think through some of the options including the one you suggested. Feel free to add more ideas as well.
Offtopic: Are you a teacher irl? you're so good at explaining stuff, for real, each time I asked here it was a pleasure to read the answer.
Haha, thank you! No, I'm not a teacher. But as a software engineer, I often have to explain features/code to other engineers or stakeholders.
With #148 implemented, you can now share common configuration between multiple separate configuration files. So for instance, let's say that you create two separate configuration files, each one to backup a different repository with different source directories. Then, assuming that you have common config options that you want to share across those config files, you can use the new include feature to pull in shared configuration options.
See #148 and this documentation for details.