Hello,
I am a newbie with TrueNAS and the Minio with little linux knowledge using TrueNAS-12.0-U8
My goal is to render my Veeam setup a repository with imumutablity feature.
Following some good links on internet, did acheive something so far but not good enough to proceed with.
jorgedelacruz.uk
Problem : if i let the S3 service port at 9000 and Console port at 9001 and let the Jail Network properties NAT Forwarding at 9000 and 9001 then i cannot reach the MiniioJail url at port 9001.
If i change the console port to 9002 and let the Jail Network properties NAT Forwarding at 9000 and 9001 i can reach the Minio at port 9002. Strangely my /etc/rc.conf says still 9001.
Set went fine but cannot create bucket with mc client.
mc alias set minioveeam https://192.16.1.127:9002 TESTRHO6IBB TESTV7f1CwQqAcwo80UEI --api S3v4
Added `minioveeam` successfully.
mc mb minioveeam/veeam --with-lock
mc: <ERROR> Unable to make bucket `minioveeam/veeam`. Put "https://192.16.1.127:9002/veeam/": dial tcp 192.16.1.127:9002: connectex: Unable to connect because the target computer has actively declined the connection.
if i shuffle with ports of S3 and Jail Network properties then i get error
mc: <ERROR> Unable to make bucket `minioveeam/veeam`. S3 API Request made to Console port. S3 Requests should be sent to API port.
i have made 4 pools with dataset to make erasure code work and changed the rc.conf (see picture) not sure if this is put right by me.
Need some guidance step by step if possible :) Appreciate your help in loads. Thanks in advance.
Regards
I am a newbie with TrueNAS and the Minio with little linux knowledge using TrueNAS-12.0-U8
My goal is to render my Veeam setup a repository with imumutablity feature.
Following some good links on internet, did acheive something so far but not good enough to proceed with.
Veeam, S3 Object Locks, MinIO and TrueNAS
I’ve been using the Veeam feature of a scale-out repository that leverages S3 storage for offsite and long term retention for a while. One of the interesting variants on this option is the ability to leverage the S3 object lock feature which basically tells the system that whatever happens, an...
infrageeks.com

Veeam: How-to Deploy, and Configure MinIO with Erasure Coding Enabled, Immutability, and Let's Encrypt - The Blog of Jorge de la Cruz
Greetings friends, just a few days ago Veeam officially announced the support for MinIO Immutability on its HCL. This is wonderful news for us to test this functionality in our labs, or in case we are using Linux storage with MinIO for production. In this blog entry, we’re going to jump into the...

Problem : if i let the S3 service port at 9000 and Console port at 9001 and let the Jail Network properties NAT Forwarding at 9000 and 9001 then i cannot reach the MiniioJail url at port 9001.
If i change the console port to 9002 and let the Jail Network properties NAT Forwarding at 9000 and 9001 i can reach the Minio at port 9002. Strangely my /etc/rc.conf says still 9001.
Set went fine but cannot create bucket with mc client.
mc alias set minioveeam https://192.16.1.127:9002 TESTRHO6IBB TESTV7f1CwQqAcwo80UEI --api S3v4
Added `minioveeam` successfully.
mc mb minioveeam/veeam --with-lock
mc: <ERROR> Unable to make bucket `minioveeam/veeam`. Put "https://192.16.1.127:9002/veeam/": dial tcp 192.16.1.127:9002: connectex: Unable to connect because the target computer has actively declined the connection.
if i shuffle with ports of S3 and Jail Network properties then i get error
mc: <ERROR> Unable to make bucket `minioveeam/veeam`. S3 API Request made to Console port. S3 Requests should be sent to API port.
i have made 4 pools with dataset to make erasure code work and changed the rc.conf (see picture) not sure if this is put right by me.
Need some guidance step by step if possible :) Appreciate your help in loads. Thanks in advance.
Regards