# Recovering data from corrupt folder

**URL:** <https://forums.foundationdb.org/t/recovering-data-from-corrupt-folder/4658>\
**Category:** Using FoundationDB\
**Created:** [October 13, 2024, 5:43am UTC](https://forums.foundationdb.org/t/recovering-data-from-corrupt-folder/4658 "2024-10-13T05:43:21Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![swr](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/swr/32/1643_2.png) [@swr](https://forums.foundationdb.org/u/swr)\
**Post date:** [October 14, 2024, 1:52pm UTC](https://forums.foundationdb.org/t/recovering-data-from-corrupt-folder/4658/4 "2024-10-14T13:52:10Z")

</div>

I’m pretty sure that the `kvfiledump` role is for “emergency” recoveries like this… I don’t think it’s part of a supported backup/restore path. I suspect you would need to build your own tooling to write these K/V pairs back to the database again (perhaps as part of your application that’s already connecting to FDB.)

The [`fdbbackup` and `fdbrestore`](https://apple.github.io/foundationdb/backups.html#fdbrestore-command-line-tool) tools (and the [disk snapshot backup](https://apple.github.io/foundationdb/disk-snapshot-backup.html) alternative) both have supported restore paths, if you want a more reliable way to do this in the future.

---

_[View the full topic](https://forums.foundationdb.org/t/recovering-data-from-corrupt-folder/4658)._