Skip to main content

Backup & Restore

What holds your state​

Everything stateful is in the data directory (default /var/lib/omnibus):

  • config.json — admin users (bcrypt hashes), MQTT broker settings, and every port's configuration.
  • audit.log — append-only audit trail.
  • TLS material — internal CA and the server leaf certificate.

Back up the data directory and you can rebuild the unit on any host. It is mode 0750 and owned by the omnibus user — some secrets (the MQTT broker password, OSDP SCBKs, webhook HMAC secrets) are stored in plaintext because OmniBus has to present them upstream, so treat the directory as sensitive.

Config export / import​

OmniBus can export and import its configuration from the Account page (and the API). Use it to:

  • Snapshot a working config before a risky change.
  • Clone a configuration to another unit.

Encrypted backups​

Exports can be AES-256-GCM encrypted with a passphrase. Use this whenever a backup leaves the box — it protects the plaintext secrets in config.json. You need the same passphrase to import.

Restoring​

  1. Import the backup file from the Account page (supply the passphrase if it's encrypted).
  2. OmniBus applies the configuration and restarts the affected adapters.

To restore by hand on a fresh install, stop the service, drop your saved config.json into the data directory with correct ownership (chown omnibus:omnibus), and start the service:

sudo systemctl stop omnibus
sudo install -o omnibus -g omnibus -m 0640 config.json /var/lib/omnibus/config.json
sudo systemctl start omnibus