Eli6
April 8, 2025, 9:26am
1
The restore continues til it reaches a TB and then crashes. It could be because of RAM limitation, although I still have 2GB left for the entire system.
When I run it again, I want it to skip data already restored. Does it behave like this?
Update
I see this mentioned here
master ← MichaelEischer:restore-skip-unchanged
opened 04:35PM - 31 May 24 UTC
What does this PR change? What problem does it solve?
-------------------------… ----------------------------
Based on https://github.com/restic/restic/pull/4837 .
On startup, the `restore` command now checks existing files to determine whether these have to be updated. By default, it verifies the full file content. To only checks whether the file size and modification time (mtime) match with those in the snapshot, use `--overwrite if-changed`. Files with matching file content will not be downloaded during the restore operation. Only their file metadata is updated.
Was the change previously discussed in an issue or on the forum?
----------------------------------------------------------------
See #4817
Fixes https://github.com/restic/restic/issues/407
Fixes https://github.com/restic/restic/issues/2662
Checklist
---------
- [x] I have read the [contribution guidelines](https://github.com/restic/restic/blob/master/CONTRIBUTING.md#providing-patches).
- [x] I have [enabled maintainer edits](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
- [x] I have added tests for all code changes.
- [x] I have added documentation for relevant changes (in the manual).
- [x] There's a new file in `changelog/unreleased/` that describes the changes for our users (see [template](https://github.com/restic/restic/blob/master/changelog/TEMPLATE)).
- [x] I have run `gofmt` on the code in all commits.
- [x] All commit messages are formatted in the same style as [the other commits in the repo](https://github.com/restic/restic/blob/master/CONTRIBUTING.md#git-commits).
- [x] I'm done! This pull request is ready for review.
Does restore resume by default (in latest version 17 versions)? Or we have to use flag —overwrite=if-changed ?
1 Like
Eli6
April 8, 2025, 11:40am
3
Damn it, I read that page except skipping in-place section.
I’m not sure if it makes sense to stop the second round of restic restore with no flag that is currently running.
The default should not restore files already restored to speed up the process. No point in restoring the same files again.
2 Likes
Indeed no point to stop. If a file is already fully restored it won’t be restored second time by default. But will be checked (read and hashed). It is IMO the best option to continue interrupted restore operation.
1 Like