# Restore Hash Failed - How to retry/restore from other backup?
**URL:** https://forum.duplicati.com/t/restore-hash-failed-how-to-retry-restore-from-other-backup/15616
**Category:** Support
**Created:** [January 19, 2023, 11:06am UTC](https://forum.duplicati.com/t/restore-hash-failed-how-to-retry-restore-from-other-backup/15616 "2023-01-19T11:06:23Z")
**Posts on this page:** 1
**Showing post:** 3
### Author:  [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [January 19, 2023, 3:36pm UTC](https://forum.duplicati.com/t/restore-hash-failed-how-to-retry-restore-from-other-backup/15616/3 "2023-01-19T15:36:21Z")
Welcome to the forum @adamlove
> [@adamlove](#):
>
> is there a fast way to get it to ‘retry’
The easy slow way is to just run again. Any file whose content is already correct won’t need a patch.
This should reduce the amount of downloading. What storage type is the Destination, and how fast?
There’s a nice CLI example of the download reduction on second try to the same restore folder [here](https://forum.duplicati.com/t/how-to-use-backup-json-file-with-duplicati-cli/15482/23).
> [@adamlove](#):
>
> ```plaintext
> 2023-01-19 17:23:33 +11 - [Error-Duplicati.Library.Main.Operation.RestoreHandler-PatchingFailed]: Failed to patch with remote file: "duplicati-bcdf22a29adb8413fa810d73aa043f1e6.dblock.zip.aes", message: Failed to decrypt data (invalid passphrase?): Message has been altered, do not trust content
>
> ```
looks like it broke a file. Maybe that file had content common to all of the files that couldn’t be rebuilt.
[Disaster Recovery](https://duplicati.readthedocs.io/en/latest/08-disaster-recovery/) talks about this, e.g. the [affected](https://duplicati.readthedocs.io/en/latest/04-using-duplicati-from-the-command-line/#the-affected-command) command which you could run in [Commandline](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#using-the-command-line-tools-from-within-the-graphical-user-interface).
You can also inspect `duplicati-bcdf22a29adb8413fa810d73aa043f1e6.dblock.zip.aes` for an unexpectedly new timestamp, check its size, try decrypt with [AES Crypt](https://www.aescrypt.com/) or Duplicati SharpAESCrypt.
Destination [dblock files contain blocks from source files](https://duplicati.readthedocs.io/en/latest/appendix-a-how-the-backup-process-works/). Ideally you can find a good one. Long shot?
> [@adamlove](#):
>
> attempt restoring from a backup from another time where the file may have been slightly different?
[Implementing the feature to restore any version of a single file](https://forum.duplicati.com/t/implementing-the-feature-to-restore-any-version-of-a-single-file/14318) might help with that. Not released yet.
[Restoring files from a backup](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#restoring-files-from-a-backup) will let you pick any backup date to look (or search) for a file of interest.
It’s kind of awkward. Looking in a copy of the [database](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#database-management) with [DB Browser for SQLite](https://sqlitebrowser.org/) in `File` view can easily let you filter any `Path` of interest. If only one row shows up, there’s only one version of that file.
If you’re nervous about these experiments, you can do test restores into a different folder one by one.
This might take less machine time at the expense of more of your time leading the experimentation…
> [@adamlove](#):
>
> Does it only calculate the hash once, or does it retry?
Probably once, but it did it on lots of files. If disk activity hurts file reading that badly, that’s a big issue.
> [@adamlove](#):
>
> Ultimately, if I could get a list of files that failed
I’m confused. Didn’t you post the list? Whether GUI or CLI, a human-driven retry attempt needs the list.
> [@adamlove](#):
>
> “command line” function to attempt restore from other earlier instances of the files?
[The RESTORE command](https://duplicati.readthedocs.io/en/latest/04-using-duplicati-from-the-command-line/#the-restore-command)
> `--version=`
> Restore files from a specific backup.
[The FIND command](https://duplicati.readthedocs.io/en/latest/04-using-duplicati-from-the-command-line/#the-find-command)
> If no `` is specified, a list of all available backups is shown.
(version number is on the left, just like it is on the GUI `Restore` selector.
> If entire path is specified, all available versions of the file are listed.
> `--all-versions=`
> Searches in all backup sets, instead of just searching the latest.
actually might be a way to see which file versions had a path of interest, without looking inside the DB.
You probably wouldn’t be able to recognize actual different versions of the file, just versions that had it.
> [@Xavron](#):
>
> you can select individual files
One can also use the search box to help with finding a file if it happens to be deep in a folder structure.
Most or all of the posted errors are in `D:\iTunes\iTunes Media\Music` though. Just open that folder.
You can try the files one at a time or check all the ones that you want to try from that particular version.
---
_[View the full topic](https://forum.duplicati.com/t/restore-hash-failed-how-to-retry-restore-from-other-backup/15616)._