Node backups

Why, and what gets backed up

If the node's disk fails, the encrypted files it holds are lost. The backup saves the node database (node.sqlite) and the encrypted file blobs. As they are sealed E2E blobs, zero-knowledge is preserved even when the backup leaves the node.

Option 1 — Do it yourself (free)

The node includes a script (backup.sh) that makes a hot backup (without stopping the node) and keeps the last N. Schedule it every night with cron and upload it wherever you like: your own server, Backblaze B2 / S3 (rclone), or another node.

# copia diaria a las 4:00, conservando 7 copias (crontab -e):
0 4 * * *  /opt/llnode/backup.sh /opt/llnode/data /opt/llnode/backups 7

# (opcional) subir fuera con rclone a Backblaze B2 / S3:
#   rclone copy /opt/llnode/backups remoto:llnode-backups/

The backup is encrypted data: even if you upload it to a third-party service, nobody can read your users' messages or files.

Option 2 — Managed backup on LOOKLOCK (optional) online payment soon

If you don't want to manage the destination, you'll be able to deposit your ENCRYPTED backups on LOOKLOCK's server, with a storage quota. They stay sealed blobs: we can't read them either. It's just one more destination, not an obligation.

Prices designed to cover the storage cost. Online payment will be enabled once the app and web are settled; in the meantime, get in touch to reserve your space.