Note: This workflow applies to SImA version 1.4, which is the latest release at the time of writing. For procedures related to earlier versions, refer to the relevant Installation and Administration Guide.
It is strongly recommended to perform a full server backup, such as a system image or snapshot. If a full backup is not feasible, ensure that the following critical data are backed up:
-
Docker Configurations (found in the SImA base directory)
- Docker secrets: Complete
.secrets
directory - Docker configs: Complete
configs
directory
- Docker secrets: Complete
-
SImA Configurations (found in the SImA base directory)
custom.env
.env
docker-compose-custom.yml
-
SImA Database
- PostgreSQL backups: All *.sql files in
/SImA/db_backup/[most_recent_timestamp]
- Refer to Signals Image Artist: Backing up the Postgres databases
- PostgreSQL backups: All *.sql files in
-
Payload data
- For MinIO Storage:
Check the MINIO_VOLUME_PATH_NEW_FS
value in SImAs .env
file to determine the correct payload location:
-
-
For S3 Storage:
- Bucket specified by
DATA_BUCKET_ORIGINAL
incustom.env
- Bucket specified by
DATA_BUCKET_SIMA
incustom.env
- All External buckets configured for use with SImA
- Bucket specified by
-
For S3 Storage:
Comments
0 comments
Article is closed for comments.