Backing Up and Restoring the Application

The Platform relies on two main databases to store the application data.

  • A PostgreSQL relational database stores the project scenarios data used, for instance, by the Data Service. For more details, please refer to Section Accessing PostgreSQL.

    Note:

    Note that scenarios can be imported and exported individually. For more details, please refer to Chapter Managing the Application Data.

  • A MongoDB database stores scenario metadata and specific properties as well as application elements. For more details, please refer to Section Accessing MongoDB.

    Note:

    Note that the application configuration can be imported and exported manually. For more details, please refer to Chapter Configuring the Application.

Both PostgreSQL and MongoDB servers are running as Docker images, therefore, it is possible to save and restore an application data using Docker commands. For more details, please refer to the official Docker documentation.

Note:

  • Restoring a Docker volume overwrites the database, i.e. the new elements are not added to the ones in the application but they replace them.

  • One must have access to the corresponding files as, by default, the information about Docker containers and volumes is located in the db-gene/deployment folder.

  • It is key that the backup/restore of both the Data and Scenario Services happens at the same time to ensure that the content databases remain synchronized, even though the two Docker volumes are processed separately.

Note:

  • Restoring a Docker volume overwrites the database: the new scenarios are not added to the ones in the application but they replace them.

  • One must have access to the corresponding files: by default, the information about Docker containers and volumes is located in the db-gene/deployment folder.