In order to help guarantee that the SImA server can be successfully restored, it is recommended that a full backup of the server by way of server Image or e.g. snapshot be taken.
The individual components of the SImA server which should be considered for data backup are detailed below.
The information relates directly to SImA 1.4.x. For version specific data backup information, please refer to the relevant Installation and Administration documentation.
1) User generated content (Payload data)
MinIO
Backup the mountpoint specified after issuing the following command:
$ docker volume inspect SImA_minio_user_data_new_fs | grep -i mountpoint
e.g.
$ docker volume inspect SImA_minio_user_data_new_fs | grep -i mountpoint
"Mountpoint": "/var/lib/docker/volumes/SImA_minio_user_data_new_fs/_data",
You can also check the MINIO_VOLUME_PATH_NEW_FS= parameter in the .env file which is found inside the SImA installation directory. The .env file is hidden by default.
AWS S3
Backup the S3 buckets defined by the variables DATA_BUCKET_ORIGINAL and DATA_BUCKET_SIMA found in the custom.env file. The custom.env file can be found inside the SImA installation directory.
2) PostgreSQL databases
Postgres DB backups are automatically created once per day. The backups are stored in the following directory on the host server:
/SImA/db_backup
The backups found in the /SImA/db_backup folder include a copy of the postgresql dbs, as well as all relevant config files/folders. Check to make sure the /SImA/db_backup directory does have content and that the dbs etc are up to date and valid.
To manually backup the databases use the backup_postgres_dbs.sh script found inside the SImA installation directory.