Release 2.0.0a4 - alpha quality, for testing only #6872
Replies: 4 comments 4 replies
-
Guess this is the last alpha release. #6871 is a known issue maybe some freebsd user/developer can have a look at that. |
Beta Was this translation helpful? Give feedback.
-
What is the expected behavior when transferring from 1.2 to a repo created without --other-repo? Currently it seems like the transfer completes without error, but just leaves inaccessible data in the new repo. |
Beta Was this translation helpful? Give feedback.
-
If you do a borg init without --other-repo, the key and secret material will be random and unique. This affects usage of this repo in 2 ways:
If you borg init --other-repo=OLDREPO, it will just re-use the key and secret material from the old repo, so chunk cutting and ID computation works in exactly the same way. This is strongly recommended for better deduplication. Other applications for having the same key material in multiple new "related" repos:
You'ld notice the bad dedup (== no dedup) after the first new backup. |
Beta Was this translation helpful? Give feedback.
-
What exactly do you mean by "inaccessible data"? |
Beta Was this translation helpful? Give feedback.
-
borgbackup 2.0.0a4 alpha release - do not use this on production backup repositories.
Long changelog:
https://borgbackup.readthedocs.io/en/2.0.0a4/changes.html#version-2-0-0a4-2022-07-17
If you use pip to install this, use: pip install "borgbackup==2.0.0a4"
Docs: https://borgbackup.readthedocs.io/en/2.0.0a4/
Feedback:
This discussion was created from the release Release 2.0.0a4 - alpha quality, for testing only.
Beta Was this translation helpful? Give feedback.
All reactions