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 a <block device>, it is recommended to use the partition type and not the disk, as shown in the following example:
sudo su –
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:
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 as follows:
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: