# Fatal Error: Corrupted backup data

**URL:** <https://forums.foundationdb.org/t/fatal-error-corrupted-backup-data/1260>\
**Category:** Using FoundationDB\
**Created:** [March 26, 2019, 10:17am UTC](https://forums.foundationdb.org/t/fatal-error-corrupted-backup-data/1260 "2019-03-26T10:17:46Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![SteavedHams](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/steavedhams/32/18_2.png) [@SteavedHams](https://forums.foundationdb.org/u/SteavedHams)\
**Post date:** [March 26, 2019, 8:46pm UTC](https://forums.foundationdb.org/t/fatal-error-corrupted-backup-data/1260/3 "2019-03-26T20:46:25Z")

</div>

The timestamps being in the future due to a bug which has been fixed in 6.1. The bug is that restore assumes it can use the destination cluster to do version-\>timestamp conversion, which doesn’t work if you are restoring into a different cluster than the source of the backup.

That specific version mismatch actually should not cause a problem. 6.0.18 should be able to read backups created from (I think) 5.1 and later.

If you can reproduce the error, try adding --log to get a trace file, it may provide more detail.

---

_[View the full topic](https://forums.foundationdb.org/t/fatal-error-corrupted-backup-data/1260)._