retivo Docs
  1. Docs
  2. Tasks

Update and back up the node

Keep the node on the latest version and back up its data volume.

Update

On the server, in the node's folder:

cd /opt/retivo-node
docker compose pull
docker compose up -d

Your data is in a Docker volume and is kept across updates. The version runs in the bottom left corner of the node's pages and on your overview on dash.retivo.net.

Back up the data

Back up the whole volume. It contains the database, the encryption key for stored credentials and uploaded firmware:

docker run --rm -v retivo-node_retivo-data:/data -v "$PWD":/out alpine \
  tar czf /out/retivo-data-$(date +%F).tgz -C /data .

Warning

A database without /data/secret.key cannot decrypt the stored credentials. Keep the key with the backup, somewhere safe.

Restore the data

Stop the node, then unpack the backup into an empty volume and start it again:

docker compose down
docker run --rm -v retivo-node_retivo-data:/data -v "$PWD":/in alpine \
  sh -c 'rm -rf /data/* && tar xzf /in/retivo-data-2026-10-15.tgz -C /data'
docker compose up -d

Move the node to another server

  1. Back up the volume on the old server.
  2. Install the node on the new server with the same command from Download & setup.
  3. Stop it, restore the backup into its volume, and start it.
  4. On dash.retivo.net, remove the old node from the list.

What's next

Last modified October 15, 2026