Replies: 2 comments 1 reply
-
|
The repo id is in the repo config, so it can be changed easily. But while that somehow works, it does of course not change the encryption key, so the crypto problem of nonce reuse (if you update the original repo and the copy of the repo independently) still remains. So guess that mode of operations is nothing we want to encourage. |
Beta Was this translation helpful? Give feedback.
-
|
I am now in this condition, since I have found an old copy of some repo (that exists because of a disk upgrade) and I need to check if it contains something that was pruned from the current copy. Borg refuses to list the repo. I have a few questions:
|
Beta Was this translation helpful? Give feedback.
-
|
You want to avoid cache confusion. So just change the repo ID before using. You can also switch the repo to append-only. Completely read-only is difficult, because borg always wants to create a lock in there. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys.
I read here that a copy of a repo, when borg complains about the same ID, needs a new/different ID as a "fix"
I wonder - if this is "approved" way for such cases, @devel - why not add it, make it "official" in the toolset, as an arg/option.
Lastly - would there be a good/recommended method to generate new IDs with/for borg?
many thanks, L.
Beta Was this translation helpful? Give feedback.
All reactions