Skip to content
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

Incremental restore vs full restore #7

Open
andrewchambers opened this issue Sep 6, 2022 · 4 comments
Open

Incremental restore vs full restore #7

andrewchambers opened this issue Sep 6, 2022 · 4 comments

Comments

@andrewchambers
Copy link
Contributor

Bupstash supports incremental restores - it will only download files it detects have changed. This may be faster, I am not sure if other tools support this.

@basldfalksjdf
Copy link
Contributor

This sounds like a really cool feature. But, out of curiosity, what is the use case for such a feature? An easy way to restore to an earlier snapshot rather than disaster recovery?

@andrewchambers
Copy link
Contributor Author

andrewchambers commented Sep 7, 2022

Bupstash doesn't support mounting a filesystem as shown in the table - but as an alternative you can 'checkout' directories more like git and browse them, to do these checkouts efficiently it has incremental restore. It also functions as a way to resume restores that were interrupted.

@blackbit47
Copy link

Duplicacy always does incremental restores.
It will not download data that is already there unless you tell it to overwrite.

@basldfalksjdf
Copy link
Contributor

Duplicacy always does incremental restores. It will not download data that is already there unless you tell it to overwrite.

Kopia can also ignore restoring existing files, but I am not sure that is the same thing as what @andrewchambers is saying bupstash has. Ignoring existing files is not the same as only restoring a file if it has changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants