Backup and restore
Back up 3AM's data volume and restore it on the same or a new server.
Everything 3AM keeps is in one place: the data volume (3am-data on a single server, the StatefulSet's
persistent volume on Kubernetes). That includes the audit log, incidents, the code index, console-managed connectors
and policy, stored secrets, and the admin token.
The backup contains secrets
The data volume holds connector secrets (files readable only by 3AM). Store backups the way you store credentials.
Back up
podman stop 3am-core # a consistent copy; 3AM resumes where it left off
podman volume export 3am-data -o 3am-data-$(date +%F).tar
podman start 3am-coreRestore
./install.sh --uninstall # keeps volumes; or start on a fresh server
podman volume create 3am-data
podman volume import 3am-data 3am-data-2026-10-04.tar
./install.sh --yesRestoring on a different server
The licence is tied to the install fingerprint. On a new server, 3AM starts in setup mode with wrong_install until you install a licence for the new fingerprint. Ask 3AM to re-issue it; everything else carries over.
After restoring, verify the audit log came back intact:
podman exec 3am-core /opt/3am/3am-core ledger-verify /var/lib/3am/ledger