Backup & Restore files - copy volumes and included bind files to folder, restore files from same folder. #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er, restore files from same folder.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is conceptually similar to the tar output, but rsync copy all the files to a folder instead.
On a computer where backup is re-run regularly, only changed files will be copied so a significant speed-up will be seen.
It also means that if a third party incremental-style backup is used on the computer, it can be pointed to the backup folder of files and only backup changes, rather than the entire tar each time.
This folder can be restored from, unlike when a third party tool is used via the --launch arg.
Edit: I think there's an issue with this still in the rsync args, the owner attributes on the files aren't being preserved currently which then breaks any restored containers that use non-root users internally.