-
-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repo: to upgrade or not to upgrade... #6569
Comments
Optionsdo a breaking change (borg 2.0 would not read, write or upgrade old repos):
stay compatible (release as borg 1.3)
|
I'd vote for the "breaking change" approach. |
Any solution that doesn't support migration or requires twice the disk space to migrate because the repository data file format changes and restartable in-place migration is not supported is obviously completely unacceptable (since there may not be enough disk space to do the migration). So if you want a new repository format you need to either support reading data files in the current format forever, or provide proper upgrade code that can convert file by file and can handle repositories in a partially upgraded state by resuming the upgrade properly, and ideally provide both of those features. My suggestion is to:
|
@bill-myers see #6703 for the current approach. That supports migration, but you'll need a new repo for it (and the space for the new repo). Everybody not having the space (yet) can also just continue using the old borg version until the space situation at the current repo location improves or until stuff is moved to another location anyway. An in-place migration likely won't happen due to the complexity of the changes, see also #6602. |
I support the BC 2.0 version. We should not sacrifice faster, cleaner and less complex code to backwards compatibility. |
Can anything be done to easily make borg1.x and borg2 coexist? (namespacing?) I realise skilled admins will probably be able to install both in different paths but having builtin support will make distro packaging for users who need both during transition easier. |
guess we can close this one and continue there. |
borg helium milestone (current master branch) will be reached quicker than expected and there will be some major changes:
the new crypto and the new repo format have some major advantages (and the old code / old repos have some major disadvantages), so it would be good to get everything to the new stuff and also get rid of the old stuff ASAP.
the question is how we get there, considering:
The text was updated successfully, but these errors were encountered: