Dealing with multiple remote repositories #159
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#159
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?
Hi there, I have a config like so:
Where each repository has:
BORG_PASSPHRASE
(encryption_passphrase
)ssh_command
)This use case is where I have a local backup and identical remotes for redundancy. However, I can't trust all remotes, the SSH configurations are different and passwords are too.
So, I need this kind of "per-repository" option configuration. I could create new folders under
/etc/borgmatic.d/
and use separate configurations but then my backup would have to run twice :/Looking at the schema right now (
3cb52423d2/borgmatic/config/schema.yaml
), I am not sure this is possible.Oh, I see witten/borgmatic#118 now ...
Hmmm, https://borgbackup.readthedocs.io/en/stable/faq.html#can-i-copy-or-synchronize-my-repo-to-another-location seems to recommend creating two separate repositories ... which means running twice is the default !? Looks like nothing borgmatic needs to deal with then ;)
Sorry for the noise!
Not a problem! When you specify multiple repositories in a list as per your example, borgmatic does run Borg twice. But the recommended approach with borgmatic if your repository options differ would indeed be to create separate config files in
/etc/borgmatic.d/
, optionally sharing any config that you want to share via includes. Hope that works out for you.