Backup and Restore

The Mica system manages data both in the MongoDB database and in its local configuration/data files (as defined by MICA_HOME).

The backup steps are:

  1. Stop Mica application

  2. Backup Mica local files

  3. Backup MongoDB

The restore steps are:

  1. Restore MongoDB

  2. Restore Mica local files

  3. Start Mica application



Some configuration and data are stored in local files and must be backup explicitly:

  • conf, contains the application’s configuration files, including instance specific templates and taxonomies.

  • data, contains the history of changes of the various documents and the local keystore.

  • plugins, contains the plugins binary libraries and specific configurations for the Mica server.

  • [optional] work, contains files that can be rebuilt such as the caches and the search index.


Mica application includes its own internal upgrade mechanism, then when restoring the runtime environment with a more recent version of Mica, the upgrade process will be automatically triggered. Still, it is recommended to look at the release notes on to verify if there are any manual upgrade actions: if this is the case, restore the Mica server one version after the other.


The MongoDB database contains the different Mica documents in there latest version. See official MongoDB documentation about the different methods for MongoDB Backup/Restore.

Using Docker

When Mica and MongoDB are managed by Docker, you may consider backup and restore containers volumes the Docker’s way: see Backup, Restore or Migrate Data Volumes - Docker documentation.

Note: in the Mica Docker container, MICA_HOME is /srv.