Signals Image Artist: Using a custom storage mountpoint for MinIO

SImA is configured so that the MinIO server stores its payload in a docker named volume(s). These named volumes are managed by the docker daemon and are stored under the /var/lib/docker/volumes directory on the SImA host. As the MinIO volume will likely become very large, e.g. in excess of 100TB, it may be more appropriate to store the volume on a separate disk or mountpoint.

If a custom storage location is required, the configuration must be modified as described below.

WARNING: The workflows below describe how to set a custom storage location for new SImA installations. If the storage mountpoint is changed for an existing SImA installation, data migration must also be considered. 

SImA v1.1 or below:

The MinIO volume mountpoint is defined within the docker-compose.yml file found in the SImA installation directory, specifically within the mapping of the minio1 service. See line 11 in the example below.

01   minio1:
02     <<: *service-base
03     image: minio-server
04     build:
05       context: ./minio
06       dockerfile: Dockerfile.server
07     entrypoint: sh
08     command: [/scripts/minio_server_entrypoint.sh, /data1]
09     env_file: default.env
10     volumes:
11       - minio1_data:/data1

Using the example above, line 11 should be modified so that the docker named volume minio1_data is replaced by the desired storage mountpoint. For example, if the MinIO volume should be stored under /nfs/minio_volume, then the updated mapping would look like this:

01   minio1:
02     <<: *service-base
03     image: minio-server
04     build:
05       context: ./minio
06       dockerfile: Dockerfile.server
07     entrypoint: sh
08     command: [/scripts/minio_server_entrypoint.sh, /data1]
09     env_file: default.env
10     volumes:
11       - /nfs/minio_volume:/data1

This change will take effect when the SImA stack is next deployed. 

SImA v1.2 or above:

The MinIO volume mountpoint is defined via the MINIO_VOLUME_PATH variable within the .env file (hidden file) found in the SImA installation directory. 

MINIO_VOLUME_PATH=minio1_data

MINIO_VOLUME_PATH should be redefined so that the docker named volume minio1_data is replaced by the desired storage mountpoint. For example, if the MinIO volume should be stored under /nfs/minio_volume, then the updated mapping would look like this:

MINIO_VOLUME_PATH=/nfs/minio_volume

This change will take effect when the SImA stack is next deployed. 

SImA v1.4 or above:

SImA data is pre-configured to use volume minio_user_data_new_fs located in
/var/lib/docker/volumes/SImA_minio_user_data_new_fs

The MinIO volume mountpoint is defined via the MINIO_VOLUME_PATH_NEW_FS variable within the .env file (hidden file) found in the SImA installation directory:

Replace minio_user_data_new_fs in .env file with the new path, e.g.

MINIO_VOLUME_PATH_NEW_FS=/path/to/remote/minio/data

This change will take effect when the SImA stack is next deployed. 

Note - if you have upgraded from an earlier version of SImA, the .env file will contain reference to the original MINIO_VOLUME_PATH  e.g.

MINIO_VOLUME_PATH=/my_minio
MINIO_VOLUME_PATH_NEW_FS="/my_minio/test"