Difference between revisions of "Last resort restore"
(Created page with "Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful. The following is t...") |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful. | Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful. | ||
The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation. | The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation. | ||
| + | In practical terms, it means that if something goes wrong with this guide and your machine explodes, you were warned and are the sole responsible for the event. | ||
=== Test with a fresh data directory === | === Test with a fresh data directory === | ||
| Line 10: | Line 11: | ||
=== Import raw data from backup === | === Import raw data from backup === | ||
| − | Open your renamed folder, get into the <code>btc_mainnet/db</code> folder, and sort files by "last modified" descending, you are looking for | + | Open your renamed folder, get into the <code>btc_mainnet/db</code> folder, and sort files by "last modified" descending, you are looking for those files that were modified most recently, all of them in the same day (presumably the last day your Bisq was operational).<br> |
The list should include:<br> | The list should include:<br> | ||
| − | <code>BsqSwapTrades<br> | + | <code><br>BsqSwapTrades<br> |
DisputeList<br> | DisputeList<br> | ||
RefundDisputeList<br> | RefundDisputeList<br> | ||
| Line 43: | Line 44: | ||
Copy all the above files in the corresponding <code>btc_mainnet/db</code> folder of your fresh data directory, overwriting the existing ones. | Copy all the above files in the corresponding <code>btc_mainnet/db</code> folder of your fresh data directory, overwriting the existing ones. | ||
| − | Then, delete from the fresh data directory, and replace with copies from the old | + | Then, delete from the fresh data directory, and replace with copies from the old directory, the following folders:<br> |
<code>btc_mainnet/keys<br> | <code>btc_mainnet/keys<br> | ||
btc_mainnet/wallet<br> | btc_mainnet/wallet<br> | ||
| Line 49: | Line 50: | ||
</code> | </code> | ||
| − | Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored;if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created. | + | Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored; if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created. |
| + | |||
| + | If anything is off with the wallet balances shown by Bisq after this restore, you can try a SPV resync (or more) | ||
Latest revision as of 13:21, 28 April 2023
Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful. The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation. In practical terms, it means that if something goes wrong with this guide and your machine explodes, you were warned and are the sole responsible for the event.
Test with a fresh data directory
First of all, make sure you have the latest version installed, and Bisq is closed (terminate orphan existing processes if any), then rename your data directory by changing Bisq to, for example, Bisq.old.
Start Bisq again: it should start into a 100% new instance, creating a brand new Bisq folder (if it doesn't, try uninstalling and then reinstalling Bisq).
Close Bisq again: we are going to use the freshly created Data Directory as a stump to populate with our old data.
Import raw data from backup
Open your renamed folder, get into the btc_mainnet/db folder, and sort files by "last modified" descending, you are looking for those files that were modified most recently, all of them in the same day (presumably the last day your Bisq was operational).
The list should include:
BsqSwapTrades
DisputeList
RefundDisputeList
SequenceNumberMap
MyVoteList
OpenOffers
MyBlindVoteList
ClosedTrades
MediationDisputeList
MyProposalList
MailboxMessageList
AccountAgeWitnessStore
PendingTrades
MyProofOfBurnList
PreferencesPayload
UserPayload
AddressEntryList
FailedTrades
MyReputationList
TempProposalStore
NavigationPath
UnconfirmedBsqChangeOutputList
IgnoredMailboxMap
PeerList
RemovedPayloadsMap
TradeStatistics3Store
SignedWitnessStore
Copy all the above files in the corresponding btc_mainnet/db folder of your fresh data directory, overwriting the existing ones.
Then, delete from the fresh data directory, and replace with copies from the old directory, the following folders:
btc_mainnet/keys
btc_mainnet/wallet
btc_mainnet/tor/hiddenservice
Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored; if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created.
If anything is off with the wallet balances shown by Bisq after this restore, you can try a SPV resync (or more)
