Code:
cp -r blocks chainstate indexes
You run it twice; one from your node to a hard drive, and the second from your hard drive to your other computer.
Topic: Duplicating BitcoinCore reorg (Read 123 times)
Copy indexes too, if you're running Bitcoin Core with txindex=1. If you're at linux, be careful not to screw it up with user permissions. This line is all that's needed:
You run it twice; one from your node to a hard drive, and the second from your hard drive to your other computer.
You run it twice; one from your node to a hard drive, and the second from your hard drive to your other computer.
peers.dat does not have any personally identifiable information because this information is serialized from (ultimately) CNode which only contains addresses and some other connection stats, and its also used to display the GUI tables of peers such as this one. This statement on the wiki will be adjusted accordingly.
Will give it a go 
Thank you for the wiki-entry, was very helpful.
Thank you for the wiki-entry, was very helpful.
Is it possible to somehow just duplicate the database of the first node?
I see no reason why not. Copy the data dir (see https://en.bitcoin.it/wiki/Data_directory ) on the new computer.
You can use similar structure or you can run with -datadir parameter.
Quote from: https://en.bitcoin.it/wiki/Data_directory
The database files in the "blocks" and "chainstate" directories are cross-platform, and can be copied between different installations.
I'm running a full nod and I'd like to get another one running.
Is it possible to somehow just duplicate the database of the first node?
I guess this question has already been asked on the forum.
Is it possible to somehow just duplicate the database of the first node?
I guess this question has already been asked on the forum.
Jump to: