Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example on how to run this on nodeos (state + blocks) - Help #11

Open
davidfrothin opened this issue Sep 14, 2020 · 1 comment
Open

Comments

@davidfrothin
Copy link

davidfrothin commented Sep 14, 2020

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.

@calebpower
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants