<p>In some cases, bitcoin-qt/bitcoind may regularly (and even gratuitously) flush the wallet [1], so it's possible that wallet.dat could be in an inconsistent state at the time you make your own copy.</p>

<p>The <strong>backupwallet</strong> RPC call should be a safe way to accomplish this.</p>

<p>[1] <a href="https://github.com/bitcoin/bitcoin/issues/10236" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues/10236</a></p>

CC BY-SA 4.0
2019-03-14T03:41:25.507Z
2019-03-14T03:41:25.507Z
rowan194
<p>Is it safe to copy wallet.dat while the daemon is running, or should the daemon be stopped before doing so?</p>

<p>I'd imagine it would be safe unless addresses are being generated exactly at the same time.</p>

<bitcoin-core><bitcoind><wallet><daemon>
Bitcoind live wallet backup (by copying wallet.dat)
tsujp
# Bitcoind live wallet backup (by copying wallet.dat)

(Asked by: username_0 on 2019-03-14)

Is it safe to copy wallet.dat while the daemon is running, or should the daemon be stopped before doing so?

I'd imagine it would be safe unless addresses are being generated exactly at the same time.

**Tags:** bitcoin-core, bitcoind, wallet, daemon


---

## 1 answers

### Answer by username_1 on 2019-03-14. Score: 1

In some cases, bitcoin-qt/bitcoind may regularly (and even gratuitously) flush the wallet [1], so it's possible that wallet.dat could be in an inconsistent state at the time you make your own copy.

The **backupwallet** RPC call should be a safe way to accomplish this.

[1] <https://github.com/bitcoin/bitcoin/issues/10236>


---

