In this article:

Creating a Backup and Restoring System

Backup can be used to restore system availability in case of unexpected behavior and also prevent loss of user data and made configuration changes.

The following can be backed up and restored:

PostgreSQL databases:

main. It contains API users credentials, parameters of connection data sources and their resources, parameters ofenvironments and projects, parameters of connection to LDAP directory, APNs certificates for sending push notifications, and so on.
cache. It contains cache data requested by mobile platform server, or mobile device from data source.
local. It contains data of the Local Database source.

TIP. It is recommended to set object copy frequency depending on how often new data is added. For example, for the main database determine frequency of adding API user accounts, for the cache database determine frequency of data change on schedule of cache update, for the local database determine frequency of adding new data to the Local Database data source. A backup is created after the peak of adding new data.

File storage MinIO. It contains loaded files and certificates for connecting to data sources.
Technical logs in the Elasticsearch storage.
Configuration file .env. It contains information about used containers in use and other system settings.

If Foresight Mobile Platform 23.05 and later is used, creating a backup and restoring of Elasticsearch logs is available separately from the system.

Creating a Backup

A procedure of creating a backup differs depending on the version of Foresight Mobile Platform:

Restoring System from Backup

Restoring of system from backup differs depending on the version of Foresight Mobile Platform: