Where Does GLPI Store Config and Data?
GLPI 10+ splits config (/etc/glpi), data (/var/lib/glpi), and logs. Assets live in MariaDB; files beside them.
Last updated
GLPI 10 reorganized into system paths: /etc/glpi holds config_db.php with database credentials, /var/lib/glpi holds uploaded files and marketplace plugins, /var/log/glpi holds logs. Assets, tickets, users, and history live in MariaDB/MySQL. The official image exposes config, marketplace, and files as volumes by default.
That split is the backup: database dump plus the three trees. Older 9.x guides point inside the web root and mislead on modern installs. Remove install/install.php after setup; leaving it permits database reinitialization over live data. FusionInventory and agent-collected data land in the same database, so inventory restores ride along with tickets.
Where GLPI stores this, by platform
/etc/glpi (config dir)
config_db.php with DB credentials. Remove install.php post-setup. Marketplace and files live in sibling trees; all three plus the dump form the backup.
/var/lib/glpi (data dir)
Uploaded documents and marketplace plugins. Mount persistently in Docker. Pair with the config dir, logs, and database dump; one alone restores nothing usable.
Frequently asked questions
how do i back up glpi
Copy /etc/glpi (config_db.php), /var/lib/glpi (files, marketplace), /var/log/glpi, plus a MariaDB dump with the app stopped. Assets, tickets, and users travel in the database; documents and plugins in the trees. Restore all four.
did glpi move its directories in version 10
Yes, since 10. Config, files, marketplace, and logs moved out of the web root into dedicated paths (and Docker volumes). Old guides pointing at web-dir files/ describe 9.x layouts. Follow the 10+ split for new installs.
Notice an outdated path? Let us know.