Minimal implementation of "related repositories" for Borg 1.4.x.#9645
Merged
ThomasWaldmann merged 1 commit intoMay 15, 2026
Merged
Conversation
ThomasWaldmann
force-pushed
the
related-repos-1.4
branch
from
1dcd7b2 to
76b7302
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 1.4-maint #9645 +/- ##
=============================================
- Coverage 81.99% 81.97% -0.02%
=============================================
Files 38 38
Lines 11329 11365 +36
Branches 1788 1793 +5
=============================================
+ Hits 9289 9317 +28
- Misses 1454 1460 +6
- Partials 586 588 +2 ☔ View full report in Codecov by Sentry. |
ThomasWaldmann
force-pushed
the
related-repos-1.4
branch
3 times, most recently
from
742573b to
1710da3
Compare
This feature allows multiple repositories to share deduplication-relevant secrets (id_key and chunk_seed) while maintaining secure, independent encryption keys. `borg key export-related-secrets <REPO> <SPATH>` to export the secrets to a JSON file. `borg init --import-related-secrets <SPATH> <REPO>` to initialize a new repository using the secrets from the JSON file. Both repositories must use the same chunk id algorithm (both HMAC-SHA256 or both BLAKE2b). If you create related repositories with borg 1.4.x, you can later transfer their archives to one or multiple related new borg2 repositories without breaking deduplication. But please note that we might remove BLAKE2b support for new borg2 repos, see borgbackup#8867, so this might only work for HMAC-SHA256 in the end.
ThomasWaldmann
force-pushed
the
related-repos-1.4
branch
from
1710da3 to
5035710
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This feature allows multiple repositories to share deduplication-relevant secrets (id_key and chunk_seed) while maintaining secure, independent encryption keys.
borg key export-related-secrets <REPO> <SPATH>to export the secrets to a JSON file.borg init --import-related-secrets <SPATH> <REPO>to initialize a new repository using the secrets from the JSON file.Both repositories must use the same chunk id algorithm (both HMAC-SHA256 or both BLAKE2b).
If you create related repositories with borg 1.4.x, you can later transfer their archives to one or multiple related new borg2 repositories without breaking deduplication.
But please note that we might remove BLAKE2b support for new borg2 repos, see #8867, so this might only work for HMAC-SHA256 in the end.