Buckup failes due to "Document {DocumentId} seems to have a attachment hash: {Hash}, but no correlating hash was found in the storage." #17470
-
I have several Databases where i cant performe my backup anymore. I seems like the attachment of the revision is not available anymore. I can access the current attachment via code and studio, but cannot access the attachment from the revision. This problem occurs on several databases, but not on all. Is there a known bug for this or how can this happen?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi Tobias Bartsch, Thanks! |
Beta Was this translation helpful? Give feedback.
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!