Skip to main content
Version: v5.0.0

Backup and Restore Your Node

Backup your node identity​

Your identity password (called the database password in older guides) is the --password value in Docker, HOPRD_PASSWORD in Docker Compose, and Identity file password in Dappnode.

Please select a platform to backup your node identity:

The identity file is automatically created and stored on your machine.

  1. Back Up Your Identity File

    note

    These steps are for a v3.0.x node. On v5.0.0, your identity file is ~/hoprd/hopr.id.

    The identity file .hopr-id-dufour is located at:

    ~/.hoprd-db-dufour/.hopr-id-dufour
    note

    The folder and the file names start with a dot, so they're hidden. In Finder, press Cmd + Shift + . to show them. In a terminal, use ls -a.

  2. Write Down Your Identity Password

    The password is set using the --password flag in the HOPRd Docker command.

    Default password:

    open-sesame-iTwnsPNg0hpagP+o6T0KOwiH9RQ0
  3. Copy, Rename and Store Your Backup Safely

    • Copy the identity file out of the node folder and rename it to hopr.id.
    • Save both hopr.id and your password in a secure location, ideally also off this machine.

Restore your node identity​

Please select platform to restore your node identity:

  1. Ensure You Have a Backup

    Before restoring your node identity, make sure you have already backed up your HOPR node identity.

    You will need the identity file hopr.id and the corresponding identity password.

  2. Restore the Identity File

    Copy your backed-up hopr.id file into the following folder:

    ~/hoprd/
  3. Set the identity password

    Set identity.password in ~/hoprd/hoprd-docker.cfg.yaml to the identity password used for your previous node. Default password: open-sesame-iTwnsPNg0hpagP+o6T0KOwiH9RQ0

  4. Configure and start your node

    Fill in the rest of the configuration file and start the node, just as you did when initially setting up a new node.

    For more details, see this section.


Migrate your node from v3.0.x to v5.0.0​

The migration guide has its own page: Migrate node from v3.0.x to v5.0.0.