Is cloning a working node enough to have a new operating one?

[trukil]

I am in the latest stages of syncing my first node. As it is taking almost 48hours to sync, I was wondering if simply cloning that node would suffice to have a new one operative. Or would it be better to increase the resources of the working one?
Any suggested reading on this? (running on Google cloud)

[zbruceli]

You can clone, but you need to change the local wallet file and password. Each node has to have its own unique id, which is associated with its wallet file and password.

And here is a good guide by community member to speed up your deployment:

Deploy nodes FASTER! Custom NKN node install with your own ChainDB + script to use it all

Content: - Free Install Script for NKN node - Requirements - Create ChainDB archive and web host - METHOD 1! - Create ChainDB archive and web host - METHOD 2! - Download the custom script to your web server - Overview of the custom script - I just wanna use the script Free Install Script for NKN node you can only use it, if you have an web address to the ChainDB*.tar.gz archive, no donation to script developer, you get all the NKN, skip all this and go to “I just wanna use the script!” a…

[no112358]

Wow thnx for the mention, I was afraid noone is paying much attention to my thread

[brounk9x]

Using google cloud, I could even make more nodes and clone them, but at each cloned node would I have to make the SSH connection, delete the wallet, and create a new wallet for each node?