What happens if a server contain fully synced ethereum node is clone and started, how will the blockchain handle cloned instances ?

Cloning the OS disk image, and running it on a different physical server, and maybe different network. assuming we are using go geth in full syncing mode.

  • Do you mean the whole disk(s) (OS, applications, data) is cloned and put into an identical machine? And do you mean both machines are running at once (and the node software)? What node software? What is the network configuration you're envisioning? And are the nodes doing anything in particular or just connecting to the blockchain and syncing?
    – lungj
    Sep 15, 2017 at 2:53
  • @lungj I added the details you requested.
    – Nabil Sham
    Sep 15, 2017 at 3:14

1 Answer 1


(I'll assume you aren't going to run into OS licensing issues and can boot straight in and that you've handled any network issues.)

You should have two nodes that stay in sync with the network and can serve requests. You shouldn't notice any differences/problems for the configuration you've described. The new machine will have many of the same peers as the first one, which may be undesirable, because it will have the same peers list. I've forked VM disk images with no trouble with geth (pre-DAO). You may need to delete the nodekey file on the "new" machine (see here); I've always done this, so I don't know what happens if you don't (probably nothing terrible).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.