PeerPlays Update (Setting a Backup Witness Server, Switching Servers)

Simple guide for witnesses creating a backup server and switching without missing blocks:
The same process can be applied to a steem witness node
Replace joseph-witness to your witness name.
Replace public/private keys with yours.
First: you created your witness node and now running it according to these directions:

https://github.com/PBSA/peerplays/blob/master/README.md
On the off chance that you lined the guidelines you will wind up with something like this in config.txt

witness-id = "1.6.41"

private-key = ["PPY7ZBgUduxjAsk5zXLeZX8skTHAjqQAyu6NnoSDKHs2Utm5XsDLR",

what's more, you will be marking hinders with that key.

Second: you will order another hub on server2 following similar directions like some time recently, just this time, you create another witness key utilizing the charge

" suggest_brain_key "

lets say the new open key was

" PPY5tPcG5AX6YFYsBR739JNxFzmDWUgrw6BZFBxfKRsTKAx4QiA76 "

your config.txt on server2 ought to have this:

witness-id = "1.6.41"

private-key = ["PPY5tPcG5AX6YFYsBR739JNxFzmDWUgrw6BZFBxfKRsTKAx4QiA76","

When you run the hub on server2 you will see this message:

[block_production_loo ] Not creating piece since I don't have the private key for

PPY7ZBgUduxjAsk5zXLeZX8skTHAjqQAyu6NnoSDKHs2Utm5XsDLR

This is ordinary since we didn't run the update_witness charge yet.

Presently suppose you have to refresh server1 when the code on github is refreshed

In the first place you run the update_witness order in your CLI like this:

update_witness joseph-witness "https://steemit.com/peerplays-witness/@jo

before long, your server1 will demonstrate this message:

[block_production_loo ] Not delivering piece since I don't have the private key for

PPY5tPcG5AX6YFYsBR739JNxFzmDWUgrw6BZFBxfKRsTKAx4QiA76

furthermore, information for you for marking key will resemble this

"signing_key": "PPY5tPcG5AX6YFYsBR739JNxFzmDWUgrw6BZFBxfKRsTKAx4QiA76",

"name": "joseph-witness",

You just pulled a quick switch from server1 to server2 without missing any blocks. Now you can safely shut down server1 and update the code. once the code is updated and the node is restarted, you can switch back signing blocks to server1 using the update_witness command again with public-key for server1.

update_witness joseph-witness "https://steemit.com/peerplays-witness/@jo

Critical:

Starting at now the TX charge for the update_witness order is 0.5 PPY that is a high cost and ought to be much lower.

I talked with Jonathan today and he said the expense for update_witness ought to be much lower. Until the point when that is settled, ensure you have no less than 1 PPY in your record to execute two update_witness charges.

It's dependably a smart thought to keep up a reinforcement witness server for piece creation, if there should arise an occurrence of downtime on one server or the need to refresh code without closing down your generation hub. A move down server will likewise be helpful in the event of an assault on the system.