Skip to main content

Backup and Restore

Back up PostgreSQL and Dash config before upgrades, migration work, and storage changes.

Backup​

Dash control plane:

pg_dump -Fc -d <db_name> -f ithiltir-$(date +%Y%m%d%H%M%S).dump
tar -C /opt -czf ithiltir-dash-config-$(date +%Y%m%d%H%M%S).tar.gz Ithiltir-dash/configs Ithiltir-dash/install_id

Node config:

Linux/macOS:

cp /var/lib/ithiltir-node/report.yaml ./report.yaml.bak

Windows:

Copy-Item "$env:ProgramData\Ithiltir-node\report.yaml" .\report.yaml.bak

Redis is optional for backup. Redis loss affects sessions, hot snapshots, and alert runtime state. Persistent settings and history data are in PostgreSQL.

Restore Dash​

  1. Install the same or a compatible release package.
  2. Stop dash.service.
  3. Restore PostgreSQL.
  4. Restore /opt/Ithiltir-dash/configs/config.local.yaml and /opt/Ithiltir-dash/install_id when available.
  5. Run migration.
  6. Start dash.service.
systemctl stop dash.service
pg_restore -d <db_name> ithiltir.dump
env DASH_HOME=/opt/Ithiltir-dash /opt/Ithiltir-dash/bin/dash migrate -config /opt/Ithiltir-dash/configs/config.local.yaml
systemctl start dash.service

If install_id changes, existing node configs can still report with their configured target and secret. Running report install against the new Dash writes the new server_install_id.

Restore Node Config​

Linux/macOS:

install -m 0600 report.yaml /var/lib/ithiltir-node/report.yaml
systemctl restart ithiltir-node.service

macOS uses launchd restart commands instead of systemd.

Windows:

Copy-Item .\report.yaml "$env:ProgramData\Ithiltir-node\report.yaml" -Force
Restart-Service ithiltir-node

Upgrade Backup​

Before upgrading, back up at least:

  • PostgreSQL database.
  • /opt/Ithiltir-dash/configs/config.local.yaml.
  • /opt/Ithiltir-dash/install_id.

The update script backs up the install directory, but it does not create a database backup.