Skip to content

Buckup failes due to "Document {DocumentId} seems to have a attachment hash: {Hash}, but no correlating hash was found in the storage." #17470

Answered by shiranshalom
oiBio asked this question in Q&A
Discussion options

You must be logged in to vote

Hi Tobias Bartsch,
I see that you had a similar issue before (#16624); we have fixed it in 5.4.105 (thanks to you :)). In addition, we recently found and handled (available in 5.4.111) another edge case related (https://issues.hibernatingrhinos.com/issue/RavenDB-20608/Excessive-number-of-revisions-after-replication-from-sharded-to-non-sharded).
To resume your Backup task, you can do the same as suggested here: #16624 (comment)

Thanks!

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@oiBio
Comment options

Answer selected by oiBio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants