Cloud Data Manager

Install MinIO S3-Proxy

When using a local storage solution, S3-Proxy software is required to handle the Model9 S3 requests to the storage. The following steps describe the installation of MinIO as the S3-Proxy. Mount the MinIO filesystem on a directory different from the Model9 home directory. For example:

# Use a separate filesystem mount on /minio

Make sure there is enough free space to accommodate the expected number of backups and archives. It is recommended to use the ‘xfs’ filesystem type. Contact your Linux administrator to allocate adequate space and ensure it is mounted.


This procedure is intended for new and unmounted block devices only, it will overwrite any data that might already exist on the device.

For <block device> it is recommended to use the partition type and not the disk, as shown in the following example:

sudo su –
export MINIO_HOME=/minio
mkdir -p $MINIO_HOME
mkfs.xfs /dev/<block device>
# add the following line to your /etc/fstab
/dev/<block device> /minio xfs defaults 0 0

UTC Date and Time

The object storage protocol requires the z/OS USS and object storage UTC times to match.

When using MinIO as object storage, the Linux server UTC must match the z/OS USS UTC. Use the following command to verify the MF UTC date/time on USS:

date -u

Run the same command on the management server Linux system to verify that the date and time match. If they do not, contact the Linux administrator to update the Linux UTC date and time.

Optional - Enabling data in flight encryption

Enable the optional Data-In-Flight encryption between the mainframe and storage system by following these steps:


Enabling Data-In-Flight encryption requires excessive ZIIP CPU usage.

The default Model9 installation provides a self-signed certificate. For production-level workloads it is strongly advised to generate a site-defined certificate. Copy the default keys to the certificates directory using the following commands:

cp $MODEL9_HOME/keys/minio_private.key $MODEL9_HOME/conf/minio/certs/private.key
cp $MODEL9_HOME/keys/minio_public.crt $MODEL9_HOME/conf/minio/certs/public.crt

MinIO deployment

Deploy the MinIO application components using the following commands:

# On Linux on z issue:
sudo docker load -i $MODEL9_HOME/minio-s390x-2018-01-02T23-07-00Z.docker
# On Linux issue:
sudo docker load -i $MODEL9_HOME/minio-x86-2018-01-02T23-07-00Z.docker

Starting the MinIO container

  1. Start the MinIO container using the following command:

    sudo docker run -d -p -v $MINIO_HOME:/export:z \
    -v $MODEL9_HOME/conf/minio:/root/.minio:z --restart unless-stopped \
    --name minio minio/minio server /export


    Make sure to edit time zone settings to ensure proper scheduling.

  2. Determine the health status of the container using the following command:

    docker ps -a
  3. Verify the command returns a value of “(healthy)” as shown in the following example:

  4. Extract the Access Key and Secret from MinIO using the following command:

    docker logs minio
  5. Verify that the command returns the AccessKey and SecretKey as shown in the following example:


    The displayed details are required for completion of the installation process.

  6. Once the MinIO installation is complete, use the following commands to stop, start, or restart the container as required:

    docker stop|start|restart minio
  7. Display the Model9 Server’s resource consumption using the following command:

    docker stats minio