-
Notifications
You must be signed in to change notification settings - Fork 25
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
Implement rdiff-backup support #59
Comments
I'ld guess for a simple implementation that would be also the way to go with With a lot of effort one could theoretically maybe avoid that full extractions get written to disk, but I guess that would be too much work for just single-time use (per user). It's not just the file names and content, we also would need to care for all the other metadata. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://rdiff-backup.net/ is another common backup tool. Implementing the importer might be a bit easier due to the fact that it's also written in python.
I've written a shell script that does it, however it's quite cumbersome as it requires the full extraction of a snapshot for borg to back it up, and rdiff-backup isn't very smart on restore (it restores a file even if it's unchanged).
The text was updated successfully, but these errors were encountered: