Where Does the mempool.space Backend Store Data?
mempool backend keeps MariaDB data and disk cache under its docker folder. Config, volumes and backup notes.
Last updated
The mempool backend configures through compose environment, not a config file in Docker. The docker-compose.yml in the repo maps two host folders into the stack: one for the backend disk cache, one for the MariaDB data directory. Images alone carry no state.
Backups target the database folder or a dump of it, plus the customized compose file. The cache rebuilds from the node, so it never needs archiving. Bare-metal installs differ: they read mempool-config.json copied from the sample, overridable by path variable.
Where mempool.space stores this, by platform
<repo>/docker/mysql/data
MariaDB data mapped to /var/lib/mysql in the db container. Backend cache at <repo>/docker/data mapped to /backend/cache. Config lives as env in docker-compose.yml. Back up the mysql folder or a dump plus compose; cache rebuilds.
Frequently asked questions
Where is the mempool config file?
In Docker there is none by default: settings ride as environment in docker-compose.yml. Bare-metal setups copy backend mempool-config.sample.json to mempool-config.json. The env path variable overrides the file when both exist.
What do I back up for a mempool instance?
The mysql data folder or a database dump, plus your customized compose file. Backend cache under docker/data rebuilds from the Bitcoin node. Images and code checkouts restore from the repo.
Can I move mempool to a new server?
Copy the compose setup and the mysql data tree with services stopped, then start against the same node. Expect a cache warm-up period while statistics rebuild. Point at the existing database rather than importing twice.
Notice an outdated path? Let us know.