# Upgraded to 0.9.4, lost all history **URL:** \ **Category:** Support\ **Created:** [February 23, 2019, 6:52pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121 "2019-02-23T18:52:04Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![sleepyhead](https://bisq.community/letter_avatar/sleepyhead/32/5_5575768a8748004e209b776fc1b2916d.png) [@sleepyhead](https://bisq.community/u/sleepyhead)\ **Post date:** [February 23, 2019, 6:52pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/1 "2019-02-23T18:52:05Z")
Is there a way to restore the history? Edit: Running on Linux Mint 17.3, 64bit. ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [February 23, 2019, 7:02pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/2 "2019-02-23T19:02:06Z")
Do you have a backup of your old (pre-v0.9.4) data directory ? ---
**Author:** ![sleepyhead](https://bisq.community/letter_avatar/sleepyhead/32/5_5575768a8748004e209b776fc1b2916d.png) [@sleepyhead](https://bisq.community/u/sleepyhead)\ **Post date:** [February 23, 2019, 8:17pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/3 "2019-02-23T20:17:28Z")
I don’t know. I think Bisq automatically creates backups, but I can’t find anywhere in the settings where that backup is supposed to be. Edit: I found the following: ~/.local/share/Bisq/btc\_mainnet/wallet/backup $ ls -l total 8 drwxr-xr-x 2 doug doug 4096 Feb 21 21:31 backups\_bisq\_BSQ\_wallet drwxr-xr-x 2 doug doug 4096 Feb 21 21:31 backups\_bisq\_BTC\_wallet Keep in mind, I don’t need to restore the wallet. I didn’t lose any Bitcoins. I just want to restore the history of my transactions. ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [February 24, 2019, 12:27pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/4 "2019-02-24T12:27:29Z")
I am not sure. You could try deleting the SPV chain file in Settings, but I have my doubts that would help. Not sure why you lost your history in the first place. It sounds like a bug. ---
**Author:** ![sleepyhead](https://bisq.community/letter_avatar/sleepyhead/32/5_5575768a8748004e209b776fc1b2916d.png) [@sleepyhead](https://bisq.community/u/sleepyhead)\ **Post date:** [February 24, 2019, 3:46pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/5 "2019-02-24T15:46:54Z")
I tried deleting the SPV file, but still missing the history. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [February 28, 2019, 4:39am UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/6 "2019-02-28T04:39:46Z")
I doubt it is related to the update but rather some weird coincidence with some bug or hard disk write issue. Open the data directory (at account/backup) and look into the db folder. There is a backup folder with a backups\_ClosedTrades folder. There u have the latest backups. Try to find the one by date before the issue happened. make a backup before doing anything. shut down bisq and copy the last intact backup and rename it to ClosedTrades and replace the one in the db folder. if u had new added closed trades those would be replaced then with the old file. there is no way to merge it… ---
**Author:** ![sleepyhead](https://bisq.community/letter_avatar/sleepyhead/32/5_5575768a8748004e209b776fc1b2916d.png) [@sleepyhead](https://bisq.community/u/sleepyhead)\ **Post date:** [February 28, 2019, 5:55am UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/7 "2019-02-28T05:55:14Z")
Manfred, Thanks for the help! Actually, you’re right, it looks like the problem actually happened at Feb 14 09:40, days before the upgrade was released. I say this because I found this: doug@Fujitsu ~/.local/share/Bisq/btc\_mainnet/db/backup\_of\_corrupted\_data $ ls -l total 3352 -rw-r–r-- 1 doug doug 2114062 Feb 14 09:40 ClosedTrades -rw-r–r-- 1 doug doug 1297224 Jan 5 20:32 DisputeList I tried to move this ClosedTrades file to the db folder, but since it’s corrupted, a new blank one was created. Is there some kind of maintenance tool I can run against this file to try to fix it? Thanks! ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [February 28, 2019, 7:01am UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/8 "2019-02-28T07:01:45Z")
I fear not. But as said you should find older backups. ---
**Author:** ![sleepyhead](https://bisq.community/letter_avatar/sleepyhead/32/5_5575768a8748004e209b776fc1b2916d.png) [@sleepyhead](https://bisq.community/u/sleepyhead)\ **Post date:** [February 28, 2019, 2:29pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/9 "2019-02-28T14:29:29Z")
No, unfortunately all the backups are newer than the corrupted one. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [March 8, 2019, 5:17pm UTC](https://bisq.community/t/upgraded-to-0-9-4-lost-all-history/7121/10 "2019-03-08T17:17:11Z")
I found the issue for that and it is fixed on master, so if you run from source you have the fix already. Otherwise in the next release in 2-3 weeks. The reason was that a few deprecated payment methods (Venmo, CahsApp, OkPay) have been removed from code base and that caused an exception at reading the protobuffer content of the ClosedTrades db file. I added it again and now its fine again. If you had that issue just take the older backup from the db/backup/backups\_ClosedTrades folder and replace the ClosedTrades file in the db folder (after you have updated to the new version where the issue is fixed). Make a backup before doing that just to be safe!