# Restore testing with weird results

**URL:** https://forum.duplicati.com/t/restore-testing-with-weird-results/9163
**Category:** Support
**Created:** [February 12, 2020, 11:00am UTC](https://forum.duplicati.com/t/restore-testing-with-weird-results/9163 "2020-02-12T11:00:58Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [February 14, 2020, 6:23pm UTC](https://forum.duplicati.com/t/restore-testing-with-weird-results/9163/7 "2020-02-14T18:23:24Z")

</div>

> [@Kliko](#):
>
> What I can answer right now is that I’ve never used upload throttling.

That gets one suspect out of the way. A quick glance at Jottacloud also looked clean (unlike others). Actually studying the damage could be done with a look in the database plus a close view of the file.  
Database has expected length and hash in RemoteVolumeTable. Hash work is a bit more indirect…

[–upload-verification-file](https://duplicati.readthedocs.io/en/latest/06-advanced-options/#upload-verification-file) can avoid viewing the DB, e.g. in [DB Browser for SQLite](https://sqlitebrowser.org/), if that’s any easier.

---

_[View the full topic](https://forum.duplicati.com/t/restore-testing-with-weird-results/9163)._