Upgrades, repair, backup, and removal
At minimum, preserve: Use permissions that protect enrollment tokens, directory bind credentials, TLS private keys, license state, audit logs, and reputation da
Upgrades, repair, backup, and removal
Back up before every upgrade
At minimum, preserve:
/etc/axiom/axiom.toml
/etc/axiom/tls/
/etc/axiom/license.json
/var/lib/axiom/
/var/log/axiom/
Use permissions that protect enrollment tokens, directory bind credentials, TLS private keys, license state, audit logs, and reputation data. Test restore procedures on a non-production system.
Repair or upgrade an existing server
Repair mode preserves the installed configuration and refreshes the binary, service, helper files, Linux capabilities, and reverse-proxy sysctl settings.
From an official checked-out release:
cd ~/Axiom
git pull --ff-only
sudo ./install.sh --repair
When using a self-contained release package, extract the new package in a separate directory and run its bundled repair procedure according to the release notes.
After every upgrade:
sudo systemctl status axiom --no-pager
sudo journalctl -u axiom -n 160 -l --no-pager
Confirm the node role, Management URL, listeners, heartbeat, policy generation, and representative traffic before declaring success.
Rolling order
- Back up Management and data-plane nodes.
- Upgrade Management.
- Verify Web UI, license, reputation, and node registry.
- Upgrade one DNS node and validate queries before the next.
- Upgrade one SMB node and validate benign and blocked transfers before the next.
Where continuous service is required, deploy redundant nodes and direct only a controlled portion of traffic to the upgraded node first.
Removal
Remove binaries and service while retaining configuration, state, and logs:
sudo ./install.sh --uninstall
Permanently remove service, binaries, configuration, state, and logs:
sudo ./install.sh --uninstall --purge
--purge is destructive. Export diagnostics and required audit records before using it.