Skip to content

Back up a validator (also for migrating a validator to a new machine)

Jump to bottom
Elliot. edited this page Jul 2, 2025 · 1 revision

Be sure to save:

  • the key
  • validators.txt e.g. "/etc/opt/ripple/validators.txt"
  • rippled.cfg e.g. "/etc/opt/ripple/rippled.cfg"
  • wallet.db e.g. "/var/lib/rippled/db/wallet.db"

In the future, you may want to save log files. Logging is becoming a bigger focus for operators, in order to help core devs identify issues and potential performance improvements.

Regardless, don't store your validation keys on the server. Use a token and keep keys safe and offline.

When doing hardware and OS upgrades, consider the following.

  1. Back up important files:
  • wallet.db
  • rippled.cfg
  • validators.txt
  • Depending on how your validation private keys were generated, you may have a master seed file in /root/.rippled/. That seed file should be stored securely offline with backups. It is required to generate/update the validation token.
  1. Consider using nudb.

General advice

Turn off swappiness. No need for it.

cat /proc/sys/vm/swappiness

Add vm.swappiness=0 in /etc/sysctl.conf

Then, do:

sysctl --load=/etc/sysctl.conf

https://askubuntu.com/questions/157793/why-is-swap-being-used-even-though-i-have-plenty-of-free-ram

Clone this wiki locally