Tarsnap VS Seaweed FS

Tarsnap for configs and critical stuff (password database, emails). Source: over 1 year ago

Someone does :) https://tarsnap.com > Tarsnap uses a prepaid model based on actual usage: > Storage: 250 picodollars / byte-month of encoded data. - Source: Hacker News / about 2 years ago

Each server also upload their configs and « important » data (my mails and git repos) to tarsnap 3. Tarsnap storage is not as cheap as B2, so I try not to upload too much data there, but it's reliable and easy to use. It was also my first backup solution, and barely cost me 10$ a year so I keep it as a secondary backup. Source: over 2 years ago

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet. Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing I've actually been looking for more open alternatives, but haven't found much. Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively:... - Source: Hacker News / 6 months ago

Wireguard + GUI: https://github.com/wg-easy/wg-easy Backups of mail accounts: https://www.offlineimap.org Cloud storage for phones: http://nextcloud.com Mirroring podcasts locally: https://github.com/akhilrex/podgrab My own matrix instance: https://matrix-org.github.io/dendrite/ Backups: https://restic.net Media Management: https://jellyfin.org Relay only tor help: https://www.torproject.org S3 compatible storage:... - Source: Hacker News / 7 months ago

JuiceFS is mostly POSIX compatible, but there are important caveats to that like no ACL, copying files changes their mtime (which impacts backup tools), has "close-to-open" consistency (which makes it dangerous for log appenders). Choosing an appropriate solution in this space still depends on what you need to do with the storage, and some options are MooseFS https://github.com/moosefs/moosefs, Curve... - Source: Hacker News / about 1 year ago

Supabase-Storage uses an S3 compatible API and is ultimately just middleware for it. So, the redundancy would be at the storage backend systems. Seems like the majority of s3 compatible selfhosted systems are built for redundancy/high-availability. With only a brief read of docs, and in no particular order: Https://garagehq.deuxfleurs.fr/documentation/quick-start/ Https://github.com/seaweedfs/seaweedfs CEPH... Source: about 1 year ago

Adopted SeaweedFS few months back. Never looked back since then. It's fast even on HDD disks. https://github.com/seaweedfs/seaweedfs#introduction. - Source: Hacker News / about 1 year ago