The following critical data must be considered as part of any back-up strategy:
1. User generated content (payload data)
By default, SImA stores its payload data in the SImA_minio1_data Docker volume. The mountpoint of the volume is customizable - the
docker volume inspect command can be used to determine the correct mountpoint.
$ docker volume inspect SImA_minio1_data | grep -i mountpoint
The following directories found within the SImA_minio1_data volume must be backed-up:
If SImA has been configured to store its payload data in Amazon S3, the MinIO index and configuration files are still stored within the SImA_minio1_data volume. It is essential to back-up both the index and .minio.sys directories found within the SImA_minio1_data Docker volume, as well as any S3 buckets used by SImA. In this case, the data directory found within the SImA_minio1_data Docker volume need not be considered.
2. PostgreSQL Databases
SImA uses several postgres databases to store user related information. By default, the relational database tables are stored within the SImA_postgres_data Docker volume.
$ docker volume inspect SImA_postgres_data | grep -i mountpoint
The database tables can be backed-up using the
backup_postgres_dbs.sh script found in the SImA installation base directory. For further information, please refer to the SImA Installation & Administration Guide.
3. Configuration files
SImA stores critical configuration files and secrets within the
.secrets directories respectively. Both directories are found within the SImA installation base directory and must be backed up as part of any backup strategy.
As well as the
.secrets directories, the following files (also found in the SImA installation base directory) must be backed up:
SImA version 1.2 (or higher):
.env [hidden file]
SImA version 1.1 (or lower):