You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the ideal way to run this for blocks and state backup on nodeos? Should nodeos be stopped and then this run and then nodeos started again? Also, same steps in reverse to restore nodeos?
Finally, why would someone use this as opposed to snapshot system available on EOS.
It will be useful to update readme for this too.
The text was updated successfully, but these errors were encountered:
Apologies for the late response on this. Hopefully you haven't been waiting a year, but I'll put this here anyhow for anyone else that might stumble on this.
Yes. You should probably stop nodeos first so that it isn't writing files when you are conducting a backup. For minimal downtime, use a second node so that a producer is always online.
Definitely for restoring, you should stop nodeos. Chances are, if you're restoring from a backup, nodeos has already stopped.
I could be incorrect, but I don't believe snapshots are going to help much if you're running a history node. If you want to restore all data, this would be the better option.
Hi,
This is more of a how-to than an issue.
What is the ideal way to run this for blocks and state backup on nodeos? Should nodeos be stopped and then this run and then nodeos started again? Also, same steps in reverse to restore nodeos?
Finally, why would someone use this as opposed to snapshot system available on EOS.
It will be useful to update readme for this too.
The text was updated successfully, but these errors were encountered: