-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Discussion] Remove Snapshot merging / legacy Code? #43
Comments
what do you propose? |
Add option --disable-merge-snapshot to disable merge. |
There's no need to do, because it won't merge snapshots in --renew mode. in --keep mode it does behave like it always did. |
What idea do you have for this? |
The idea was to compeltely remove all merge logic since it you might not detect if something goes wrong until you try to restore stuff. For now let's keep it in, and keep backwards compatibility.. |
Ok for me good idea remove all merge logic |
Since there are currently two approaches in the Codebase, I want to discuss if you want to keep the ability to merge snapshots into each other. I personally wouldn't dare to go on and take one Base Snapshot in a year, and then only merge onto it. And: There's no way to merge into the Basecopy, so the volatile data would accumulate in the first Differential file after the Basecopy.
The text was updated successfully, but these errors were encountered: