To create a system backup in Foresight. Mobile Platform 23.12:
Make sure that versions of docker client and docker server correspond to 26.1.xx, and versions of docker-compose corresponds to 1.29.xx:
To get the used versions of docker client and docker server, execute the command:
% docker version
To get the used version of docker-compose, execute the command:
% docker-compose -v
If versions of docker client, docker server and docker-compose do not correspond to the specified ones, update them.
Copy the make_standalone_backup.sh script contained in the standalone_compose_files_v23.12.<version number>.zip archive and place it in the folder with the docker-compose.standalone.yml file.
Make sure that data source caches are not being updated or deleted, and user synchronization is not running from LDAP directory. To view background task log, use the Background Tasks subsection or the tasks API method. If background tasks are being executed, data integrity may be corrupted on creating a backup.
Start the script in its folder:
bash make_standalone_backup.sh
After this, the standalone_backup_<date and time of backup creation> folder is created in the folder with the script, containing backup files of PostgreSQL databases, the MinIO file storage, and Elasticsearch technical logs.
Move the standalone_backup_<backup creation date and time> folder to the to the computer used for storing backups.
Create a copy of *.env configuration file if it has not been changed, and place it to the computer next to the standalone_backup_<backup creation date and time> folder.
After executing the operations the following backups are created: PostgreSQL databases, the MinIO file storage and Elasticsearch technical logs, .env configuration file.
See also:
Creating a Backup and Restoring System | Restoring Elasticsearch Logs from Backup in Foresight Mobile Platform 23.12