Linux

Where Does SonarQube Store Data and Config?

SonarQube reads sonar.properties in conf with the embedded database and extensions under data beside it.

Last updated

SonarQube splits state between a properties file and a data tree. The conf folder holds sonar.properties for database URLs and ports. Findings live in the configured database while Elasticsearch indices sit under data.

Zip installs, packages, and Docker images root these differently. Production always points at an external database, which makes the local data disposable. Back up the properties file with database dumps for restores.

Where SonarQube stores this, by platform

Linux
[SonarDir]/conf/sonar.properties

Database URL, ports, and LDAP settings live here. Data indices sit in data beside conf. Docker layouts remap both, so inspect volumes.

Frequently asked questions

Where is the SonarQube database?

Wherever sonar.properties points, Postgres or another supported engine for production. The embedded database suits trials only. Dump it before every upgrade.

How do I back up SonarQube?

Copy sonar.properties with a database dump and any custom plugins from extensions. Indices rebuild from the database. Keep version matched backups per release.

Notice an outdated path? Let us know.