New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Selfhosted S3
I'm playing around with the idea of setting up some selfhosted S3 storage. The idea is to use it for backups, nextcloud and whatever else I might see fit. Mostly just personal playground.
So far I've looked at SeaweedFS, MinIO and Garage. Any quick thoughts or recommendations? I'm sure each solution has it's pros and cons and is suitable in different scenarios, anyone with some experience that can shed some light?
Comments
I personally only use (self hosted)S3 occasionally. Since I'm already using AList,I just use the S3 feature inbuilt.
I know Minio is pretty good
I installed and use minio at work, and personally using garage at my own lowend vps. Both are fine.
Usability-wise for personal use, I would recommend minio because of the web interface. But too resource intensive for my low end taste.
Garage was OK to install and use, uses very little resources. Doc is very good, I configured it to listen on localhost and a caddy reverse proxy doing SSL for it. Doing my rclone and restic backups to its buckets with no issues yet (3 months) -- restic restore check finds it all good.
show me the numbers?
Just current htop output. This is as idle as they get, nobody is using either one of them in this instant:
I evaluated and measured both when choosing our restic backend, and both performed well in the single-node simple configuration with huge zfs disks backend that was our goal.
In the small 2GB VPS trying minio, I found my VM sluggish at backup times, what I did not see with garage. I can tell that my restic backups are a tad bit slow with garage in that small VPS, but at least it does not gob down the entire server.
With minio community, you don't get disk monitoring, which is fucking lame.
This fits the picture I've got from only reading the docs.
Thank you.
I've only ever used minio and seaweedfs on hetzner.
When installed on a single node both work great. When used in a distributed way (multiple nodes) you should also set up a private network (an actual switch and LAN, not vswitch) and have the servers communicate over that rather than over the public network (internet), otherwise the performance will be very poor.
Minio has 1 TB limit? I remember this number, not sure recently still limit applicable. Or it may be for cluster?
That should be the strength of garage, his cluster code is oriented for coping well with nodes that may have high latencies in a geo distributed deployment.
If that limit is written in their docs anywhere, I definitely missed it.