# ODB configuration

The SQLite database that stores the configuration of a Zato environment.

The ODB (operational database) is an internal component of Zato which stores the configuration of a given server - e.g. services, channels, security definitions and other objects. Each environment has its own ODB and it runs on SQLite.

The database is managed by Zato automatically and there's no need for you to access it manually, but if you're like to check what it looks like internally, you can find it here `/opt/zato/data/zato.db` inside a running Zato container.

Unlike the audit log database, the ODB doesn't need any backups - it is always recreated from your [enmasse](https://zato.io/docs/admin/enmasse.html) configuration each time a container starts.

## See also {#see-also}

- [Backup](https://zato.io/docs/admin/backup.html) - What to back up when the configuration lives in Git
- [Enmasse](https://zato.io/docs/admin/enmasse.html) - The YAML export that recreates the ODB contents at each start
- [Audit log](https://zato.io/docs/admin/audit-log/index.html) - The separate database that records API traffic

## Learn more {#learn-more}

- [Production best practices](https://zato.io/docs/admin/production-best-practices.html) - What to configure before an environment takes real traffic
- [Audit log](https://zato.io/docs/admin/audit-log/) - Every request, response and error, and what you can do with them afterwards
- [Health checks](https://zato.io/docs/admin/health-checks.html) - Have Zato ping your outgoing connections instead of waiting for traffic to fail
- [Logging](https://zato.io/docs/admin/logging.html) - What is written where, and how to ship it to Splunk, Loki, Elastic or Datadog
- [GitOps with enmasse](https://zato.io/docs/admin/enmasse.html) - Keep the whole environment in git as YAML and import it anywhere