<p>This is doable. You can run as many nodes with the same wallets as you want.
I imagine you want to do this because the synchronisation process will be faster on another node?
After the process is done, you will have to copy the complete <strong>blockchain data</strong>, not the wallet itself.</p>

<p>You might want to consider checking for what your bottleneck is - could be the hard disk or the CPU, or in some cases the internet bandwidth.</p>

CC BY-SA 4.0
2020-03-25T12:10:36.087Z
by `complete blockchain data` you mean full `.bitcoin` folder with wallets, blocks etc.?
Gleb
CC BY-SA 4.0
2020-03-25T12:14:52.667Z
during wallets synchronization, our bitcoin node stops to respond on any other requests (creating transactions, loading wallets balance...). So, I tend to think that the bottleneck here is the node itself. That's why would like to perform a sync on the separate server
Gleb
CC BY-SA 4.0
2020-03-26T13:45:02.783Z
I think the whole .bitcoin folder should suffice, yes. It's been a while since I've done that so I'm not 100% sure. If you do it correctly, you won't be prompted to rebuild the indexes. Have you checked the disk and CPU usage?
GChuf
CC BY-SA 4.0
2020-03-26T13:53:16.697Z
Yes, we did. During the process, one core of CPU is busy for 100%.
Gleb
CC BY-SA 4.0
2020-03-26T13:59:53.857Z
I'm not sure why there's only one core at 100%. All cores should be doing the work. Anyway, if the CPU is at 100%, that means the CPU is the bottleneck and you need a faster CPU for faster synchronization times.
You should also update to the newest bitcoind version and use more cache (memory) with -dbcache option. The default is 450 I think, you can bump that to 5000.
GChuf
CC BY-SA 4.0
2020-03-26T14:04:20.953Z
ok, I will keep investigating. thanks
Gleb
CC BY-SA 4.0
2020-03-24T20:19:56.747Z
2020-03-24T20:19:56.747Z
GChuf
<p>We have a full Bitcoin node with its wallets on the server. The issue is that the majority of our wallets were synchronized long time ago. For us, it would seem that this synchronization task can take a significant amount of time in which the Bitcoin node will be unreachable for all other requests and our server will be unavailable for users.</p>

<p>We think about replicating the current Bitcoin node on the separate server and synchronize wallets there. After this process will be finished we will copy wallets back to the origin server. </p>

<p>Is it doable? Or we can't have the same wallets on two different Bitcoin nodes?</p>

<bitcoin-core><wallet>
Can I run 2 Bitcoin nodes with the same wallets?
Gleb
# Can I run 2 Bitcoin nodes with the same wallets?

(Asked by: username_0 on 2020-03-24)

We have a full Bitcoin node with its wallets on the server. The issue is that the majority of our wallets were synchronized long time ago. For us, it would seem that this synchronization task can take a significant amount of time in which the Bitcoin node will be unreachable for all other requests and our server will be unavailable for users.

We think about replicating the current Bitcoin node on the separate server and synchronize wallets there. After this process will be finished we will copy wallets back to the origin server.

Is it doable? Or we can't have the same wallets on two different Bitcoin nodes?

**Tags:** bitcoin-core, wallet


---

## 1 answers

### Answer by username_1 on 2020-03-24. Score: 1 | Accepted answer

This is doable. You can run as many nodes with the same wallets as you want.
I imagine you want to do this because the synchronisation process will be faster on another node?
After the process is done, you will have to copy the complete **blockchain data**, not the wallet itself.

You might want to consider checking for what your bottleneck is - could be the hard disk or the CPU, or in some cases the internet bandwidth.

> **Comments:**
> **username_0**: by `complete blockchain data` you mean full `.bitcoin` folder with wallets, blocks etc.?  
> **username_0**: during wallets synchronization, our bitcoin node stops to respond on any other requests (creating transactions, loading wallets balance...). So, I tend to think that the bottleneck here is the node itself. That's why would like to perform a sync on the separate server  
> **username_1**: I think the whole .bitcoin folder should suffice, yes. It's been a while since I've done that so I'm not 100% sure. If you do it correctly, you won't be prompted to rebuild the indexes. Have you checked the disk and CPU usage?  
> **username_0**: Yes, we did. During the process, one core of CPU is busy for 100%.  
> **username_1**: I'm not sure why there's only one core at 100%. All cores should be doing the work. Anyway, if the CPU is at 100%, that means the CPU is the bottleneck and you need a faster CPU for faster synchronization times. You should also update to the newest bitcoind version and use more cache (memory) with -dbcache option. The default is 450 I think, you can bump that to 5000.  
> **username_0**: ok, I will keep investigating. thanks  

---

